Obsidian (beshkenadze) MCP Server

@beshkenadze/mcp-obsidian npm v1.2.0

Published by @beshkenadze — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
94/100
Last scanned
Trust
A · 94/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade 100 − 6.3 = 94/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 8

high Dynamic code execution in server code (dist/sse.js)MTC-SRC-001

In the server's implementation (`dist/sse.js:436`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: Function(`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/sse.js

high Dynamic code execution in server code (dist/stdio.js)MTC-SRC-001

In the server's implementation (`dist/stdio.js:436`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: Function(`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/stdio.js

high Shell/command execution in server code (dist/sse.js)MTC-SRC-002

In the server's implementation (`dist/sse.js:4283`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/sse.js

high Shell/command execution in server code (dist/stdio.js)MTC-SRC-002

In the server's implementation (`dist/stdio.js:4283`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/stdio.js

high Shell/command execution in server code (src/bin/run-with-supergateway.ts)MTC-SRC-002

In the server's implementation (`src/bin/run-with-supergateway.ts:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/bin/run-with-supergateway.ts

high Shell/command execution in server code (src/cmd/generate-types.ts)MTC-SRC-002

In the server's implementation (`src/cmd/generate-types.ts:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/cmd/generate-types.ts

high Shell/command execution in server code (src/servers/mcp-sse-server.ts)MTC-SRC-002

In the server's implementation (`src/servers/mcp-sse-server.ts:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/servers/mcp-sse-server.ts

medium Untrusted input concatenated into a command sink (src/cmd/generate-types.ts)MTC-SRC-009

In the server's implementation (`src/cmd/generate-types.ts:33`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execSync(`bunx openapi-typescript ${inputPath} -o ${

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/cmd/generate-types.ts

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.0 latest A 94/100 8 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/beshkenadze-mcp-obsidian/badge.svg)](https://mcptrustchecker.com/registry/beshkenadze-mcp-obsidian)
HTML
<a href="https://mcptrustchecker.com/registry/beshkenadze-mcp-obsidian"><img src="https://mcptrustchecker.com/registry/beshkenadze-mcp-obsidian/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/beshkenadze-mcp-obsidian/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @beshkenadze/mcp-obsidian --online

Use the free API → How scoring works

Other implementations of Obsidian 34

Independent packages implementing the same tool, scanned with the same engine. Compare all 35 side by side →

More in Productivity & Workflow