Skip to content

Agent Rescue Desk Production Triage MCP server

app.netlify.agent-rescue-desk/production-triageagent-rescue-desk.netlify.appstreamable-httpv1.0.0Scanned

Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures.

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Rescue Desk Production Triage MCP server can do

The Agent Rescue Desk Production Triage MCP server is published by agent-rescue-desk.netlify.app, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: triage_production_failure), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (describe_rescue_offer and get_case_intake_requirements).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • triage_production_failureClassifies one sanitized n8n, MCP, webhook, agent-tool-routing, retry, or general production incident and returns concrete next checks without echoing the submitted incident.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.incident.description mentions "credentials".

      Matched text

      inputSchema.properties.incident.description: "A sanitized symptom summary. Remove credentials, tokens, private keys, regulated data,..."

      What this check looks for
    Description, as the server wrote it
    Classifies one sanitized n8n, MCP, webhook, agent-tool-routing, retry, or general production incident and returns concrete next checks without echoing the submitted incident.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • describe_rescue_offerReturns the exact scope, price, service window, acceptance rules, private fit-review URL, and direct x402 purchase URL for the Agent Rescue Desk service.Reads text others writeNo findings

    Why it is in this group

    • The name "describe_rescue_offer" says "describe": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Returns the exact scope, price, service window, acceptance rules, private fit-review URL, and direct x402 purchase URL for the Agent Rescue Desk service.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_case_intake_requirementsReturns the minimum redacted evidence needed for a fixed-scope fit review and the public intake URL.Reads text others writeNo findings

    Why it is in this group

    • The name "get_case_intake_requirements" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Returns the minimum redacted evidence needed for a fixed-scope fit review and the public intake URL. It does not submit a case.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agent-rescue-desk.netlify.app/mcp: tools/list returned 3 tools to an anonymous client, including triage_production_failure (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.incident.description mentions "credentials".

    Matched text

    inputSchema.properties.incident.description: "A sanitized symptom summary. Remove credentials, tokens, private keys, regulated data,..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http production-triage https://agent-rescue-desk.netlify.app/mcp
claude mcp add --transport http production-triage https://agent-rescue-desk.netlify.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__production-triage__describe_rescue_offer",
      "mcp__production-triage__get_case_intake_requirements"
    ],
    "ask": [
      "mcp__production-triage__triage_production_failure"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as production-triage. Review it before you use it.

Capability tags behind 2 rules
  • mcp__production-triage__describe_rescue_offer untrusted-input
  • mcp__production-triage__get_case_intake_requirements untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.netlify.agent-rescue-desk/production-triage/verify?hash=63fe088663a9fc73c399ce32bd2fa0e7ba68051bdec5b7a238bd1ef00407b3eb" | jq -e '.changed == false'

Pinned hash 63fe088663a9, from Nov 12, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.netlify.agent-rescue-desk/production-triage/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.netlify.agent-rescue-desk/production-triage
[![Anlyon Radar](https://radar.anlyon.com/badge/app.netlify.agent-rescue-desk/production-triage.svg)](https://radar.anlyon.com/servers/app.netlify.agent-rescue-desk/production-triage)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

Agent Rescue Desk Production Triage MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Rescue Desk Production Triage MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Rescue Desk Production Triage MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Rescue Desk Production Triage MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Agent Rescue Desk Production Triage MCP server have?

3 tools: 1 write, 2 read. triage_production_failure, describe_rescue_offer and get_case_intake_requirements.

Does the Agent Rescue Desk Production Triage MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Rescue Desk Production Triage MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Agent Rescue Desk Production Triage MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.