Is RE-call MCP Memory Server MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.7 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scansource not scanned: tarball over 25MB25/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 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 80/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 RE-call MCP Memory Server does
- Echo MemoryShared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM.not reviewedGrowingA
- Memory VaultLocal-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.not reviewedGrowingB
- EngraphySelf-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.not reviewedNewB