Is r3 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.9 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan60 source files scanned25/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 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/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 r3 does
- Redis MCP ServerRead-first Redis MCP: SCAN key explorer, keyspace/TTL/memory/slowlog stats, DBA advisornot reviewedGrowingB
- KEPTA — Agent MemoryLocal memory for AI agents. One SQLite file on your machine — no cloud, no account.not reviewedGrowingA
- Memory VaultLocal-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.not reviewedGrowingB