LeashIndex Get the report

Index / storage

Obsidian CLI MCP

io-github-dariuscorvus-obsidian-cli-mcp declares 42 capabilities across 42 tools, with 2 critical issues.

92/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package @dariuscodes/obsidian-cli-mcp@0.4.1 (published to npm as @dariuscodes/obsidian-cli-mcp, listed in the official MCP registry as io.github.dariuscorvus/obsidian-cli-mcp 0.4.1), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 42 tools

42 of 42 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 3 of 42 tools

3 tools are classified as irreversible and declare no limit.

high · no-expiry · All 42 tools

42 of 42 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 42 tools

42 of 42 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 28 of 42 tools

28 tools can modify data and declare no limit.

low · uncapped-read · 11 of 42 tools

11 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
note_readread declared
vault_searchread declared
note_listread declared
vault_tagsread declared
unresolved_linksread declared
tasks_listread declared
note_diffread declared
note_createwrite inferred
note_appendwrite assumed
note_set_frontmatterwrite inferred
daily_openwrite assumed
daily_appendwrite assumed
note_replace_rangewrite assumed
note_insert_atwrite inferred
note_replacewrite assumed
note_insertwrite inferred
file_importwrite assumed
attachment_importwrite assumed
note_attachwrite inferred
attachment_embedwrite assumed
file_movewrite inferred
file_renamewrite inferred
file_deletedestructive declared
file_read_binary_metadataread declared
task_createwrite inferred
task_updatewrite inferred
backlinks_getread declared
outlinks_getread declared
canvas_add_nodewrite inferred
canvas_add_edgewrite inferred
canvas_auto_layoutwrite assumed
note_renamewrite inferred
note_movewrite inferred
folder_createwrite inferred
note_deletedestructive declared
note_transitionwrite inferred
canvas_readread declared
canvas_createwrite inferred
canvas_upsert_nodeswrite inferred
canvas_upsert_edgeswrite inferred
canvas_removedestructive declared
canvas_openwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.