RECOVER — Decide Safely After a Failed Machine Action MCP server
Choose the safest next action after an API, MCP, or agent failure before retrying.
0 stars
Reviews
Write oneNobody has reviewed RECOVER — Decide Safely After a Failed Machine Action yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
RECOVER — Decide Safely After a Failed Machine Action tools (1)
write = sends, deletes, buys or postsrecover_decideFreeUse immediately after an API, MCP tool, automation, or agent action fails and before retrying. Especially use after timeouts, 5xx/429 responses, uncertain execution, or any side-effecting action that may already have completed. Returns the safest deterministic next action: RETRY_NOW, WAIT, REPAIR_REQUEST, VERIFY_FIRST, ESCALATE, or ABORT. Do not use before an action or for successful actions.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
- –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
Install directly
claude mcp add --transport http recover https://recover-api-production-bbba.up.railway.app/mcp
RECOVER — Decide Safely After a Failed Machine Action: common questions
- Is RECOVER — Decide Safely After a Failed Machine Action MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the RECOVER — Decide Safely After a Failed Machine Action safety report
- How do I install RECOVER — Decide Safely After a Failed Machine Action?
- It runs remotely at recover-api-production-bbba.up.railway.app. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does RECOVER — Decide Safely After a Failed Machine Action need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is RECOVER — Decide Safely After a Failed Machine Action maintained?
- The last commit was 6 days ago (2026-09-13). The latest release is v0.1.3.
- Is RECOVER — Decide Safely After a Failed Machine Action up?
- 100% of our last 1 checks got an answer. We check remote servers about four times a day.
- What can I use instead of RECOVER — Decide Safely After a Failed Machine Action?
- Servers from other publishers that do the same job: MCP server, Projectmem MCP server and Agent-Native Chat MCP server. Compare all RECOVER — Decide Safely After a Failed Machine Action alternatives.
Alternatives to RECOVER — Decide Safely After a Failed Machine Action
Same job from other publishers: the closest match first, then the best rated.
- 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
- GitWarrenCode review on your own machine, for you and your coding agent. Nothing leaves your computer.not reviewedEstablishedA
- LockstepDecision memory for AI coding agents: captures decisions once, briefs every agent before it acts.not reviewedGrowingA