Other · Remote MCP server
x402 Preflight
Inspect and validate an x402 endpoint before an autonomous agent spends USDC.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.chico10117/x402-preflight- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-04
- Updated
- 2026-09-04
- Publisher
- chico10117 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/chico10117) · how
- Repository
- github.com/chico10117/basepay-readiness-service
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://x402.chikocorp.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- x402-preflight 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
inspect_x402_endpoint,audit_x402_endpoint,order_x402_remediation - Checked on
- 2026-10-05
How to connect x402 Preflight
x402 Preflight is a remote MCP server: there is nothing to install. Its endpoint is https://x402.chikocorp.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| X402 MCP ServerJMT x402: 35 pay-per-call Base/USDC tools for agents, auto-paid via x402 v2. No API key. | Local · stdio |
| X402 MCP ServerMCP server for Hermes Asia x402 CN/JP market intelligence via USDC on Base. 8 endpoints. | Local · stdio |
| X402 Money FarmPay-per-call web extraction: clean text, metadata, links, JSON-LD, change detection. USDC on Base. | Local · stdio |
| X402 Payment SafetyAuthorize x402 payments before signing with request-bound, signed safety decisions. | Remote · HTTPLive check: ✓ handshake |
| X402 Scan MCPX402 Endpoint Scanner - a free local health probe for x402 paid endpoints as an MCP server. | Local · stdio |
| X402 SmsPay-per-call MCP server. $0.03 USDC sends one transactional SMS to a US phone number via x402. | Local · stdio |
| X402 Tools61 x402 pay-per-call tools that chain: each answer names the next call. No API key, no account. | Remote · HTTPLive check: ✓ handshake |
| X402 Tools MCPMelis x402 Tools - 22 pay-per-call APIs for AI agents. No accounts, no API keys. USDC on Base. | Local · stdio |