RECOVER — Decide Safely After a Failed Machine Action
mcp remote · streamable-http · v0.1.3 · source: crawl
https://recover-api-production-bbba.up.railway.app/mcp
https://github.com/GSterlingPress/recover-api
Choose the safest next action after an API, MCP, or agent failure before retrying.
Works
100
Verified Oct 31, 2026 · p50 778 ms · p95 833 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'RECOVER' |
| tools_listed | 15 | pass | 1 tools |
| schema_complete | 15 | pass | 1 of 1 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 778 ms |
| latency_p95 | 5 | pass | p95 833 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (1)
| Name | Description | Schema |
|---|---|---|
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 | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/io-github-gsterlingpress-recover)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.