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.
npx agentmods add mcp/attilakiss9000/ember-memory/ember-memorygit clone --depth 1 https://github.com/attilakiss9000/ember-memoryWrote 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/attilakiss9000/ember-memory/ember-memory)<a href="https://agentmods.dev/mcp/attilakiss9000/ember-memory/ember-memory"><img src="https://agentmods.dev/badge/mcp/attilakiss9000/ember-memory/ember-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ember-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 3d 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
{ "ember-memory": { "command": "npx", "args": [ "-y", "ember-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.
- 3d ago First seen · 9 lines scan A a82345a0f59f
ember-memory is an MCP server published in the GitHub repository attilakiss9000/ember-memory (0 stars, last pushed 5mo 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
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.
mnemo-mcp
Open-source MCP Server for persistent AI memory with embedded sync. Runs locally from the mnemo-mcp Python package. Needs 1 environment variable to run.
weasley-deepmind
Secure, fragment-based long-term memory for MCP-compatible AI agents. Runs locally from the weasley-deepmind npm package. Needs 3 environment variables to run.
mcp-server
MCP server for MemoryPlugin API integration. Runs locally from the @memoryplugin/mcp-server npm package.
memory-lancedb-mcp
MCP server for LanceDB-backed long-term memory with hybrid retrieval (Vector + BM25), cross-encoder rerank, multi-scope isolation, and memory lifecycle management. Runs locally from the @cablate/memory-lancedb-mcp npm package.
motecloud-mcp-server
Cloud-hosted MCP server for durable AI memory. Remote server at motecloud.io.