x402 Doctor

Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.

我该使用它吗

质量与安全性

A
描述质量
93%
模式完整度
70%
命名质量
87%
投毒风险
100%
权限匹配度
100%
协议合规性
100%

基于对工具定义和协议合规性的自动分析。

上下文开销

~304token 数(工具定义)
~365 B典型响应大小
对注意力的影响极小(占 128k 上下文窗口的 0.24%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

{
  "mcpServers": {
    "x402-doctor": {
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}

远程端点

https://x402-doctor.tsharpe.workers.dev/mcpstreamable-http

它能做什么

工具清单

工具(3)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢probe_x402_endpoint(url)

Probe an x402 seller endpoint and report what it observes about it. Performs the handshake a paying client would: GET with no X-PAYMENT header, then checks the 402 challenge against 16 rules. Every finding says whether the rule comes from the x402 spec or from an observed facilitator rejection. Reports status "healthy" (nothing to report), "advisories" (only warn/info findings — the endpoint works), "defects_found" (at least one error-severity finding), "not_x402" or "unreachable".

输入模式

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The endpoint to probe, http(s) only. Private and loopback addresses are refused."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢explain_defect(id)

Full explanation of one rule by id — what it checks, why it matters, how to fix it, and where the rule came from. Use when you want the reasoning without re-probing.

输入模式

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
🟢list_checks

The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.

输入模式

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

社区

评价此服务器

证据

最近观测

已验证未记录版本3 个工具
已验证未记录版本3 个工具