Is rag-rat 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.3 · 2026-09-19 · same rubric, same numbers if you re-run it
2 medium
- Code scan6 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 owner7/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: …check": "prettier --check **/*.js", "postinstall": "node ./install.js" }, "supportedPl…
Overall 75/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 rag-rat does
- Google SurfWeb, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.not reviewedEstablishedC
- ProjectmemCoding agent memory — one local MCP server for every project. Warns before repeating failed fixes.not reviewedGrowingA
- BomlyGive your coding agent the dependency graph it is about to change: scan, diff, explain, auditnot reviewedGrowingB