Is RECOVER — Decide Safely After a Failed Machine Action 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 scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 295ms20/20
- Tool poisoning1 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 88/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 RECOVER — Decide Safely After a Failed Machine Action does
- MCPAuthorize consequential AI agent actions before executionnot reviewedEstablishedA
- ProjectmemCoding agent memory — one local MCP server for every project. Warns before repeating failed fixes.not reviewedGrowingA
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA
RECOVER — Decide Safely After a Failed Machine Action reviews, tools and install