Is Sovereignty Scan 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-27 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 115ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (unknown)9/15
- Maintenancelast push 18 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/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 Sovereignty Scan does
- Healthclaw GuardrailsGuardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolationnot reviewedGrowingA
- KastellServer security audit (413 checks), hardening, and fleet management across 4 cloud providers.not reviewedGrowingB
- BastionReliability + security proxy for MCP: runtime tool-security and a compliance-mapped audit trail.not reviewedGrowingA