x402 Doctor

Name: x402 Doctor
Author: com.twelvepermissions

MCP serverMCP

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

Listed on its own since 2026-09-24. Until then it was part of twelve-permissions, where its earlier checks remain.

by com.twelvepermissionsrepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"x402-doctor","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability57/57 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	71 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
13 h ago	mcp initialize	ok	200	10 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
20 h ago	mcp initialize	ok	200	11 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
26 h ago	mcp initialize	ok	200	54 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
32 h ago	mcp initialize	ok	200	73 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
2 d ago	mcp initialize	ok	200	63 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
2 d ago	mcp initialize	ok	200	14 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
2 d ago	mcp initialize	ok	200	13 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
2 d ago	mcp initialize	ok	200	16 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools
3 d ago	mcp initialize	ok	200	18 ms	server x402-doctor 1.0.0 · protocol 2024-11-05 · 3 tools

Tools observed via MCP handshake

probe_x402_endpoint — 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
explain_defect — 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-pro
list_checks — The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.twelvepermissions/x402-doctor

first seen 1 mo ago · fetched 14 h agoopen ↗

Field history (7 recent events)

15 d ago · declared · summary → "Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it."
15 d ago · declared · description → "Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it."
15 d ago · declared · publisherName → "com.twelvepermissions"
15 d ago · declared · homepageUrl → "https://x402-doctor.tsharpe.workers.dev"
15 d ago · declared · repoUrl → "https://github.com/tsharpe2282-web/twelve-permissions"
15 d ago · declared · version → "1.0.0"
15 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from