RECOVER — Decide Safely After a Failed Machine Action MCP Server

by gsterlingpress Your server? Claim it

answering

RECOVER — Decide Safely After a Failed Machine Action is answering right now. Last checked 8 min ago. It exposes 1 tools. Last commit 13 Sep 2026.

Choose the safest next action after an API, MCP, or agent failure before retrying.

Uptime history 66 days of history · worst day 98%

66 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

399 ms

Response time

average over 24h

Stars

last commit 13 Sep 2026

Nothing serious here today

Today is the operative word: we check RECOVER — Decide Safely After a Failed Machine Action every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add recover --transport http https://recover-api-production-bbba.up.railway.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "recover": {
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.recover]
url = "https://recover-api-production-bbba.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "recover": {
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "recover": {
      "url": "https://recover-api-production-bbba.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recover

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 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.

Endpoints

URL	Transport	State	Latency	Checked
https://recover-api-production-bbba.up.railway.app/mcp	streamable-http	answering	369 ms	8 min ago

Alternatives to RECOVER — Decide Safely After a Failed Machine Action

same job, measured the same way

VERAX

by verax-ai

The body an agent asks before it acts: decide, approve, and keep a signed record on your machine.

1 105 installs/wk local only

Failecho

by failecho

Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.

205 installs/wk 4 tools answering

Tersign Evidence

by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

743 installs/wk local only

Kaval

by usekaval

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

112 installs/wk local only

Kaval

by lufemc

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

local only

Merchant Context

by ihint

Resolve sourced merchant facts and safe actions before an agent acts.

9 tools answering

Clair

by meetclair

Sell-side agent for retail: one typed waitlist transaction plus read-only machine manifests.

3 tools answering

ai.confess.online

by confess

Machines share their truth. Confessions made by AI agents: text, a picture, a recording or a film.

8 tools answering

RECOVER — Decide Safely After a Failed Machine Action — questions

Answers built from our own checks of this server.

What can RECOVER — Decide Safely After a Failed Machine Action do?

It exposes 1 tools, read directly from the server on our last check. Among them: recover_decide. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RECOVER — Decide Safely After a Failed Machine Action working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 399 ms. The bar chart above shows every period we have measured.

How do I connect RECOVER — Decide Safely After a Failed Machine Action?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RECOVER — Decide Safely After a Failed Machine Action need an API key?

No. RECOVER — Decide Safely After a Failed Machine Action completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RECOVER — Decide Safely After a Failed Machine Action?

It answers our handshake in 399 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is RECOVER — Decide Safely After a Failed Machine Action open source?

We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.