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/Amanaakash/Obsidian-RAG-with-Claude-mcpWrote 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/amanaakash/obsidian-rag-with-claude-mcp/obsidian-rag-assistant)<a href="https://agentmods.dev/mcp/amanaakash/obsidian-rag-with-claude-mcp/obsidian-rag-assistant"><img src="https://agentmods.dev/badge/mcp/amanaakash/obsidian-rag-with-claude-mcp/obsidian-rag-assistant/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/amanaakash/obsidian-rag-with-claude-mcp/obsidian-rag-assistant"><img src="https://agentmods.dev/badge/mcp/amanaakash/obsidian-rag-with-claude-mcp/obsidian-rag-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
obsidian-rag-assistant 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
{ "obsidian-rag-assistant": { "command": "uvx", "args": [ "obsidian-rag-assistant" ] } }
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 · 8 lines scan A 1db19a21ad90
obsidian-rag-assistant is an MCP server published in the GitHub repository Amanaakash/Obsidian-RAG-with-Claude-mcp (0 stars, last pushed 4d 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
context-engine
Task-aware context compression for logs, RAG, and coding workflows. Runs locally from the melonelish-context-engine Python package.
token-savior
Optimized MCP server for AI coding agents. Structural codebase navigation + persistent memory engine — 97.9% accuracy at −80% tokens on tsbench. Runs locally from the token-savior-recall Python package. Needs 3 environment variables to run.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
inspeximus
MCP server "inspeximus" as configured in DanceNitra/inspeximus. Runs locally from the inspeximus[mcp] Python package. Needs 1 environment variable to run.
coalent
A real-time, provenance-invalidated cognitive cache layer for AI agents and RAG. Runs locally from the coalent Python package. Needs 2 environment variables to run.
re-call
Trustworthy retrieval for an AI agent's own memory — verdict, confidence and provenance per hit, or an explicit abstention. Runs locally from the recall-rag Python package. Needs 3 environment variables to run.