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/kael-bit/engram-rs/engramgit clone --depth 1 https://github.com/kael-bit/engram-rsWrote 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/kael-bit/engram-rs/engram)<a href="https://agentmods.dev/mcp/kael-bit/engram-rs/engram"><img src="https://agentmods.dev/badge/mcp/kael-bit/engram-rs/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 5d 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",
"engram-rs-mcp"
],
"env": {
"ENGRAM_URL": "",
"ENGRAM_API_KEY": ""
}
}
}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.
- 5d ago First seen · 13 lines scan A c8294d8533de
engram is an MCP server published in the GitHub repository kael-bit/engram-rs (27 stars, last pushed 6mo 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-30.
Other mcp servers, from other repositories
mcp
AI memory engine exposed as an MCP server. Runs locally from the @openmem/mcp npm package.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
logic-server
Agent reasoning, memory, and token-optimized context for AI applications. Runs locally from the nocturnusai-mcp npm package. Needs 4 environment variables to run.
cortex
Patented semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial. Remote server at skynetlab-cortex-saas-mcp.cortex-320.workers.dev.
agentmemory
Standalone MCP server for agentmemory — thin shim that re-exposes @agentmemory/agentmemory's MCP entrypoint. Runs locally from the @agentmemory/mcp npm package. Needs 3 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.