External endpointresponds
RECOVER — Safe Next-Step Decisions After Machine Failures
Deterministic next-step decisions after failed API, MCP, automation, or AI-agent actions.
Endpoint URL
https://recover-api-production-bbba.up.railway.app/mcpCurrent status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
90 ms
Response record
1 of 1 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.GSterlingPress/recover
Current observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- RECOVER
- Version
- 0.1.2
- Capability keys
- tools
- Tool names
- recover_decide
Instructions excerpt
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.
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 90ms