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/OpenAgentHQ/localmem-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/openagenthq/localmem-mcp/localmem-mcp)<a href="https://agentmods.dev/mcp/openagenthq/localmem-mcp/localmem-mcp"><img src="https://agentmods.dev/badge/mcp/openagenthq/localmem-mcp/localmem-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
localmem-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.
What it actually says
{ "localmem-mcp": { "command": "uvx", "args": [ "localmem-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 b072e6528dae
localmem-mcp is an MCP server published in the GitHub repository OpenAgentHQ/localmem-mcp (7 stars, last pushed 7d 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
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
deepmem
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically. Remote server at deepmem.dev.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
yantrikdb-mcp
YantrikDB — Cognitive memory for AI agents. Persistent semantic recall, knowledge graph, contradiction detection, and procedural learning. Ships as embeddable engine, network database, or MCP server. Runs locally from the yantrikdb-mcp Python package.