Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Choose the safest next action after an API, MCP, or agent failure before retrying.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://recover-api-production-bbba.up.railway.app/mcpRun this in your terminal
claude mcp add --transport http recover https://recover-api-production-bbba.up.railway.app/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"recover": {
"url": "https://recover-api-production-bbba.up.railway.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"recover": {
"type": "http",
"url": "https://recover-api-production-bbba.up.railway.app/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://recover-api-production-bbba.up.railway.app/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 9, 2026. The maker wrote them, not us; we show them as plain text.
recover_decideUse 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_
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account GSterlingPress, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 408 ms (HTTP 200)
No sign-in needed
Read 1 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, phylokit-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Phylogenetic inference via IQ-TREE 3 — never returns a topology without its support
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A failed machine action happened. What should happen next?
RECOVER is a tiny deterministic decision API for AI agents, MCP clients, automations, and ordinary backend systems. It converts failure context into one of six actions:
RETRY_NOW · WAIT · REPAIR_REQUEST · VERIFY_FIRST · ESCALATE · ABORT
Use it immediately after a failed API/tool/action and before an automatic retry—especially for side-effecting operations, ambiguous timeouts, rate limits, malformed requests, exhausted retry budgets, and uncertain execution outcomes.
Base URL: https://recover-api-production-bbba.up.railway.app
MCP Streamable HTTP endpoint: https://recover-api-production-bbba.up.railway.app/mcp
Activity dashboard: https://recover-api-production-bbba.up.railway.app/activity
Safe demo: https://recover-api-production-bbba.up.railway.app/demo
POST https://recover-api-production-bbba.up.railway.app/v1/recover
{
"method":"POST", "status":503, "error":"upstream timeout", "attempt":1, "sideEffect":true, "idempotencyKey":false }
Example response:
{
"decision":"VERIFY_FIRST", "retry":false, "risk":"high", "reason":"A side-effecting non-idempotent action may have completed before the failure became visible.", "next":"Verify external state or obtain an idempotency key before retrying." }
Tool: recover_decide
Point an MCP client at:
https://recover-api-production-bbba.up.railway.app/mcp
The server is designed for machine discovery and includes server.json metadata for the official MCP Registry.
Retry libraries answer *how to retry*. RECOVER answers the more important question first: what is the safest next action after this specific failure?
Good call sites include API clients, AI agents, browser automations, workflow engines, MCP hosts, job runners, payment/order flows, and any system where blindly retrying can duplicate a side effect or amplify a failure.
GET /activity displays durable, privacy-safe usage telemetry and a permanent FIRST 10 REAL-WORLD STRANGER CONVERSIONS scoreboard. Real-use events are stored separately so discovery traffic cannot push milestones out of history. Raw IPs and request payloads are not stored.
The repo is Railway-ready with Dockerfile and railway.toml. Mount a persistent volume at /data so the permanent real-use ledger survives restarts.