Agent Rescue

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

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
100%
命名品質
93%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~673Token(工具定義)
~1.3 KB典型回應大小
中等的注意力影響(128k 上下文的 0.53%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "agent-rescue": {
      "url": "https://agent-rescue.vercel.app/api/mcp"
    }
  }
}

遠端端點

https://agent-rescue.vercel.app/api/mcpstreamable-http

它能做什麼

工具清單

工具(3)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢check_and_claim(key, ttl_seconds, metadata)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Stable identifier for the action, e.g. 'invoice-2026-07-A491:pay'."
    },
    "ttl_seconds": {
      "type": "integer",
      "description": "How long the claim lasts, in seconds. Default 86400 (1 day), max 30 days."
    },
    "metadata": {
      "type": "object",
      "description": "Small payload returned alongside the claim. Do not include secrets."
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false
}
🟢fetch_structured(url, schema, instructions)

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`.

輸入結構描述

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL."
    },
    "schema": {
      "type": "object",
      "description": "JSON Schema of the object you want back. Missing fields come back as null."
    },
    "instructions": {
      "type": "string",
      "description": "Optional. What exactly to look for if the page is ambiguous."
    }
  },
  "required": [
    "url",
    "schema"
  ],
  "additionalProperties": false
}
🟢request_capability(need, context, deadline, would_pay)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "need": {
      "type": "string",
      "description": "What exactly you need, in one or two sentences. Do not include personal data."
    },
    "context": {
      "type": "string",
      "description": "Optional. What you tried and why it did not work."
    },
    "deadline": {
      "type": "string",
      "description": "Optional. ISO 8601."
    },
    "would_pay": {
      "type": "boolean",
      "description": "Optional. Whether your policy allows paying to get this solved. Answer honestly: a false answer unlocks nothing and degrades the measurement."
    }
  },
  "required": [
    "need"
  ],
  "additionalProperties": false
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本3 個工具
已驗證未記錄版本3 個工具
已驗證未記錄版本3 個工具