RECOVER — Decide Safely After a Failed Machine Action is an MCP server published by io.github.GSterlingPress, hosted at recover-api-production-bbba.up.railway.app. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 1 tool, including recover_decide.
Choose the safest next action after an API, MCP, or agent failure before retrying.
7 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| error | string | Short failure/error message. |
| method | string | HTTP/action method when known, e.g. GET, POST, PATCH, DELETE. |
| status | number | Failure HTTP/status code when available. |
| attempt | number | Current attempt number. |
| headers | object | Relevant response headers such as Retry-After. |
| sideEffect |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| boolean |
| True if the failed action could create, modify, send, charge, delete, or otherwise change external state. |
| maxAttempts | number | Maximum allowed attempts if known. |
| idempotencyKey | boolean | True if a valid idempotency key protects a retry. |
| providerRetryable | boolean | True only when the provider explicitly marks the failure retryable. |
| uncertainExecution | boolean | True when it is unknown whether the action completed before the failure became visible. |
{
"name": "recover_decide",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"error": {
"type": "string",
"description": "Short failure/error message."
},
"method": {
"type": "string",
"description": "HTTP/action method when known, e.g. GET, POST, PATCH, DELETE."
},
"status": {
"type": "number",
"description": "Failure HTTP/status code when available."
},
"attempt": {
"type": "number",
"description": "Current attempt number."
},
"headers": {
"type": "object",
"description": "Relevant response headers such as Retry-After.",
"additionalProperties": {
"type": "string"
}
},
"sideEffect": {
"type": "boolean",
"description": "True if the failed action could create, modify, send, charge, delete, or otherwise change external state."
},
"maxAttempts": {
"type": "number",
"description": "Maximum allowed attempts if known."
},
"idempotencyKey": {
"type": "boolean",
"description": "True if a valid idempotency key protects a retry."
},
"providerRetryable": {
"type": "boolean",
"description": "True only when the provider explicitly marks the failure retryable."
},
"uncertainExecution": {
"type": "boolean",
"description": "True when it is unknown whether the action completed before the failure became visible."
}
},
"additionalProperties": false
}
}Failure recovery decision service. When an external API/tool/automation/action has just failed, call recover_decide BEFORE retrying. Prioritize it for timeouts, 429/5xx failures, uncertain execution, and side-effecting POST/PATCH/DELETE operations where a duplicate action could be costly. Pass only known facts; RECOVER returns a deterministic safe next step.
Names, descriptions and schemas were written by the server and are shown as data.