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/JJHbrams/Project-AMBERInstalling this writes the configuration, not the program: `__ENGRAM_BRIDGE_EXECUTABLE__` has to be on your PATH already, or the server will not start.
Wrote 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/jjhbrams/project-amber/claude-engram)<a href="https://agentmods.dev/mcp/jjhbrams/project-amber/claude-engram"><img src="https://agentmods.dev/badge/mcp/jjhbrams/project-amber/claude-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/jjhbrams/project-amber/claude-engram"><img src="https://agentmods.dev/badge/mcp/jjhbrams/project-amber/claude-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 14d 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": "__ENGRAM_BRIDGE_EXECUTABLE__",
"args": [
"--upstream-url",
"http://127.0.0.1:17385/mcp",
"--state-url",
"http://127.0.0.1:17384/state/mcp/events",
"--discovery-file",
"${USERPROFILE}/.engram/overlay-state-api-v1.json"
]
}
}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.
- 14d ago First seen · 13 lines scan A 00be20795296
engram is an MCP server published in the GitHub repository JJHbrams/Project-AMBER (2 stars, last pushed 14d 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-10-02.
Other mcp servers, from other repositories
penfield-mcp
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more. Remote server at mcp.penfield.app.
mengram
MCP server "mengram", hosted remotely at mengram.io, as configured in alibaizhanov/mengram.
obsidian-sync-mcp
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync. Runs locally from the obsidian-sync-mcp npm package. Needs 11 environment variables to run.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.