Obsidian Extended MCP Server

mcp-obsidian-extended npm v1.1.1

Published by adder-factory — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Obsidian — 39 tools, 100% REST API coverage

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. 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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 a deduction.

Findings 9

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([list_files_in_vault, list_files_in_dir, get_file_contents, batch_get_file_contents]) and tools that can send data out ([execute_command]) are exposed together. An agent can move private data to the sink.

Evidence: sources [list_files_in_vault, list_files_in_dir, get_file_contents, batch_get_file_contents] → sinks [execute_command]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow list_files_in_vault → execute_command

high Tool "execute_command" exposes command/code executionMTC-CAP-001

Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_command

medium Tool "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool delete_file

medium Tool "move_file" can modify the filesystemMTC-CAP-002

Tool "move_file" can write, overwrite or delete files (keyword "move_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool move_file

low Mutating tool "delete_file" declares no destructiveHintMTC-CAP-005

Tool "delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool delete_file

low Mutating tool "move_file" declares no destructiveHintMTC-CAP-005

Tool "move_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool move_file

low Mutating tool "execute_command" declares no destructiveHintMTC-CAP-005

Tool "execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_command

low Unconstrained path parameter "path" on "get_file_contents"MTC-CAP-008

Tool "get_file_contents" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool get_file_contents · inputSchema.properties.path

low Unconstrained path parameter "path" on "delete_file"MTC-CAP-008

Tool "delete_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool delete_file · inputSchema.properties.path

Tools 48

Each tool and what it can reach — statically extracted from the published source.

  • batch_get_file_contentsreads sensitive data
  • delete_filewrites files
  • execute_commandruns code / shell
  • get_file_contentsreads sensitive data
  • list_files_in_dirreads sensitive data
  • list_files_in_vaultreads sensitive data
  • move_filewrites files
  • active_fileno sensitive capability
  • append_active_fileno sensitive capability
  • append_contentno sensitive capability
Show 38 more tools ↓
  • append_periodic_noteno sensitive capability
  • append_periodic_note_for_dateno sensitive capability
  • batch_getno sensitive capability
  • commandsno sensitive capability
  • complex_searchno sensitive capability
  • configureno sensitive capability
  • dataview_searchno sensitive capability
  • delete_active_fileno sensitive capability
  • delete_periodic_noteno sensitive capability
  • delete_periodic_note_for_dateno sensitive capability
  • get_active_fileno sensitive capability
  • get_backlinksno sensitive capability
  • get_note_connectionsno sensitive capability
  • get_periodic_noteno sensitive capability
  • get_periodic_note_for_dateno sensitive capability
  • get_recent_changesno sensitive capability
  • get_recent_periodic_notesno sensitive capability
  • get_server_statusno sensitive capability
  • get_vault_structureno sensitive capability
  • list_commandsno sensitive capability
  • open_fileno sensitive capability
  • patch_active_fileno sensitive capability
  • patch_contentno sensitive capability
  • patch_periodic_noteno sensitive capability
  • patch_periodic_note_for_dateno sensitive capability
  • periodic_noteno sensitive capability
  • put_active_fileno sensitive capability
  • put_contentno sensitive capability
  • put_periodic_noteno sensitive capability
  • put_periodic_note_for_dateno sensitive capability
  • recentno sensitive capability
  • refresh_cacheno sensitive capability
  • searchno sensitive capability
  • search_replaceno sensitive capability
  • simple_searchno sensitive capability
  • statusno sensitive capability
  • vaultno sensitive capability
  • vault_analysisno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

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.1.1 latest A 93/100 9 1.13.0 2026-09-07

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-obsidian-extended/badge.svg)](https://mcptrustchecker.com/registry/mcp-obsidian-extended)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-obsidian-extended"><img src="https://mcptrustchecker.com/registry/mcp-obsidian-extended/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-obsidian-extended/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 mcp-obsidian-extended --online

Use the free API → How scoring works

More in Productivity & Workflow