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/kengo006/alexandria-semantic-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/kengo006/alexandria-semantic-recall/alexandria-semantic-recall)<a href="https://agentmods.dev/mcp/kengo006/alexandria-semantic-recall/alexandria-semantic-recall"><img src="https://agentmods.dev/badge/mcp/kengo006/alexandria-semantic-recall/alexandria-semantic-recall/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/kengo006/alexandria-semantic-recall/alexandria-semantic-recall"><img src="https://agentmods.dev/badge/mcp/kengo006/alexandria-semantic-recall/alexandria-semantic-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alexandria-semantic-recall 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 2mo 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
{ "alexandria-semantic-recall": { "command": "uvx", "args": [ "alexandria-semantic-recall" ] } }
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.
- 2mo ago First seen · 8 lines scan A d3adf36a70e5
alexandria-semantic-recall is an MCP server published in the GitHub repository kengo006/alexandria-semantic-recall (1 stars, last pushed 1mo 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
markdown-vault-mcp
Generic markdown vault MCP with hybrid search. Runs locally from the markdown-vault-mcp Python package. Needs 91 environment variables to run.
minirag-mcp
Local-first RAG MCP server: hybrid search over your documents, fully local. Runs locally from the minirag-mcp Python package. Needs 13 environment variables to run.
mama
MAMA MCP Server - Memory-Augmented MCP Assistant for Claude Code & Desktop. Runs locally from the @jungjaehoon/mama-server npm package.
agent-knowledge
Cross-session memory and recall for AI agents — git-synced knowledge base, knowledge graph, confidence scoring, hybrid semantic+TF-IDF search, auto-distillation with secrets scrubbing. Runs locally from the agent-knowledge npm package.
re-call
Trustworthy retrieval for an AI agent's own memory — verdict, confidence and provenance per hit, or an explicit abstention. Runs locally from the recall-rag Python package. Needs 3 environment variables to run.
mnemotree
MCP server "mnemotree" as configured in kurcontko/mnemotree. Runs locally from the mnemotree Python package.