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/jhunter11/multi-agent-memory-mcp/claude-code-multi-agent-memorygit clone --depth 1 https://github.com/jhunter11/multi-agent-memory-MCPGrade A, and why
multi-agent-memory 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 2d 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
{
"multi-agent-memory": {
"type": "stdio",
"command": "__NODE_EXECUTABLE__",
"args": [
"__SERVER_ENTRYPOINT__"
],
"env": {
"MULTI_AGENT_MEMORY_DB": "__MEMORY_DB__"
}
}
}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.
- 2d ago First seen · 12 lines scan A b28fb8eff9cc
multi-agent-memory is an MCP server published in the GitHub repository jhunter11/multi-agent-memory-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
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
waggle
MCP server "waggle" as configured in Abhigyan-Shekhar/Waggle-mcp. Runs ./plugins/waggle/bin/waggle-server-launcher.js with node. Needs 6 environment variables to run.
superlocalmemory
MCP server "superlocalmemory" as configured in qualixar/superlocalmemory. Launched with ${CLAUDE_PLUGIN_ROOT}/scripts/slm-launch. 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.
trinity-memory
Trinity v8.2.0: Memory Operating System — Multi-Agent Shared Memory, 50-Layer Guardian Chain, 129-Paper Brain-Inspired Alignment, GraphQL API, Raft Cluster, BM25+Jieba Chinese Retrieval. Runs locally from the trinity-memory Python package.