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/navid-kianfar/claude-memory-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/navid-kianfar/claude-memory-mcp/memory-mcp)<a href="https://agentmods.dev/mcp/navid-kianfar/claude-memory-mcp/memory-mcp"><img src="https://agentmods.dev/badge/mcp/navid-kianfar/claude-memory-mcp/memory-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/navid-kianfar/claude-memory-mcp/memory-mcp"><img src="https://agentmods.dev/badge/mcp/navid-kianfar/claude-memory-mcp/memory-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory-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 8d 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.
This is a copy
100% identical to memory-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "memory-mcp": { "command": "uvx", "args": [ "memory-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.
- 8d ago First seen · 8 lines scan A 6042d2aa940b
memory-mcp is an MCP server published in the GitHub repository navid-kianfar/claude-memory-mcp (0 stars, last pushed today), 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. It is 100% identical to memory-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
cmk
MCP server "cmk" as configured in LH8PPL/core-memory-kit. Launched with cmk mcp serve.
context-keeper
MCP server that maintains project context (decisions, pipelines, constraints) across Claude conversations. Runs locally from the context-keeper-mcp Python package. Needs 1 environment variable to run.
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.
groundmemory
Persistent, semantic memory for AI agents - mcp-native, local-first, framework-agnostic, production-ready. Runs locally from the groundmemory Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.