io.github.GSterlingPress/recover
RECOVER — Decide Safely After a Failed Machine Action
Choose the safest next action after an API, MCP, or agent failure before retrying.
timeout probed 2026-10-15
fetch failed | Connect Timeout Error (attempted address: recover-api-production-bbba.up.railway.app:443, timeout: 10000ms) | UND_ERR_CONNECT_TIMEOUT
- Endpoint
- https://recover-api-production-bbba.up.railway.app/mcp (streamable-http)
- Host
- recover-api-production-bbba.up.railway.app
- Repository
- https://github.com/GSterlingPress/recover-api
- Website
- https://github.com/GSterlingPress/recover-api
- Registry
- active, updated 2026-09-13 · registry entry
- Reachable
- 6 of the last 6 probes
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-05 14:18 | alive | 678 ms | 1 | 597 | 325 |
| 2026-10-05 00:29 | alive | 297 ms | 1 | 325 | |
| 2026-10-04 10:02 | alive | 495 ms | 1 | 325 | |
| 2026-10-04 07:55 | alive | 406 ms | 1 | 325 | |
| 2026-10-03 20:35 | alive | 384 ms | 1 | 325 | |
| 2026-10-03 17:51 | alive | 487 ms | 1 | 325 |
Badge and feed
[](https://mcpcost.ulehla.dev/s/io.github.GSterlingPress/recover)
An entry for every probe that changed the result, the tool count or the token cost: Atom feed. Add it to a feed reader or a Slack RSS app to hear when the server stops answering or its tool set grows.