Agent Rescue
REMOTE · AGENT-RESCUE.VERCEL.APP · SCANNED SEP 22
Cross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 648 tokens (~216/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Agent Rescue MCP server?
Agent Rescue is a hosted endpoint at https://agent-rescue.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-rescue.vercel.app
claude mcp add --transport http santismm-agent-rescue 'https://agent-rescue.vercel.app/api/mcp'
{
"mcpServers": {
"santismm-agent-rescue": {
"url": "https://agent-rescue.vercel.app/api/mcp"
}
}
} {
"servers": {
"santismm-agent-rescue": {
"type": "http",
"url": "https://agent-rescue.vercel.app/api/mcp"
}
}
} [mcp_servers.santismm-agent-rescue] url = "https://agent-rescue.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"santismm-agent-rescue": {
"type": "remote",
"url": "https://agent-rescue.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add santismm-agent-rescue --url 'https://agent-rescue.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
santismm-agent-rescue:
url: "https://agent-rescue.vercel.app/api/mcp" {
"McpServers": {
"santismm-agent-rescue": {
"Transport": "http",
"Url": "https://agent-rescue.vercel.app/api/mcp"
}
}
} assistant mcp add santismm-agent-rescue -t streamable-http -u 'https://agent-rescue.vercel.app/api/mcp'
{
"mcpServers": {
"santismm-agent-rescue": {
"type": "http",
"url": "https://agent-rescue.vercel.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Sept 26 +55
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 8 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://agent-rescue.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-rescue.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-rescue.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agent-rescue.vercel.app/api/mcp | HTTPS enforced | 308 | https://agent-rescue.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_and_claim Check and claim ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Stable identifier for the action, e.g. 'invoice-2026-07-A491:pay'. |
| metadata | object | – | Small payload returned alongside the claim. Do not include secrets. |
| ttl_seconds | integer | – | How long the claim lasts, in seconds. Default 86400 (1 day), max 30 days. |
No output schema declared.
No examples provided.
fetch_structured Fetch a URL as structured JSON ~221
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | – | Optional. What exactly to look for if the page is ambiguous. |
| schema | object | yes | JSON Schema of the object you want back. Missing fields come back as null. |
| url | string | yes | Public http(s) URL. |
No output schema declared.
No examples provided.
request_capability Request a capability that does not exist ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional. What you tried and why it did not work. |
| deadline | string | – | Optional. ISO 8601. |
| need | string | yes | What exactly you need, in one or two sentences. Do not include personal data. |
| would_pay | boolean | – | Optional. Whether your policy allows paying to get this solved. Answer honestly: a false answer unlocks nothing and degrades the measurement. |
No output schema declared.
No examples provided.
What is the Agent Rescue MCP server?
Agent Rescue is an MCP server listed in the public MCP registry as io.github.santismm/agent-rescue. Cross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities. This page covers its hosted endpoint (https://agent-rescue.vercel.app/api/mcp).
Is the Agent Rescue MCP server safe to use?
Agent Rescue scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Rescue MCP server expose?
Agent Rescue exposes 3 tools: check_and_claim, fetch_structured, request_capability. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Does the Agent Rescue MCP server require authentication?
No. We connected to Agent Rescue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Rescue MCP server still maintained?
Agent Rescue is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.