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/jnMetaCode/engramWrote 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/jnmetacode/engram/engram)<a href="https://agentmods.dev/mcp/jnmetacode/engram/engram"><img src="https://agentmods.dev/badge/mcp/jnmetacode/engram/engram/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/jnmetacode/engram/engram"><img src="https://agentmods.dev/badge/mcp/jnmetacode/engram/engram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
engram 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
{ "engram": { "command": "npx", "args": [ "-y", "@jnmetacode/engram" ] } }
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 · 9 lines scan A 7bc51389582f
engram is an MCP server published in the GitHub repository jnMetaCode/engram (4 stars, last pushed 1mo 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
memorylane
Agent-native memory layer — persistent context, semantic recall, session history, SDK, CLI, API, and MCP for AI agents and developers. Runs locally from the @talocode/memorylane npm package.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
knowl
Persistent memory for Claude Code, Cursor and Codex. Facts are typed, sourced, and retired when they change. Local SQLite, no API keys. Runs locally from the @dat999zx/knowl npm package.
turbo-quant-memory
Local-first MCP memory server for AI coding agents with compact retrieval and project/global scopes. Runs locally from the turbo-quant-memory Python package. Needs 4 environment variables to run.
atomicmemory
MCP server "atomicmemory" as configured in atomicstrata/atomicmemory. Runs locally from the atomicmemory-mcp npm package. Needs 7 environment variables to run.