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/verygoodplugins/claude-pluginsWrote 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/verygoodplugins/claude-plugins/automem-memory)<a href="https://agentmods.dev/mcp/verygoodplugins/claude-plugins/automem-memory"><img src="https://agentmods.dev/badge/mcp/verygoodplugins/claude-plugins/automem-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/verygoodplugins/claude-plugins/automem-memory"><img src="https://agentmods.dev/badge/mcp/verygoodplugins/claude-plugins/automem-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 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
{
"memory": {
"command": "npx",
"args": [
"-y",
"@verygoodplugins/mcp-automem"
],
"env": {
"AUTOMEM_ENDPOINT": "${AUTOMEM_ENDPOINT:-http://127.0.0.1:8001}"
}
}
}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 · 12 lines scan A 1f14f7ee4f95
memory is an MCP server published in the GitHub repository verygoodplugins/claude-plugins (2 stars, last pushed 8mo 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
mem-search
MCP server "mem-search" as configured in maxritter/pilot-shell. Launched with sh -c bun run ~/.pilot/scripts/mcp-server.cjs.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
lethe
Context garbage collector for long-running LLM agents — offload and recall to save tokens (Claude Code & Codex via MCP). Runs locally from the lethe-llm-context Python package. Needs 1 environment variable to run.
thought-mcp
THOUGHT — Temporal Hierarchical Object Union & Graph Hybrid Toolkit. A local MCP memory server with bi-temporal graph + vector + temporal layers, a query router, and a consolidation engine. Runs locally from the thought-mcp Python package.
mnemonic-memory
AI Memory MCP Server - Persistent memory management for Claude and other AI assistants. Runs locally from the mnemonic-memory Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.