NestDaddy

RECOVER — Decide Safely After a Failed Machine Action

io.github.GSterlingPress/recover · v0.1.3

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

Connect Remote server

Terminal
claude mcp add --transport http recover https://recover-api-production-bbba.up.railway.app/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "recover": {
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "recover": {
      "type": "http",
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://recover-api-production-bbba.up.railway.app/mcp

Tools 1 found in our last check

  • recover_decide

    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…

Details

Endpointhttps://recover-api-production-bbba.up.railway.app/mcp (Streamable HTTP)
First published13 Sep 2026
Last updated13 Sep 2026
Registry nameio.github.GSterlingPress/recover

More ai and media servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.