Is Engram MCP server safe?

Probably. Read the findings first.

C68/100grade C

Use with care. Some checks failed or could not be verified.

How Engram compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 68/100; higher than 30% of 48,243 servers
Tools that change things: 67%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read · 2 change

Release history: 2 versions in the registry since 2026-09-18, latest 2026-09-21, typically one every 3 days.

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

2 medium

Code scan263 source files scanned15/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 17 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

mediumnpm install lifecycle script presentinstall.script

package.json: …npm run build && npm run test:run", "postinstall": "node scripts/preflight.cjs", "vers…

Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
not reviewed
Widely used
C
Neo4j Memory
MCP Neo4j Knowledge Graph Memory Server
not reviewed
Established
A
Deja Vu
deja-vu: local memory over the session histories of forty-three coding agents.
not reviewed
Established
A