# x402 Doctor (remote · x402-doctor.tsharpe.workers.dev)

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

- Trust score: 70/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `x402-doctor.tsharpe.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor.md), [page](https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor)

## Channel facts

- Endpoint: `https://x402-doctor.tsharpe.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 227 tokens (~75/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the x402 Doctor MCP server?

x402 Doctor is a hosted endpoint at https://x402-doctor.tsharpe.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-twelvepermissions-x402-doctor 'https://x402-doctor.tsharpe.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-twelvepermissions-x402-doctor]
url = "https://x402-doctor.tsharpe.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-twelvepermissions-x402-doctor": {
      "type": "remote",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-twelvepermissions-x402-doctor --url 'https://x402-doctor.tsharpe.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-twelvepermissions-x402-doctor:
    url: "https://x402-doctor.tsharpe.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-twelvepermissions-x402-doctor": {
      "Transport": "http",
      "Url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-twelvepermissions-x402-doctor -t streamable-http -u 'https://x402-doctor.tsharpe.workers.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-16 (score 70, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `probe_x402_endpoint` (~144 tokens)

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

Input parameters:

- `url` (string, required): The endpoint to probe, http(s) only. Private and loopback addresses are refused.

### `explain_defect` (~55 tokens)

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.

Input parameters:

- `id` (string, required)

### `list_checks` (~28 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 70
- 2026-09-25: 70
- 2026-09-24: 70
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64
- 2026-09-03: 64
- 2026-09-02: 63
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62

## Common questions

### What is the x402 Doctor MCP server?

x402 Doctor is an MCP server listed in the public MCP registry as com.twelvepermissions/x402-doctor. Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it. This page covers its hosted endpoint (https://x402-doctor.tsharpe.workers.dev/mcp).

### Is the x402 Doctor MCP server safe to use?

x402 Doctor scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the x402 Doctor MCP server expose?

x402 Doctor exposes 3 tools: probe_x402_endpoint, explain_defect, list_checks. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

### Does the x402 Doctor MCP server require authentication?

No. We connected to x402 Doctor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the x402 Doctor MCP server still maintained?

x402 Doctor is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402-doctor.tsharpe.workers.dev/mcp
- Repository: https://github.com/tsharpe2282-web/twelve-permissions
- Website: https://x402-doctor.tsharpe.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor.json
- HTML version of this page: https://verifymcp.io/servers/com-twelvepermissions-x402-doctor/x402-doctor