MCP.Market

RECOVER — Decide Safely After a Failed Machine Action MCP server

online · 100% uptime
by GSterlingPress·io.github.GSterlingPress/recover·v0.1.3
No reviews yet

Choose the safest next action after an API, MCP, or agent failure before retrying.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody 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 posts
  • recover_decideFree

    Use 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.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 366ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 20 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

How RECOVER — Decide Safely After a Failed Machine Action compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 4,460 AI and agents servers
Tools
1
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
358 ms
faster than 39% of 2,331 AI and agents servers

What its tools let an agent do: 1 read

Install RECOVER — Decide Safely After a Failed Machine Action in Claude Code, Cursor or VS Code

claude mcp add --transport http recover https://recover-api-production-bbba.up.railway.app/mcp
Add to Cursor

What the publisher says

From the RECOVER — Decide Safely After a Failed Machine Action repository's README, as published. We do not edit it. Read it on GitHub

RECOVER

A failed machine action happened. What should happen next?

RECOVER is a tiny deterministic decision API for AI agents, MCP clients, automations, and ordinary backend systems. It converts failure context into one of six actions:

RETRYNOW · WAIT · REPAIRREQUEST · VERIFY_FIRST · ESCALATE · ABORT

Use it immediately after a failed API/tool/action and before an automatic retry—especially for side-effecting operations, ambiguous timeouts, rate limits, malformed requests, exhausted retry budgets, and uncertain execution outcomes.

Live production

Base URL: https://recover-api-production-bbba.up.railway.app

MCP Streamable HTTP endpoint: https://recover-api-production-bbba.up.railway.app/mcp

Activity dashboard: https://recover-api-production-bbba.up.railway.app/activity

Safe demo: https://recover-api-production-bbba.up.railway.app/demo

REST

POST https://recover-api-production-bbba.up.railway.app/v1/recover

{
  "method":"POST",
  "status":503,
  "error":"upstream timeout",
  "attempt":1,
  "sideEffect":true,
  "idempotencyKey":false
}

Example response:

{
  "decision":"VERIFY_FIRST",
  "retry":false,
  "risk":"high",
  "reason":"A side-effecting non-idempotent action may have completed before the failure became visible.",
  "next":"Verify external state or obtain an idempotency key before retrying."
}

MCP

Tool: recover_decide

Point an MCP client at:

https://recover-api-production-bbba.up.railway.app/mcp

The server is designed for machine discovery and includes server.json metadata for the official MCP Registry.

Why call RECOVER?

Retry libraries answer how to retry. RECOVER answers the more important question first: what is the safest next action after this specific failure?

Good call sites include API clients, AI agents, browser automations, workflow engines, MCP hosts, job runners, payment/order flows, and any system where blindly retrying can duplicate a side effect or amplify a failure.

Analytics

GET /activity displays durable, privacy-safe usage telemetry and a permanent FIRST 10 REAL-WORLD STRANGER CONVERSIONS scoreboard. Real-use events are stored separately so discovery traffic cannot push milestones out of history. Raw IPs and request payloads are not stored.

Deploy

The repo is Railway-ready with Dockerfile and railway.toml. Mount a persistent volume at /data so the permanent real-use ledger survives restarts.

Nothing above is checked by us. What we check is on the safety report.

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, Cursor, VS Code or Claude Desktop 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 52 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 28 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: Decionis MCP server, Agent-Native Chat MCP server and Emilia Protocol MCP server.
How does RECOVER — Decide Safely After a Failed Machine Action compare with other AI and agents MCP servers?
safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 1 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to RECOVER — Decide Safely After a Failed Machine Action

Same job from other publishers: the closest match first, then the best rated.

  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    More from nirholas →
    B

More from GSterlingPress →