# dev.x402check/mcp (remote · x402check.dev)

Preflight before paying any x402 tool (ok|caution|avoid + history). 1 free/wallet; then $0.01 Base.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `x402check.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-x402check-mcp/x402check.md), [page](https://verifymcp.io/servers/dev-x402check-mcp/x402check)
- npm · `x402check-mcp`: 34/100, [markdown](https://verifymcp.io/servers/dev-x402check-mcp/x402check-mcp.md), [page](https://verifymcp.io/servers/dev-x402check-mcp/x402check-mcp)

## Channel facts

- Endpoint: `https://x402check.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.6`

## 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 879 tokens (~146/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 dev.x402check/mcp server?

dev.x402check/mcp is a hosted endpoint at https://x402check.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 dev-x402check-mcp 'https://x402check.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-x402check-mcp": {
      "url": "https://x402check.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-x402check-mcp": {
      "type": "http",
      "url": "https://x402check.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-x402check-mcp]
url = "https://x402check.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-x402check-mcp": {
      "type": "remote",
      "url": "https://x402check.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-x402check-mcp --url 'https://x402check.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-x402check-mcp:
    url: "https://x402check.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-x402check-mcp": {
      "Transport": "http",
      "Url": "https://x402check.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-x402check-mcp -t streamable-http -u 'https://x402check.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-x402check-mcp": {
      "type": "http",
      "url": "https://x402check.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-11-21 (score 79, +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.

### 2026-11-19 (score 78, +1)

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

### 2026-11-17 (score 77, +1)

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

### 2026-11-14 (score 76, +1)

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

### 2026-11-12 (score 75, +1)

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

### 2026-11-10 (score 74, +1)

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

### 2026-11-08 (score 73, +1)

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

### 2026-11-06 (score 72, +1)

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

## MCP tools (6)

### `preflight_check` (~174 tokens)

Preflight an x402 seller URL before settle / PAYMENT-SIGNATURE. Pass the absolute https seller URL. Returns verdict ok|caution|avoid plus that tool's history only (uptime, payToChanges, priceChanges). Use when: about to pay any x402 endpoint; asking is this API a scam; is this endpoint safe or legit; debugging a failing 402; checking uptime; validating payment requirements before signing USDC on Base. Do not pay if verdict=avoid. Charged $0.01 per URL via x402 Exact on this MCP tools/call (params._meta['x402/payment']).

Input parameters:

- `fresh` (boolean): Force a live probe; ignore cache
- `url` (string, required): Absolute https URL of the x402 seller endpoint (the resource you are about to pay)

### `verify_payto` (~125 tokens)

Verify the payTo / receiving wallet an x402 seller demands before you sign. Same check as preflight_check: live 402 probe + history.payToChanges (wallet rotations) and priceChanges. Use when confirming which Base USDC address you will pay, comparing payTo to an allowlist, or detecting a rug-style wallet swap. Charged per URL via MCP x402 payment.

Input parameters:

- `fresh` (boolean): Force a live probe; ignore cache
- `url` (string, required): Absolute https URL of the x402 seller endpoint (the resource you are about to pay)

### `preflight_batch` (~88 tokens)

Trust-check up to 25 x402 seller URLs in one request. Charged per URL (N × unit) in a single Exact settlement via MCP _meta payment. Prefer when comparing candidates, picking the cheapest/most reliable, or screening Bazaar search hits before paying any of them.

Input parameters:

- `fresh` (boolean)
- `urls` (array, required): Absolute https seller URLs; billed per item

### `compare_tools` (~84 tokens)

Compare several x402 tools before choosing which to pay. Alias of preflight_batch: returns each URL's verdict, priceUsd, payTo, uptimePct, and drift history so you can pick reliable/cheap candidates and skip avoid. Charged per URL via MCP x402 payment.

Input parameters:

- `fresh` (boolean)
- `urls` (array, required): Candidate seller URLs to compare

### `deep_check` (~119 tokens)

Deeper trust check before paying an x402 endpoint ($0.05 Exact USDC). Runs the same live 402 + history as preflight_check, then repeated probes for payTo/price consistency, a recent public Base USDC-to-payTo transfer sample, Bazaar + 402 Index listing checks, and drift vs last KV history. Does not claim OFAC or wallet simulation. Optional when the base check is not enough signal.

Input parameters:

- `url` (string, required): Absolute https URL of the x402 seller endpoint (the resource you are about to pay)

### `watch_tool` (~136 tokens)

Subscribe to daily re-checks of one x402 seller URL for 30 days. Alerts your webhook and/or email when payTo, price, network, or availability changes. Fixed $5 USDC Exact (not per-check). Optional after a one-shot preflight when you will revisit the same seller.

Input parameters:

- `email` (string): Optional email for change alerts via Resend (also set webhookUrl if you want an HTTPS webhook)
- `url` (string, required): Absolute https URL of the x402 seller endpoint (the resource you are about to pay)
- `webhookUrl` (string): https URL that receives POST JSON alerts on change

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-x402check-mcp/x402check#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 63
- 2026-10-31: 63

## Common questions

### What is the dev.x402check/mcp server?

dev.x402check/mcp is listed in the public MCP registry as dev.x402check/mcp. Preflight before paying any x402 tool (ok|caution|avoid + history). 1 free/wallet; then $0.01 Base. This page covers its hosted endpoint (https://x402check.dev/mcp).

### Is the dev.x402check/mcp server safe to use?

dev.x402check/mcp scores 79 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 dev.x402check/mcp server expose?

dev.x402check/mcp exposes 6 tools: preflight_check, verify_payto, preflight_batch, compare_tools, deep_check, watch_tool. Their descriptions and schemas cost roughly 726 tokens of context every time the server is loaded.

### Does the dev.x402check/mcp server require authentication?

No. We connected to dev.x402check/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.x402check/mcp server still maintained?

dev.x402check/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the dev.x402check/mcp server?

VerifyMCP ran 13 checks on dev.x402check/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://x402check.dev/mcp
- Website: https://x402check.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-x402check-mcp/x402check.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-x402check-mcp/x402check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-x402check-mcp/x402check.json
- HTML version of this page: https://verifymcp.io/servers/dev-x402check-mcp/x402check
