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/bacharyehya/claude-memory-architectureWrote 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/bacharyehya/claude-memory-architecture/mnemonic-memory)<a href="https://agentmods.dev/mcp/bacharyehya/claude-memory-architecture/mnemonic-memory"><img src="https://agentmods.dev/badge/mcp/bacharyehya/claude-memory-architecture/mnemonic-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mnemonic-memory 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 7d 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
{ "mnemonic-memory": { "command": "uvx", "args": [ "mnemonic-memory" ] } }
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.
- 7d ago First seen · 8 lines scan A bf4ea5bafb56
mnemonic-memory is an MCP server published in the GitHub repository bacharyehya/claude-memory-architecture (0 stars, last pushed 7mo 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
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
cmk
MCP server "cmk" as configured in LH8PPL/core-memory-kit. Launched with cmk mcp serve.
claudedesktop-warnerco-schematica
MCP server "claudedesktop-warnerco-schematica" as configured in timothywarner-org/context-engineering. Runs locally from the warnerco-mcp Python package. Needs 1 environment variable to run.
ccrecall
AI memory service for Claude Code — on-demand context injection with metacognition. Runs locally from the @tznthou/ccrecall npm package.
ultramemory
MCP server "ultramemory", hosted remotely at api.ultramemory.us, as configured in LogicLabsAI/ultramemory-mcp.
ultramemory-mcp
Cross-tool memory for your AI that recalls first every turn and admits when it doesn't know. Remote server at api.ultramemory.us.