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/caiowilson/MCP-mementoWrote 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/plugins/caiowilson/mcp-memento/memento)<a href="https://agentmods.dev/plugins/caiowilson/mcp-memento/memento"><img src="https://agentmods.dev/badge/plugins/caiowilson/mcp-memento/memento.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
memento 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "memento",
"displayName": "Memento MCP",
"version": "1.0.5",
"description": "Local-first repository context and durable memory through MCP",
"author": {
"name": "Memento MCP maintainers"
},
"homepage": "https://github.com/caiowilson/MCP-memento",
"repository": "https://github.com/caiowilson/MCP-memento",
"license": "MIT",
"keywords": ["mcp", "memory", "repository", "context"],
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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 · 16 lines scan A 1b5e78b5978d
memento is a plugin published in the GitHub repository caiowilson/MCP-memento (11 stars, last pushed 14d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
iai-memory
Persistent local memory for your assistant: every turn captured verbatim, relevant memory injected at session start and before each turn, and fourteen memory tools over MCP. Requires the iai-pme package (pip install iai-pme).
anytype-toolbox-skills
Agent Skills for Anytype setup, including a dedicated headless account for one LLM-sharing space, plus anyr and any-mcp workflows.
memem
Persistent, self-evolving memory for Claude Code. Local-first, no cloud, browsable Obsidian vault.
rag-rat
Local repo-intelligence index + MCP server: semantic search, symbol/graph navigation, impact-surface preflight, git + GitHub papertrail, and a source-anchored memory graph.
mcp
Read, write, search, and manage your Kept conversation vault.
captain-memo
Cross-AI local memory layer (Claude Code, Codex, Gemini, Cursor) — hybrid search, three summarizer providers, self-hosted embedder. Replaces claude-mem.