x402 Doctor
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
我該用這個嗎
品質與安全性
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 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
}社群
證據