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/nickcirv/engram/engram-engramgit clone --depth 1 https://github.com/NickCirv/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/nickcirv/engram/engram-engram)<a href="https://agentmods.dev/mcp/nickcirv/engram/engram-engram"><img src="https://agentmods.dev/badge/mcp/nickcirv/engram/engram-engram.svg" alt="Measured on agentmods" 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- engram — 100% identical, 0 lines differ
What it actually says
{
"engram": {
"command": "engram-serve",
"args": [
"${CLAUDE_PROJECT_DIR}"
],
"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.
- 6d ago First seen · 9 lines scan A b5cfaa3f3dfa
engram is an MCP server published in the GitHub repository NickCirv/engram (141 stars, last pushed 2mo 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-30.
Other mcp servers, from other repositories
chatcrystal
Local-first AI PKM memory for coding conversations. Runs locally from the chatcrystal npm package. Needs 2 environment variables to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
nexus-memory
DEPRECATED: This package has been renamed to smriti-memcore. Please use 'smriti-memcore' instead. Runs locally from the nexus-memory Python package.
forensic-deepdive
Forensic deep-dive of any codebase (9 languages). Persistent code knowledge graph + MCP server (9 composite tools incl. hybrid NL query, Mermaid export & cross-stack trace) for AI coding agents, with 5 durable markdown artifacts (MAP, HOTPATHS, ARCHAEOLOGY, MENTALMODEL, AGENTBRIEF) as the human-readable projection.…
fish-bridge-mcp
Session-scoped knowledge graph engine for AI chat context compression. Runs locally from the fish-bridge-mcp Python package. Needs 3 environment variables to run.
mcp-server
Expert-curated knowledge, brand, research & earnings intelligence — 47 tools, 220+ graphs. Runs locally from the fodda-mcp npm package. Needs 2 environment variables to run.