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/kindledflamestudios/ember-memory/claude_code-ember-memorygit clone --depth 1 https://github.com/KindledFlameStudios/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/kindledflamestudios/ember-memory/claude_code-ember-memory)<a href="https://agentmods.dev/mcp/kindledflamestudios/ember-memory/claude_code-ember-memory"><img src="https://agentmods.dev/badge/mcp/kindledflamestudios/ember-memory/claude_code-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": "python3",
"args": [
"-c",
"import sys; sys.path.insert(0, '${CLAUDE_PLUGIN_ROOT}'); from ember_memory.server import mcp; mcp.run(transport='stdio')"
],
"env": {
"EMBER_AI_ID": "claude"
}
}
}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 · 12 lines scan A bbe16905ee3b
ember-memory is an MCP server published in the GitHub repository KindledFlameStudios/ember-memory (2 stars, last pushed 2mo 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
mcp-broker
Local MCP broker for sharing upstream MCP servers across MCP clients. Runs locally from the mcp-broker Python package.
living-memory
An MCP memory server. One memory your agents share — across models, devices and apps. Runs locally from the @nature-labs/lme-mcp npm package.
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.
taskgrade
Local task classification for coding-agent model selection. Runs locally from the taskgrade npm package.
mindmap
Mind Map — a memory consolidation / context-handoff MCP server. Capture context from any AI tool, resume it anywhere, and let it decay gracefully. Runs locally from the @ravi-labs/mindmap-mcp-server npm package.
mindmap-mcp-server
Local-first memory & context-handoff across AI tools — capture in one, resume in another. No cloud. Runs locally from the @ravi-labs/mindmap-mcp-server npm package.