Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/t-rhex/obsidian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/t-rhex/obsidian-mcp-server/mcp-obsidian-vault)<a href="https://agentmods.dev/mcp/t-rhex/obsidian-mcp-server/mcp-obsidian-vault"><img src="https://agentmods.dev/badge/mcp/t-rhex/obsidian-mcp-server/mcp-obsidian-vault/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/t-rhex/obsidian-mcp-server/mcp-obsidian-vault"><img src="https://agentmods.dev/badge/mcp/t-rhex/obsidian-mcp-server/mcp-obsidian-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-obsidian-vault scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp-obsidian-vault": { "command": "npx", "args": [ "-y", "mcp-obsidian-vault" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 9 lines scan A 3d816dec1aab
mcp-obsidian-vault is an MCP server published in the GitHub repository t-rhex/obsidian-mcp-server (2 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
link
MCP server for Link local agent memory — remember, recall, search, context, and graph traversal. Runs locally from the link-mcp Python package.
vulcanus
A validated Markdown memory vault your coding agent can recall, project by project. Runs locally from the @sunsato/vulcanus npm package.
obsidian-vault-mcp
MCP server for reading and searching an Obsidian vault directly from the filesystem. No Obsidian plugin, no REST API, no running Obsidian required. Runs locally from the @phssakaigawa/obsidian-vault-mcp npm package.
obsidian-icloud-mcp
MCP server for Obsidian vaults that survives iCloud — reads, searches and writes notes without hanging on evicted files. Runs locally from the obsidian-icloud-mcp npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
vault-cortex
MCP server "vault-cortex" as configured in aliasunder/vault-cortex. Runs in Docker (ghcr.io/aliasunder/vault-cortex:0.45.0). Needs 24 environment variables to run.