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/dawith-ai/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/dawith-ai/recall/recall-cc)<a href="https://agentmods.dev/mcp/dawith-ai/recall/recall-cc"><img src="https://agentmods.dev/badge/mcp/dawith-ai/recall/recall-cc/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/dawith-ai/recall/recall-cc"><img src="https://agentmods.dev/badge/mcp/dawith-ai/recall/recall-cc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
recall-cc 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 1mo 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
{ "recall-cc": { "command": "uvx", "args": [ "recall-cc" ] } }
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.
- 1mo ago First seen · 8 lines scan A f2a1c2511cb4
recall-cc is an MCP server published in the GitHub repository dawith-ai/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
sessions
MCP server "sessions" as configured in nicknisi/sessions. Launched with sessions --mcp.
ai-journal-mcp
Journal engine and MCP server: capture, structure, and ask questions of your work journals. Runs locally from the ai-journal-mcp Python package.
docgraph
MCP server "docgraph" as configured in carrilloapps/docgraph. Launched with cmd /c npx -y -p @carrilloapps/docgraph docgraph-mcp serve.
kbdb
A searchable second brain for AI agents: ranked keyword and semantic search over your Markdown. Runs locally from the @dikolab/kbdb npm package.
imessage-rich-search
MCP server "imessage-rich-search" as configured in cannavis/imessage-rich-search. Runs locally from the imessage-rich-search Python package.
citeguard-cli
Check a bibliography for retracted papers -- retractions, corrections, and expressions of concern via Crossref (including Retraction Watch records). CLI, Python library, MCP server, GitHub Action. Runs locally from the citeguard-cli Python package.