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/nousergon/mnemonWrote 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/nousergon/mnemon/mnemon-memory)<a href="https://agentmods.dev/mcp/nousergon/mnemon/mnemon-memory"><img src="https://agentmods.dev/badge/mcp/nousergon/mnemon/mnemon-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/nousergon/mnemon/mnemon-memory"><img src="https://agentmods.dev/badge/mcp/nousergon/mnemon/mnemon-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mnemon-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
{ "mnemon-memory": { "command": "uvx", "args": [ "mnemon-memory" ] } }
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 · 8 lines scan A bd5f7b433424
mnemon-memory is an MCP server published in the GitHub repository nousergon/mnemon (1 stars, last pushed 3d 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
aimem-mcp
Local-first, project-scoped MCP memory server for AI coding assistants. Runs locally from the aimem-mcp npm package.
memex
Zettelkasten-based agent memory system with bidirectional links. Runs locally from the @touchskyer/memex npm package. Needs 1 environment variable to run.
turbo-quant-memory
Local-first MCP memory server for AI coding agents with compact retrieval and project/global scopes. Runs locally from the turbo-quant-memory Python package. Needs 4 environment variables to run.
knowit
Shared team memory for AI coding agents — MCP server and CLI for persistent, queryable knowledge across sessions and teammates. Runs locally from the knowit npm package.
linksee-memory
Local-first cross-agent memory MCP. 6-layer WHY structure + AST file diff cache (86% savings). Runs locally from the linksee-memory npm package.
rememb
Persistent memory standard for AI agents — local, portable, zero config. Runs locally from the rememb Python package.