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/GhostyAI-HA/ERINYS-memWrote 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/ghostyai-ha/erinys-mem/erinys-memory)<a href="https://agentmods.dev/mcp/ghostyai-ha/erinys-mem/erinys-memory"><img src="https://agentmods.dev/badge/mcp/ghostyai-ha/erinys-mem/erinys-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/ghostyai-ha/erinys-mem/erinys-memory"><img src="https://agentmods.dev/badge/mcp/ghostyai-ha/erinys-mem/erinys-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
erinys-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 10d 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
{ "erinys-memory": { "command": "uvx", "args": [ "erinys-memory" ] } }
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.
- 10d ago First seen · 8 lines scan A e4f2dd23602c
erinys-memory is an MCP server published in the GitHub repository GhostyAI-HA/ERINYS-mem (5 stars, last pushed 13d 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
long-term-memory
Long-term memory system for AI assistants — persistent, searchable, self-organizing memory powered by semantic search, knowledge graphs, and reinforcement learning. Runs locally from the long-term-memory Python package.
memora
MCP server "memora" as configured in agentic-box/memora. Launched with memora-server. Needs 3 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
neurostack
Token-efficient MCP memory for Markdown vaults. Tiered retrieval, hybrid search, GraphRAG. Runs locally from the neurostack npm package. Needs 1 environment variable to run.
obsidian-everywhere
Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults. Runs locally from the obsidian-everywhere npm package.
memory
MCP server "memory", hosted remotely at memory.studiomeyer.io, as configured in studiomeyer-io/studiomeyer-memory.