Skip to main content

RECOVER — Decide Safely After a Failed Machine Action

io.github.GSterlingPress/recoverVersion 0.1.3

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

Status

Responds332 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:37 UTC
Latency
332 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://recover-api-production-bbba.up.railway.app/mcpResponds332 ms
No sign-in

Claude Code

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

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: recover
Remote MCP server URL: https://recover-api-production-bbba.up.railway.app/mcp

Cursor

{
  "mcpServers": {
    "recover": {
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"recover","type":"http","url":"https://recover-api-production-bbba.up.railway.app/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

1 tools

Tools of RECOVER — Decide Safely After a Failed Machine Action
Read-only
Idempotent
Open world
recover_decideUse 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.Not declaredNot declaredNot declaredNot declared