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/v1b3x0r/living-memory-engineWrote 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/v1b3x0r/living-memory-engine/living-memory)<a href="https://agentmods.dev/mcp/v1b3x0r/living-memory-engine/living-memory"><img src="https://agentmods.dev/badge/mcp/v1b3x0r/living-memory-engine/living-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/v1b3x0r/living-memory-engine/living-memory"><img src="https://agentmods.dev/badge/mcp/v1b3x0r/living-memory-engine/living-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
living-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
{ "living-memory": { "command": "npx", "args": [ "-y", "@nature-labs/lme-mcp" ], "env": {} } }
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 · 10 lines scan A c999fa1c2041
living-memory is an MCP server published in the GitHub repository v1b3x0r/living-memory-engine (2 stars, last pushed 25d ago), 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-31.
Other mcp servers, from other repositories
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.
freshvault
Local semantic search over your Obsidian vault - always fresh, never reindex. Runs locally from the freshvault npm package. Needs 1 environment variable to run.
local-recall-mcp
Fully local semantic memory for AI agents: search your notes and session logs from any MCP client, with embeddings served by Ollama. Runs locally from the local-recall-mcp Python package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
mcp
Memory the human governs, on their own machine, plus what other coding agents here wrote. Runs locally from the @mnemosyne_os/mcp npm package. Needs 3 environment variables to run.
lians_memory
MCP server "liansmemory" as configured in Lians-ai/Lians. Launched with lians-memory-mcp. Needs 11 environment variables to run.