Is Echo Memory MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan80 source files scanned25/25
- Live reliabilityremote reachable in 889ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (bearer)9/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Echo Memory does
- RE-call MCP Memory ServerAgent memory on your own Postgres that flags superseded facts and abstains instead of guessing.not reviewedGrowingB
- EngraphySelf-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.not reviewedNewB
- Memory VaultLocal-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.not reviewedGrowingB