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/alphaonedev/ai-memory-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/alphaonedev/ai-memory-mcp/ai-memory)<a href="https://agentmods.dev/mcp/alphaonedev/ai-memory-mcp/ai-memory"><img src="https://agentmods.dev/badge/mcp/alphaonedev/ai-memory-mcp/ai-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/alphaonedev/ai-memory-mcp/ai-memory"><img src="https://agentmods.dev/badge/mcp/alphaonedev/ai-memory-mcp/ai-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ai-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
{
"ai-memory": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/alphaonedev/ai-memory:0.5.1"
],
"env": {
"AI_MEMORY_DB": ""
}
}
}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 · 14 lines scan A ee5f37cc165b
ai-memory is an MCP server published in the GitHub repository alphaonedev/ai-memory-mcp (54 stars, last pushed today), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.
xmemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST. Runs locally from the @xmemo/client npm package. Needs 2 environment variables to run.
inspeximus
MCP server "inspeximus", hosted remotely at pypi.org, as configured in DanceNitra/inspeximus. Needs 1 environment variable to run.
goodmem
GoodMem MCP server — exposes GoodMem API as MCP tools. Runs locally from the @pairsystems/goodmem-mcp npm package.
memoweft
Portable AI memory as MCP tools: five reads and three controlled writes. Runs locally from the @memoweft/mcp-server npm package. Needs 1 environment variable to run.
membrain
Self-hosted AI memory ledger. You and your agents share one memory store over MCP — one SQLite file, web UI, REST, works offline. Runs locally from the membrain-mcp npm package.