English Français العربية

RECOVER — Decide Safely After a Failed Machine Action

Official registry AI and agents

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http recover-decide-safely-after-a-failed-mac 'https://recover-api-production-bbba.up.railway.app/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "recover-decide-safely-after-a-failed-mac": {
            "type": "http",
            "url": "https://recover-api-production-bbba.up.railway.app/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. RECOVER
  2. Live production
  3. REST
  4. MCP
  5. Why call RECOVER?
  6. Analytics
  7. Deploy

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:

RETRY_NOW · WAIT · REPAIR_REQUEST · 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.

Frequently asked questions

What is RECOVER — Decide Safely After a Failed Machine Action?

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

How do I install RECOVER — Decide Safely After a Failed Machine Action?

It runs as a remote server. In Claude Code: claude mcp add --transport http recover-decide-safely-after-a-failed-mac 'https://recover-api-production-bbba.up.railway.app/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does RECOVER — Decide Safely After a Failed Machine Action need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is RECOVER — Decide Safely After a Failed Machine Action open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains RECOVER — Decide Safely After a Failed Machine Action?

It is published by GSterlingPress. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.