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/zircote/rlm-rsWrote 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/zircote/rlm-rs/memory)<a href="https://agentmods.dev/mcp/zircote/rlm-rs/memory"><img src="https://agentmods.dev/badge/mcp/zircote/rlm-rs/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/zircote/rlm-rs/memory"><img src="https://agentmods.dev/badge/mcp/zircote/rlm-rs/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 today.
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.
This is a copy
92% identical to memory — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 3. 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.
- today First seen · 9 lines scan A 2ab64fbe22b4
memory is an MCP server published in the GitHub repository zircote/rlm-rs (60 stars, last pushed yesterday), 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. It is 92% identical to memory, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
agent-memory
Git-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe. Runs locally from the @xchucx/agent-memory npm package.
memento
Local-first, LLM-agnostic memory layer for AI assistants. Runs locally from the @psraghuveer/memento npm package. Needs 1 environment variable to run.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.
shaddai-aura
AURA — a tiny, dependency-free token saver. Answers prompts from a local cache, saved skills, or deterministic compute, and distills bloated system prompts, so you call (and pay for) the LLM far less. Use it as a CLI, a library, or an MCP server for Claud. Runs locally from the shaddai-aura npm package.
obsidian-mcp-guard
MCP server for agent-safe Obsidian vault access with lint validation. Runs locally from the obsidian-mcp-guard Python package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.