Is Remem 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.
How Remem compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 40% of 802 Databases servers
Release history: 3 versions in the registry since 2026-09-08, latest 2026-10-08, typically one every 18 days.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
2 medium
- Code scan2 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 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 (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: … "bin/remem.js" }, "scripts": { "postinstall": "node scripts/install.js", "test": …
Overall 77/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 Remem does
- Memory ArbiterLocal SQLite MCP memory: evidence-based recall, advisory conflict notices, authorized governance.not reviewedGrowingA
- CludePortable agent memory anchored on Solana. Local SQLite + vector recall, open export.not reviewedGrowingB
- open-memexLocal-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.not reviewedGrowingB