Obsidian Cli (joemugen) MCP Server

@joemugen/obsidian-cli-mcp npm v1.0.0-beta.1

Published by @joemugen — 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 CLI — semantic tools for vault management

Trust grade
B
89/100
Last scanned get badge →
Trust
B · 89/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
Critical
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
B Why this grade threat 100 − adoption risk = 89/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 − 11 = 89. 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
−10 capability blast radius (critical) — 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 7

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: obsidian_list_themes → obsidian_list_files → obsidian_eval. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow obsidian_list_themes → obsidian_list_files → obsidian_eval

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

Tool "obsidian_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 obsidian_execute_command

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

Tool "obsidian_eval" appears to run shell commands or evaluate code (keyword "eval" 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 obsidian_eval

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

In the server's implementation (`dist/index.js:7`): 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: n, execFileSync } from "child_process"; import os from "os"; var ObsidianCliService = class { constructor(obsidianBin,

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/index.js

medium Unconstrained command parameter "code" on "obsidian_eval"MTC-CAP-006

Tool "obsidian_eval" takes a command-shaped parameter "code" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool obsidian_eval · inputSchema.properties.code

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

Tool "obsidian_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 obsidian_execute_command

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

Tool "obsidian_eval" 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 obsidian_eval

Tools 78

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

  • obsidian_evalruns code / shell
  • obsidian_execute_commandruns code / shell
  • obsidian_list_filesreads sensitive data
  • obsidian_list_themesingests untrusted input
  • obsidian_sync_deletedreads sensitive data
  • obsidian_add_bookmarkno sensitive capability
  • obsidian_append_dailyno sensitive capability
  • obsidian_append_noteno sensitive capability
  • obsidian_create_base_itemno sensitive capability
  • obsidian_create_noteno sensitive capability
Show 68 more tools ↓
  • obsidian_daily_pathno sensitive capability
  • obsidian_delete_noteno sensitive capability
  • obsidian_diffno sensitive capability
  • obsidian_disable_pluginno sensitive capability
  • obsidian_disable_snippetno sensitive capability
  • obsidian_enable_pluginno sensitive capability
  • obsidian_enable_snippetno sensitive capability
  • obsidian_file_infono sensitive capability
  • obsidian_get_hotkeyno sensitive capability
  • obsidian_get_pluginno sensitive capability
  • obsidian_get_propertyno sensitive capability
  • obsidian_get_tagno sensitive capability
  • obsidian_get_themeno sensitive capability
  • obsidian_history_listno sensitive capability
  • obsidian_history_readno sensitive capability
  • obsidian_history_restoreno sensitive capability
  • obsidian_insert_templateno sensitive capability
  • obsidian_install_pluginno sensitive capability
  • obsidian_install_themeno sensitive capability
  • obsidian_list_aliasesno sensitive capability
  • obsidian_list_backlinksno sensitive capability
  • obsidian_list_base_viewsno sensitive capability
  • obsidian_list_basesno sensitive capability
  • obsidian_list_bookmarksno sensitive capability
  • obsidian_list_commandsno sensitive capability
  • obsidian_list_deadendsno sensitive capability
  • obsidian_list_foldersno sensitive capability
  • obsidian_list_hotkeysno sensitive capability
  • obsidian_list_linksno sensitive capability
  • obsidian_list_orphansno sensitive capability
  • obsidian_list_pluginsno sensitive capability
  • obsidian_list_plugins_enabledno sensitive capability
  • obsidian_list_propertiesno sensitive capability
  • obsidian_list_recentsno sensitive capability
  • obsidian_list_snippetsno sensitive capability
  • obsidian_list_snippets_enabledno sensitive capability
  • obsidian_list_tabsno sensitive capability
  • obsidian_list_tagsno sensitive capability
  • obsidian_list_tasksno sensitive capability
  • obsidian_list_templatesno sensitive capability
  • obsidian_list_unresolvedno sensitive capability
  • obsidian_list_vaultsno sensitive capability
  • obsidian_move_noteno sensitive capability
  • obsidian_outlineno sensitive capability
  • obsidian_prepend_dailyno sensitive capability
  • obsidian_prepend_noteno sensitive capability
  • obsidian_query_baseno sensitive capability
  • obsidian_random_readno sensitive capability
  • obsidian_read_dailyno sensitive capability
  • obsidian_read_noteno sensitive capability
  • obsidian_read_templateno sensitive capability
  • obsidian_remove_propertyno sensitive capability
  • obsidian_rename_noteno sensitive capability
  • obsidian_searchno sensitive capability
  • obsidian_search_contextno sensitive capability
  • obsidian_set_propertyno sensitive capability
  • obsidian_set_themeno sensitive capability
  • obsidian_sync_historyno sensitive capability
  • obsidian_sync_readno sensitive capability
  • obsidian_sync_restoreno sensitive capability
  • obsidian_sync_statusno sensitive capability
  • obsidian_toggle_taskno sensitive capability
  • obsidian_uninstall_pluginno sensitive capability
  • obsidian_uninstall_themeno sensitive capability
  • obsidian_vault_infono sensitive capability
  • obsidian_versionno sensitive capability
  • obsidian_wordcountno sensitive capability
  • obsidian_workspaceno 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.0.0-beta.1 latest B 89/100 7 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: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/joemugen-obsidian-cli-mcp/badge.svg)](https://mcptrustchecker.com/registry/joemugen-obsidian-cli-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/joemugen-obsidian-cli-mcp"><img src="https://mcptrustchecker.com/registry/joemugen-obsidian-cli-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/joemugen-obsidian-cli-mcp/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 @joemugen/obsidian-cli-mcp --online

Use the free API → How scoring works

Other implementations of Obsidian Cli 3

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

More in Web, Search & Scraping