RECOVER — Safe Next-Step Decisions After Machine Failures MCP Server

by gsterlingpress Your server? Claim it

answering

RECOVER — Safe Next-Step Decisions After Machine Failures is answering right now. Last checked 6 min ago. It exposes 1 tools. Last commit 14 Aug 2026.

Deterministic next-step decisions after failed API, MCP, automation, or AI-agent actions.

Uptime history 20 days of history

20 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

369 ms

Response time

average over 24h

Stars

last commit 14 Aug 2026

Nothing serious here today

Today is the operative word: we check RECOVER — Safe Next-Step Decisions After Machine Failures 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 6 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	349 ms	6 min ago

Alternatives to RECOVER — Safe Next-Step Decisions After Machine Failures

same job, measured the same way

Just MCP Server

by promptexecution

Expose curated Justfile recipes via MCP for safe deterministic automation.

local only

shaft-mcp

by shafthq

SHAFT browser automation, capture, and offline deterministic failure diagnosis

local only

Browser Agent

by runbook-ai

MCP server for browser automation with AI agent

247 installs/wk local only

Opsera

by opsera

Opsera AI Agent MCP server providing authenticated DevOps automation over SSE

10 tools answering

Uindow

by uindow

Real signed-browser automation for AI agents, over a local stdio MCP server.

1 266 installs/wk local only

State Memory MCP

by putervision

Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.

1 805 installs/wk local only

MCP Coda

by vish288

MCP server for Coda API — docs, pages, tables, rows, formulas, permissions, and automation.

474 installs/wk local only

Rewst MCP

by servosity

Operate and monitor Rewst RPA across every client org: automation health, failures, ROI, and drift.

local only

RECOVER — Safe Next-Step Decisions After Machine Failures — questions

Answers built from our own checks of this server.

What can RECOVER — Safe Next-Step Decisions After Machine Failures 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 — Safe Next-Step Decisions After Machine Failures working right now?

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

How do I connect RECOVER — Safe Next-Step Decisions After Machine Failures?

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 — Safe Next-Step Decisions After Machine Failures need an API key?

No. RECOVER — Safe Next-Step Decisions After Machine Failures 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 — Safe Next-Step Decisions After Machine Failures?

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

Is RECOVER — Safe Next-Step Decisions After Machine Failures open source?

Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.