x402 Preflight MCP server
io.github.chico10117/x402-preflightchico10117streamable-httpv1.0.2Scanned
Check an x402 endpoint's payment challenge and discovery metadata before paying.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 1
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the x402 Preflight MCP server can do
The x402 Preflight MCP server is published by the GitHub account chico10117. It has 3 tools. It can create or change data (2 tools: audit_x402_endpoint and order_x402_remediation), but cannot delete data. 1 tool only reads.
3 tools bring in text other people can write (inspect_x402_endpoint, audit_x402_endpoint and order_x402_remediation); 1 tool can send data out of your system (order_x402_remediation).
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
audit_x402_endpointTechnical audit for API developers launching or debugging x402.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "...402 resource to inspect without payment credentials."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
order_x402_remediationDiagnostic report for API developers launching or debugging x402.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
inspect_x402_endpointFree endpoint check for API developers launching or debugging x402.Reads text others write2 findings
Why it is in this group
- The name "inspect_x402_endpoint" says "inspect": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...mparison policy without sending payment credentials. ALLOW and BLOCK are policy decisions,..."
- Info
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "...402 resource to inspect without payment credentials."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://x402.chikocorp.com/mcp: tools/list returned 3 tools to an anonymous client, including audit_x402_endpoint (write), order_x402_remediation (write)
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...mparison policy without sending payment credentials. ALLOW and BLOCK are policy decisions,..."
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "...402 resource to inspect without payment credentials."
The input schema at properties.resource_url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.resource_url.description: "...402 resource to inspect without payment credentials."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http x402-preflight https://x402.chikocorp.com/mcpclaude mcp add --transport http x402-preflight https://x402.chikocorp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__x402-preflight__inspect_x402_endpoint"
],
"ask": [
"mcp__x402-preflight__audit_x402_endpoint",
"mcp__x402-preflight__order_x402_remediation"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as x402-preflight. Review it before you use it.
Capability tags behind 3 rules
- mcp__x402-preflight__inspect_x402_endpoint untrusted-input
- mcp__x402-preflight__audit_x402_endpoint untrusted-input
- mcp__x402-preflight__order_x402_remediation untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.chico10117/x402-preflight/verify?hash=e784f6298139aab21dd25c25ddae0c0bbcf304dd6a17503805fc9e7527511d55" | jq -e '.changed == false'Pinned hash e784f6298139, from Nov 19, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.chico10117/x402-preflight/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.chico10117/x402-preflight)Source: MCP Registry · repository. Synced Nov 5, 2026, 17:17 UTC.
x402 Preflight MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the x402 Preflight MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the x402 Preflight MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the x402 Preflight MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the x402 Preflight MCP server have?
- 3 tools: 2 write, 1 read. audit_x402_endpoint, order_x402_remediation and inspect_x402_endpoint.
Does the x402 Preflight MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the x402 Preflight MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): order_x402_remediation.
Has the x402 Preflight MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.