Is License Flip Audit 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.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan5 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 qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 89/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 License Flip Audit does
- JanuscopeLocal MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.not reviewedGrowingA
- Redis MCP ServerRead-first Redis MCP: SCAN key explorer, keyspace/TTL/memory/slowlog stats, DBA advisornot reviewedGrowingB
r3Local Redis memory MCP for AI apps with hybrid caching and optional Mem0 cloud backup.not reviewedGrowingB