Skills/PyPI/obsidian-remote-mcp

obsidian-remote-mcp@2.1.2

VERIFIED· not started

Publisher claims: "MCP server for Obsidian vaults — read, write, search, graph, canvas, kanban" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher ykoellmann · publishing for 113 daysInstalls 1,599Last detonated 25 h ago
$claude mcp add obsidian-remote-mcp -- uvx obsidian-remote-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
API_KEYOAUTH_GITHUB_ALLOWED_LOGINSOAUTH_GITHUB_CLIENT_IDOAUTH_GITHUB_CLIENT_SECRETOBSIDIAN_MCP_API_KEYConfiguration, not credentials: ALLOW_PERMANENT_DELETE, AUDIT_LOG_PATH, DENY_READ_PATHS, DENY_WRITE_PATHS, EXCLUDE_PATHS, FASTMCP_HOME, HEALTH_CHECK_INBOX, INDEX_RECONCILE_INTERVAL, LOCK_PATH, MAX_ATTACHMENT_BYTES, PUBLIC_BASE_URL, READ_ONLY, READ_PATHS, REQUIRE_WRITE_PRECONDITIONS, TRANSPORT, VAULT_PATH, VAULTS_CONFIG, WATCH_MODE, WATCHER_DEBOUNCE_MS, WRITE_PATHS
Where it talks to
no vendor host named in the codeAlso obsidian.md, your-server.com, excalidraw.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names obsidian.md, your-server.com, excalidraw.com as well as its own vendor. The guard injects API_KEY, OAUTH_GITHUB_ALLOWED_LOGINS, OAUTH_GITHUB_CLIENT_ID, OAUTH_GITHUB_CLIENT_SECRET, OBSIDIAN_MCP_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx obsidian-remote-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Access to sensitive file pathsdocker-compose.home-server.yml:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# CLOUDFLARE_TUNNEL_TOKEN in .env. The complete vault remains read-only inFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.home-server.yml:48 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- "${HOST_VAULT_PATH:?set HOST_VAULT_PATH in .env}:/vault:ro"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.home-server.yml:36 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesAPI_KEY: "${API_KEY:?set API_KEY in .env}"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.home-server.yml:51 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- "${MCP_DATA_PATH:?set MCP_DATA_PATH in .env}:/data:rw"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_storage.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files_storage(tmp_path).policy.canonicalize("../../etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedscripts/run_local_smoke_test.py:93 · Python subprocess execution detectedprocess = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.yml:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Works alongside API_KEY — see .env.example for full setup instructions.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Python subprocess execution detectedscripts/run_local_smoke_test.py:101 · Python subprocess execution detectedcompleted = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.home-server.yml:62 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesTUNNEL_TOKEN: "${CLOUDFLARE_TUNNEL_TOKEN:?set CLOUDFLARE_TUNNEL_TOKEN in .env}"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsdocker-compose.yml:30 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# See .env.example for details.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈59 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for obsidian-remote-mcp@2.1.2 as of 25 h ago. This is the package itself, not its dependencies.

obsidian-remote-mcp@2.1.2 safety verdict: Verified (not started) — KillerSkills