Agent Rescue Desk Production Triage
REMOTE · AGENT-RESCUE-DESK.NETLIFY.APP · SCANNED SEP 20
Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 206 tokens (~68/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Desk Production Triage MCP server?
Agent Rescue Desk Production Triage is a hosted endpoint at https://agent-rescue-desk.netlify.app/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-desk.netlify.app
claude mcp add --transport http app-netlify-agent-rescue-desk-production-triage 'https://agent-rescue-desk.netlify.app/mcp'
{
"mcpServers": {
"app-netlify-agent-rescue-desk-production-triage": {
"url": "https://agent-rescue-desk.netlify.app/mcp"
}
}
} {
"servers": {
"app-netlify-agent-rescue-desk-production-triage": {
"type": "http",
"url": "https://agent-rescue-desk.netlify.app/mcp"
}
}
} [mcp_servers.app-netlify-agent-rescue-desk-production-triage] url = "https://agent-rescue-desk.netlify.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-netlify-agent-rescue-desk-production-triage": {
"type": "remote",
"url": "https://agent-rescue-desk.netlify.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-netlify-agent-rescue-desk-production-triage --url 'https://agent-rescue-desk.netlify.app/mcp' --transport streamable-http
mcp_servers:
app-netlify-agent-rescue-desk-production-triage:
url: "https://agent-rescue-desk.netlify.app/mcp" {
"McpServers": {
"app-netlify-agent-rescue-desk-production-triage": {
"Transport": "http",
"Url": "https://agent-rescue-desk.netlify.app/mcp"
}
}
} assistant mcp add app-netlify-agent-rescue-desk-production-triage -t streamable-http -u 'https://agent-rescue-desk.netlify.app/mcp'
{
"mcpServers": {
"app-netlify-agent-rescue-desk-production-triage": {
"type": "http",
"url": "https://agent-rescue-desk.netlify.app/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.
- 27 Aug 26 +68
- Authorization: unverified → partial ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: pass functional
- 26 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
- 22 Aug 26 20
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.83 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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
- 31 Jul 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- Tool “describe_rescue_offer” changed its title: Describe the 48-Hour Agent Rescue → Describe the 12-Hour Agent Rescue cosmetic
- 27 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://agent-rescue-desk.netlify.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-rescue-desk.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-rescue-desk.netlify.app/mcp | Verified | 200 | |
| http (plaintext) | http://agent-rescue-desk.netlify.app/mcp | HTTPS enforced | 301 | https://agent-rescue-desk.netlify.app/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 →
describe_rescue_offer Describe the 12-Hour Agent Rescue ~41
Returns the exact scope, price, service window, acceptance rules, private fit-review URL, and direct x402 purchase URL for the Agent Rescue Desk service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_case_intake_requirements Get Rescue Case Intake Requirements ~39
Returns the minimum redacted evidence needed for a fixed-scope fit review and the public intake URL. It does not submit a case.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
triage_production_failure Triage an AI Workflow Production Failure ~72
Classifies one sanitized n8n, MCP, webhook, agent-tool-routing, retry, or general production incident and returns concrete next checks without echoing the submitted incident.
| Name | Type | Req | Description |
|---|---|---|---|
| incident | string | yes | A sanitized symptom summary. Remove credentials, tokens, private keys, regulated data, and unrelated customer data. |
No output schema declared.
No examples provided.
What is the Agent Rescue Desk Production Triage MCP server?
Agent Rescue Desk Production Triage is an MCP server listed in the public MCP registry as app.netlify.agent-rescue-desk/production-triage. Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures. This page covers its hosted endpoint (https://agent-rescue-desk.netlify.app/mcp).
Is the Agent Rescue Desk Production Triage MCP server safe to use?
Agent Rescue Desk Production Triage scores 88 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 Desk Production Triage MCP server expose?
Agent Rescue Desk Production Triage exposes 3 tools: describe_rescue_offer, triage_production_failure, get_case_intake_requirements. Their descriptions and schemas cost roughly 152 tokens of context every time the server is loaded.
Does the Agent Rescue Desk Production Triage MCP server require authentication?
No. We connected to Agent Rescue Desk Production Triage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Rescue Desk Production Triage MCP server still maintained?
Agent Rescue Desk Production Triage is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.