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/maplehilllabs/mcp-mem.aiWrote 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/maplehilllabs/mcp-mem.ai/mcp-mem)<a href="https://agentmods.dev/mcp/maplehilllabs/mcp-mem.ai/mcp-mem"><img src="https://agentmods.dev/badge/mcp/maplehilllabs/mcp-mem.ai/mcp-mem/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/maplehilllabs/mcp-mem.ai/mcp-mem"><img src="https://agentmods.dev/badge/mcp/maplehilllabs/mcp-mem.ai/mcp-mem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-mem 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-mem — 100% identical, 0 lines differ
What it actually says
{ "mcp-mem": { "command": "uvx", "args": [ "mcp-mem" ] } }
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.
- 9d ago First seen · 8 lines scan A c712eacc2d0f
mcp-mem is an MCP server published in the GitHub repository maplehilllabs/mcp-mem.ai (4 stars, last pushed 6mo 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
obsidian-semantic-mcp
MCP server "obsidian-semantic-mcp" as configured in artificemachine/obsidian-semantic-mcp. Runs locally from the obsidian-semantic-mcp Python package.
vault-mind
MCP server "vault-mind" as configured in Statutecontempt951/obsidian-llm-wiki. Runs mcp-server/dist/index.js with node.
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.
technocore-chat
MCP server for technocore-chat: shared rooms, durable notes and rendezvous for agents, over plain HTTP. Runs locally from the technocore-mcp Python package. Needs 2 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.