Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.x402check/mcp

REMOTE · X402CHECK.DEV · 2 COMPONENTS

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

+3 this week 79 Trust /100

Last scanned (13 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://x402check.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=x402check.dev CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39803d4bc6ff22b213e65c4b408a7f62
SANs: x402check.dev, *.x402check.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402check.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
x402check.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402check.dev/mcp Verified 200
http (plaintext) http://x402check.dev/mcp HTTPS enforced 301 https://x402check.dev/mcp
MCP tools · 6 exposed · ~726 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_tools ~84

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.

NameTypeReqDescription
freshboolean––
urlsarrayyesCandidate seller URLs to compare

No output schema declared.

No examples provided.

deep_check ~119

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.

NameTypeReqDescription
urlstringyesAbsolute https URL of the x402 seller endpoint (the resource you are about to pay)

No output schema declared.

No examples provided.

preflight_batch ~88

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.

NameTypeReqDescription
freshboolean––
urlsarrayyesAbsolute https seller URLs; billed per item

No output schema declared.

No examples provided.

preflight_check ~174

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']).

NameTypeReqDescription
freshboolean–Force a live probe; ignore cache
urlstringyesAbsolute https URL of the x402 seller endpoint (the resource you are about to pay)

No output schema declared.

No examples provided.

verify_payto ~125

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.

NameTypeReqDescription
freshboolean–Force a live probe; ignore cache
urlstringyesAbsolute https URL of the x402 seller endpoint (the resource you are about to pay)

No output schema declared.

No examples provided.

watch_tool ~136

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.

NameTypeReqDescription
emailstring–Optional email for change alerts via Resend (also set webhookUrl if you want an HTTPS webhook)
urlstringyesAbsolute https URL of the x402 seller endpoint (the resource you are about to pay)
webhookUrlstring–https URL that receives POST JSON alerts on change

No output schema declared.

No examples provided.

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.

remote · x402check.dev

# add to Claude Code
claude mcp add --transport http dev-x402check-mcp 'https://x402check.dev/mcp'
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.