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/Zavelinski/recallWrote 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/zavelinski/recall/recall-mcp)<a href="https://agentmods.dev/mcp/zavelinski/recall/recall-mcp"><img src="https://agentmods.dev/badge/mcp/zavelinski/recall/recall-mcp/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/zavelinski/recall/recall-mcp"><img src="https://agentmods.dev/badge/mcp/zavelinski/recall/recall-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
recall-mcp 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- recall-mcp — 100% identical, 0 lines differ
What it actually says
{ "recall-mcp": { "command": "npx", "args": [ "-y", "recall-mcp" ] } }
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.
- 9d ago First seen · 9 lines scan A 6d3b01b1c54f
recall-mcp is an MCP server published in the GitHub repository Zavelinski/recall (0 stars, last pushed 2mo 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
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
localkeep
Local memory banks you keep — a localhost Hub UI + MCP connector for Claude. You curate titled, dated memory banks on your machine; Claude recalls them via MCP. Runs locally from the localkeep Python package. Needs 2 environment variables to run.
memory-manager
MCP server "memory-manager" as configured in Kit4Some/Oh-my-ClaudeClaw. Runs ./mcp-servers/memory-manager/src/index.js with node. Needs 1 environment variable to run.
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.