x402 Preflight
REMOTE · X402.CHIKOCORP.COM
Check an x402 endpoint's payment challenge and discovery metadata before paying.
Available components
Last scanned (22 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 →
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.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 5 Nov 26 +59
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “audit_x402_endpoint” rewrote its description, which is the text the model reads security
- Tool “inspect_x402_endpoint” rewrote its description, which is the text the model reads security
- Tool “order_x402_remediation” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: fair → good functional
- Tool “audit_x402_endpoint” changed its title: Audit x402 Endpoint → x402 Technical Audit cosmetic
- Tool “inspect_x402_endpoint” changed its title: Inspect x402 Endpoint → Free x402 Endpoint Check cosmetic
- Tool “order_x402_remediation” changed its title: Order x402 Remediation → Order x402 Diagnostic Report cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://x402.chikocorp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402.chikocorp.com | CN=YR1,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | 6ec68a531e1c9b4f7d7476c25c6224e872b |
| SANs: x402.chikocorp.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402.chikocorp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| chikocorp.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402.chikocorp.com/mcp | Verified | 200 | |
| http (plaintext) | http://x402.chikocorp.com/mcp | HTTPS enforced | 308 | https://x402.chikocorp.com/mcp |
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 →
audit_x402_endpoint x402 Technical Audit ~120
Technical audit for API developers launching or debugging x402. Returns deeper read-only evidence of payment configuration, schemas, redirects, CORS, cache behavior, OpenAPI, llms.txt, agent metadata, and x402 discovery consistency. Requires an explicitly authorized x402 purchase; does not test settlement, paid delivery, or actual marketplace indexing.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_network | string | – | – |
| max_price_usd | number | – | – |
| method | string | – | – |
| resource_url | string | yes | Public HTTPS x402 resource to inspect without payment credentials. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| claimBoundary | object | yes | – |
| cors | object | yes | – |
| decision | string | yes | – |
| discovery | object | yes | – |
| evidence | array | yes | – |
| expiresAt | string | yes | – |
| issues | array | yes | – |
| observedAt | string | yes | – |
| operational | object | yes | – |
| payment | object | yes | – |
| profile | string | yes | – |
| requestId | string | yes | – |
| resource | object | yes | – |
| score | integer | yes | – |
No examples provided.
inspect_x402_endpoint Free x402 Endpoint Check ~109
Free endpoint check for API developers launching or debugging x402. Inspect your live payment challenge and caller-selected comparison policy without sending payment credentials. ALLOW and BLOCK are policy decisions, not launch certification; a price-limit BLOCK does not establish a broken integration. Buyer-side inspection remains available.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_network | string | – | – |
| max_price_usd | number | – | – |
| method | string | – | – |
| resource_url | string | yes | Public HTTPS x402 resource to inspect without payment credentials. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| claimBoundary | object | yes | – |
| cors | object | yes | – |
| decision | string | yes | – |
| discovery | object | yes | – |
| evidence | array | yes | – |
| expiresAt | string | yes | – |
| issues | array | yes | – |
| observedAt | string | yes | – |
| operational | object | yes | – |
| payment | object | yes | – |
| profile | string | yes | – |
| requestId | string | yes | – |
| resource | object | yes | – |
| score | integer | yes | – |
No examples provided.
order_x402_remediation Order x402 Diagnostic Report ~123
Diagnostic report for API developers launching or debugging x402. An explicitly authorized x402 purchase creates a durable order for asynchronous findings, evidence, and prioritized fix recommendations in JSON/Markdown. The receipt is not the completed report. No implementation, human consultation, target payment, deployment, or guaranteed marketplace indexing.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | – |
| constraints | string | – | – |
| contact | string | – | – |
| goal | string | yes | – |
| language | string | – | – |
| resource_url | string | yes | – |
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedAt | string | yes | – |
| capability | string | yes | – |
| claimBoundary | object | yes | – |
| orderId | string | yes | – |
| payment | object | yes | – |
| persistence | object | yes | – |
| request | object | yes | – |
| review | object | yes | – |
| service | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the x402 Preflight MCP server?
x402 Preflight is a hosted endpoint at https://x402.chikocorp.com/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 · x402.chikocorp.com
claude mcp add --transport http chico10117-x402-preflight 'https://x402.chikocorp.com/mcp'
What is the x402 Preflight MCP server?
x402 Preflight is an MCP server listed in the public MCP registry as io.github.chico10117/x402-preflight. Check an x402 endpoint's payment challenge and discovery metadata before paying. This page covers its hosted endpoint (https://x402.chikocorp.com/mcp).
Is the x402 Preflight MCP server safe to use?
x402 Preflight scores 84 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 Preflight MCP server expose?
x402 Preflight exposes 3 tools: inspect_x402_endpoint, audit_x402_endpoint, order_x402_remediation. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.
Does the x402 Preflight MCP server require authentication?
No. We connected to x402 Preflight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402 Preflight MCP server still maintained?
x402 Preflight 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 x402 Preflight MCP server?
VerifyMCP ran 13 checks on x402 Preflight, 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.