Is VerifyAPI — fact-check with signed receipts 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.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan3 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 8 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 80/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 VerifyAPI — fact-check with signed receipts does
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB
VerifyAPI — fact-check with signed receipts reviews, tools and install