# x402 Doctor

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

- name: com.twelvepermissions/x402-doctor
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.twelvepermissions%2Fx402-doctor
- tools: https://api.protogrid.dev/v1/servers/com.twelvepermissions%2Fx402-doctor/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-97% ~updated-64d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_checks (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); probe_x402_endpoint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_defect (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 292 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 292 tokens to load them all
- tool set hash: 5bb6902a60eb59f6483d6df7b7272c84
- badge: [![protogrid quality](https://protogrid.dev/badge/com.twelvepermissions/x402-doctor.svg)](https://protogrid.dev/servers/com.twelvepermissions/x402-doctor)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://x402-doctor.tsharpe.workers.dev/mcp (streamable-http, auth none, reachable true, uptime30d 0.96581197)

## Packages

_none_

## Tools (3)

- `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-probing.
- `list_checks`: The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.
- `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 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".