mcpbeat Sign in

Agent Rescue MCP Server

answering

Agent Rescue is answering right now. Last checked 6 min ago. It exposes 3 tools.

Cross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities.

Uptime history 51 days of history · worst day 16%
51 days agonow
54.9%
Uptime 24h
50 of 91 checks
3
Tools
read from the server
610 ms
Response time
average over 24h
open, no key
Access
streamable-http

Agent Rescue does not always answer

Over the last week it answered 61.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

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.

run in your terminal
claude mcp add agent-rescue --transport http https://agent-rescue.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-rescue": {
      "url": "https://agent-rescue.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-rescue]
url = "https://agent-rescue.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-rescue": {
      "url": "https://agent-rescue.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-rescue": {
      "url": "https://agent-rescue.vercel.app/api/mcp"
    }
  }
}

Available tools 3

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

and
check_and_claim
Atomically check whether an action identified by a key was already performed, and claim it if not. Use it before performing a non-idempotent action that may have completed in an earlier attempt (a payment, a message, a write), or when you need to remember something across sessions. Returns 'claimed' if you are first and 'already_done' if not. Do not use it as a general data store or as a result cache.
request
request_capability
Record a specific need that none of the tools available to you can cover. Today it almost always answers that the capability is unavailable, and suggests alternatives only when they genuinely exist; its purpose is to measure what agents ask for and nobody serves. Use it when you are blocked by a missing capability — not for general questions, and not for anything you can work out by reasoning.
structured
fetch_structured
Fetch a public URL and return its content as JSON validated against the schema you pass. Use it when you need data from a page and cannot parse it reliably yourself. Do not use it for URLs requiring authentication or a session, for internal networks, or when you already have the content — extract it yourself in that case. `extracted_by` tells you where the answer came from: `structured_data` when the page already published it (JSON-LD, OpenGraph, or a JSON body — exact and free) or `model` when it had to be extracted from the text. If structured extraction is unavailable, the response carries `degraded: true`, `data: null` and the page `text` for you to parse: check `degraded` before reading `data`.

Endpoints

URLTransportStateLatencyChecked
https://agent-rescue.vercel.app/api/mcp streamable-http answering 249 ms 6 min ago

Alternatives to Agent Rescue

same job, measured the same way
Bristlecone Logic
by bristlecone2026

Micro-settled web content extraction and JSON schema validation utilities for AI agents via XRPL.

166 installs/wk local only
Regex/Email/URL Validator
by apished

Regex matching, email/URL format validation, and JSON Schema validation.

4 tools answering
I
CapabilityWire
by jawauntb

A live, curated feed of new AI agent capabilities across MCP, SDKs, models, and APIs.

4 tools answering
Agent JSON Reliability
by toninovo4249-ai

Deterministic inspect, safe repair, and JSON Schema validation for agent JSON. No LLM.

local only
C
Tern
by tern0

Resolve capability gaps: validate native MCPs, search live web, and record unmet demand.

3 tools answering
klanex
by chrassy

Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.

24 installs/wk 6 tools answering
Doc Extract MCP
by koraynar

Document tooling for AI agents: PDF/text reading, chunking, schema-validated JSON output.

local only
Dashclaw
by ucsandman

Policy checks, approvals, records, and governed HTTP capabilities for unattended agents.

63 installs/wk local only

Agent Rescue — questions

Answers built from our own checks of this server.

What can Agent Rescue do?
It exposes 3 tools, read directly from the server on our last check. Among them: check_and_claim, fetch_structured, request_capability. 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 Agent Rescue working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 50 of 91 checks got a reply (54.9%), average response time 610 ms. The bar chart above shows every period we have measured.
How do I connect Agent Rescue?
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 Agent Rescue need an API key?
No. Agent Rescue completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Rescue?
It answers our handshake in 610 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.