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/Chikoku-NEKO/local-recall-mcpWrote 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/chikoku-neko/local-recall-mcp/local-recall-mcp)<a href="https://agentmods.dev/mcp/chikoku-neko/local-recall-mcp/local-recall-mcp"><img src="https://agentmods.dev/badge/mcp/chikoku-neko/local-recall-mcp/local-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/chikoku-neko/local-recall-mcp/local-recall-mcp"><img src="https://agentmods.dev/badge/mcp/chikoku-neko/local-recall-mcp/local-recall-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
local-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 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
{ "local-recall-mcp": { "command": "uvx", "args": [ "local-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.
- 11d ago First seen · 8 lines scan A 1ff227611a75
local-recall-mcp is an MCP server published in the GitHub repository Chikoku-NEKO/local-recall-mcp (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
delx-memory
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe. Runs locally from the delx-memory npm package. Needs 5 environment variables to run.
kimi-memory
Installer for kimi-memory MCP server — persistent memory for Kimi Code CLI. Runs locally from the kimi-memory npm package.
membrain
Self-hosted AI memory ledger. You and your agents share one memory store over MCP — one SQLite file, web UI, REST, works offline. Runs locally from the membrain-mcp npm package.
freshvault
Local semantic search over your Obsidian vault - always fresh, never reindex. Runs locally from the freshvault npm package. Needs 1 environment variable to run.
personal-model
Local-first macOS Runtime for screen-context memory, personal modeling, and MCP. Runs locally from the personal-model Python package.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.