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/shaxzodbek-uzb/agentrecallWrote 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/shaxzodbek-uzb/agentrecall/agentrecall-db)<a href="https://agentmods.dev/mcp/shaxzodbek-uzb/agentrecall/agentrecall-db"><img src="https://agentmods.dev/badge/mcp/shaxzodbek-uzb/agentrecall/agentrecall-db/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/shaxzodbek-uzb/agentrecall/agentrecall-db"><img src="https://agentmods.dev/badge/mcp/shaxzodbek-uzb/agentrecall/agentrecall-db.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentrecall-db 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 11d 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
{ "agentrecall-db": { "command": "uvx", "args": [ "agentrecall-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.
- 11d ago First seen · 8 lines scan A 92bc54fe777c
agentrecall-db is an MCP server published in the GitHub repository shaxzodbek-uzb/agentrecall (0 stars, last pushed 11d 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
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
midas
MCP server for Midas — local-first, source-traceable agent memory with no LLM at ingest. Runs locally from the midas-memory-mcp Python package. Needs 4 environment variables to run.
wanyimem
A local memory system for coding agents that stores past interactions and retrieves relevant information later. It runs through MCP, a standard way for AI tools to connect to programs.
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.
pensyve
Universal memory runtime for AI agents — episodic, semantic, and procedural memory. Remote server at mcp.pensyve.com.
mnemic-memory
MCP server "mnemic-memory" as configured in dongtang3/mnemic. Launched with /bin/bash ./scripts/run-agent-memory-mcp.sh. Needs 1 environment variable to run.