Is memo 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.
How memo compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 65% of 802 Databases servers
- Tools that change things
- 0%
- typical: 9%. Fewer write tools means less an agent can break
What its tools let an agent do: 1 read
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
1 medium
- Code scan566 source files scanned20/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 qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumeval / new Function used
exec.evalmlx_memo-4.16.0/src/memo/cli_dream_passes.py: … -> dict: """Nightly retrieval-only eval (vec mode, no reranker — the same fast pa…
Overall 85/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 memo does
- Local MemoryPersistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys.not reviewedGrowingA
- LoreConvoLocal-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.not reviewedGrowingB
- lean-memoryEmbedded, local-first agent memory: one SQLite file per namespace, no server, no cloud.not reviewedGrowingA
