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/samrusani/AliceMemoryWrote 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/samrusani/alicememory/alice-memory-alice)<a href="https://agentmods.dev/mcp/samrusani/alicememory/alice-memory-alice"><img src="https://agentmods.dev/badge/mcp/samrusani/alicememory/alice-memory-alice/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/samrusani/alicememory/alice-memory-alice"><img src="https://agentmods.dev/badge/mcp/samrusani/alicememory/alice-memory-alice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
alice 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 13d 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
{
"alice": {
"command": "uvx",
"args": [
"--from",
"alice-memory==0.20.0",
"alice-memory",
"mcp",
"--data-dir",
"${user_config.data_dir}"
]
}
}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.
- 13d ago Changed 6731e2ad6526
- 14d ago Changed dea045c15813
- 16d ago First seen · 13 lines scan A b623a4272f51
alice is an MCP server published in the GitHub repository samrusani/AliceMemory (4 stars, last pushed today), 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-09-30.
Other mcp servers, from other repositories
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
homestead-memory
Verifiable, local-first AI memory that catches rot, tampering, and poisoning. Plain markdown you own. Runs locally from the homestead-memory Python package.
epiphany
One private, local memory your AI tools share. Cross-model, on-device, never lose a session. Runs locally from the epiphany-mcp npm package.
cortex
Patent-pending semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial. Remote server at skynetlab-cortex-saas-mcp.cortex-320.workers.dev.
peon-mem
Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt. Runs locally from the peon-mem npm package. Needs 1 environment variable to run.
sovseal-memory
Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads. Runs locally from the @sovseal/mcp-server npm package.