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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/mcp-memory)<a href="https://agentmods.dev/mcp/nickcrew/claude-cortex/mcp-memory"><img src="https://agentmods.dev/badge/mcp/nickcrew/claude-cortex/mcp-memory/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/nickcrew/claude-cortex/mcp-memory"><img src="https://agentmods.dev/badge/mcp/nickcrew/claude-cortex/mcp-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-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 1mo 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
{
"mcp-memory": {
"command": "uvx",
"args": [
"--refresh",
"--quiet",
"mcp-memory-py"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 10 lines scan A 815efebb7a53
mcp-memory is an MCP server published in the GitHub repository NickCrew/Claude-Cortex (56 stars, last pushed 3mo 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-30.
Other mcp servers, from other repositories
hot-memory-mcp
Engram-inspired memory MCP server with hot cache and pattern mining. Runs locally from the hot-memory-mcp Python package. Needs 2 environment variables to run.
neatcontext
MCP server "neatcontext" as configured in XTSoftwareLabs/neatcontext-plugins. Runs ./src/codex/mcp-bridge.mjs with node.
loredocs
Knowledge management MCP server for AI projects - search, tag, version, and organize your project knowledge. Runs locally from the loredocs Python package. Needs 1 environment variable to run.
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.
bls-mcp
MCP server "bls-mcp", hosted remotely at 127.0.0.1, as configured in openai/openai-cookbook.