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.
npx agentmods add mcp/varun29ankus/shodh-memory/code-review-graphgit clone --depth 1 https://github.com/varun29ankuS/shodh-memoryWrote 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/varun29ankus/shodh-memory/code-review-graph)<a href="https://agentmods.dev/mcp/varun29ankus/shodh-memory/code-review-graph"><img src="https://agentmods.dev/badge/mcp/varun29ankus/shodh-memory/code-review-graph.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
code-review-graph 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 4d 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
{
"code-review-graph": {
"command": "python",
"args": [
"-m",
"code_review_graph",
"mcp"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 10 lines scan A 1f45ace42f99
code-review-graph is an MCP server published in the GitHub repository varun29ankuS/shodh-memory (275 stars, last pushed today), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
neurostack
Token-efficient MCP memory for Markdown vaults. Tiered retrieval, hybrid search, GraphRAG. Runs locally from the neurostack npm package. Needs 1 environment variable to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
mcp
Model Context Protocol server for Citadel: encrypted memory as MCP tools. Runs locally from the citadeldb-mcp Python package. Needs 1 environment variable to run.
talamus
MCP server "talamus" as configured in ampres-ai/talamus. Runs locally from the talamus[mcp] Python package.
talamus
Local-first, source-grounded memory for AI agents with citations, bitemporal history, and MCP. Runs locally from the talamus Python package.
LINZA-MCP
Local-first MCP sidecar for agent workspaces, artifacts, review intents, and context export. Runs locally from the linza-mcp Python package. Needs 9 environment variables to run.