x402 Preflight
https://x402.chikocorp.com/mcpInspect and validate an x402 endpoint before an autonomous agent spends USDC.
What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 29 (97%). Median response 347 ms, 95th percentile 1,256 ms.
When we called tools/list it returned 3 tools, including inspect_x402_endpoint, audit_x402_endpoint, order_x402_remediation, over MCP protocol revision 2025-11-25.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 53% and higher on readiness than 35%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (3)
As returned by the server's own tools/list when we called it.
- inspect_x402_endpoint
- Free endpoint check for API developers launching or debugging x402. Inspect your live payment challenge and caller-selected comparison policy without sending pa…
- audit_x402_endpoint
- Technical audit for API developers launching or debugging x402. Returns deeper read-only evidence of payment configuration, schemas, redirects, CORS, cache beha…
- order_x402_remediation
- Diagnostic report for API developers launching or debugging x402. An explicitly authorized x402 purchase creates a durable order for asynchronous findings, evid…
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 80.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (843 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 14.5/15 | 29/30 probes succeeded over 30 days (97%). |
| Tool declaration | 10/10 | Lists 3 tool(s) with descriptions. |
| Verified identity | 0/10 | No source repository, package or homepage declared. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 35% of peers
- This listing 75 · peer median 81
- Latency
- Faster than 53% of peers
- This listing 318 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Verified identity −10
— Claim the listing and prove control of its domain.
Now: No source repository, package or homepage declared.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Listed in
Directories this entry was found in.
How to connect
https://x402.chikocorp.com/mcp
curl -X POST https://x402.chikocorp.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'