Is Engram MCP server safe?
Probably. Read the findings first.
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
- 65/100
- higher than 20% of 48,255 servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 6 read
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
2 medium
- Code scan45 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 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: …tress": "tsx bench/stress-test.ts", "postinstall": "node scripts/postinstall.mjs", "pr…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON