MCP server list / RECOVER — Safe Next-Step Decisions After Machine Failures
Deterministic next-step decisions after failed API, MCP, automation, or AI-agent actions.
Answered:
1 of 1 check
- Status
- responds
- Typical response time
- 90 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 90 ms.
- Address
- https://recover-api-production-bbba.up.railway.app/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.GSterlingPress/
recover - Transport
- streamable HTTP
streamable-http - Host
recover-api-production-bbba.up.railway.app
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- RECOVER
- Version:
- 0.1.2
- MCP features it lists:
- 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| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 90 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.