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/adeeljames/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/adeeljames/claude-memory-mcp/claude-mcp-optimize)<a href="https://agentmods.dev/mcp/adeeljames/claude-memory-mcp/claude-mcp-optimize"><img src="https://agentmods.dev/badge/mcp/adeeljames/claude-memory-mcp/claude-mcp-optimize/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/adeeljames/claude-memory-mcp/claude-mcp-optimize"><img src="https://agentmods.dev/badge/mcp/adeeljames/claude-memory-mcp/claude-mcp-optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-mcp-optimize 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 bc0f813ddafa
claude-mcp-optimize is an MCP server published in the GitHub repository adeeljames/claude-memory-mcp (0 stars, last pushed 4mo ago), with no licence file. 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.
memstem
Unified memory and skill infrastructure for AI agents. Runs locally from the memstem Python package.
obsidian-mcp
Access your Obsidian vault from Claude Desktop and other AI tools — MCP server wrapping the official Obsidian CLI with tools, resources, and prompts. Runs locally from the @zethictech/obsidian-mcp npm package.
savecontext
MCP server "savecontext" as configured in AlexanderBoger/SaveContext. Runs savecontext with python. Needs 1 environment variable to run.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
llm-wiki-mcp
MCP server + Claude Code skills for Karpathy-style LLM wikis: persistent markdown knowledge bases your agent grows over time. Runs locally from the llm-wiki-mcp Python package.