url/mcp.code402.dev/mcp
code402
Is the code402 MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-14.
Storefront for x402 APIs: discover services, probe payment terms and list your own API.
alive probed 2026-11-14 · HTTP 200
- Endpoint
- https://mcp.code402.dev/mcp (streamable-http)
- Host
- mcp.code402.dev
- Protocol
- 2025-11-25
- Reports itself as
- code402 1.3.0
- Capabilities
- prompts, resources, tools
- Instructions
- 1 026 characters
- Of a 1M window
- 1.7 % of a 1M context window
- Count
- 17k tokens in Claude Opus 5.5, exact, measured 2026-11-14. With the Claude Code prefix mcp__…__ on each tool name: 18k. The o200k_base estimate is 9.7k. Counted again when the tool definitions change. Method.
- Website
- https://code402.dev
- Registry
- Not in the official registry. Listed in awesome-remote-mcp-servers, so the daily probe measures it with the registry servers. Publish it and it gets its registry name here.
- Changes
- 4 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.77×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| iso20022_validate | 686 | 388 | 4 % |
| pre_disbursement_guard | 676 | 382 | 4 % |
| counterparty_passport_verify | 654 | 370 | 4 % |
| batch_validate | 584 | 330 | 3 % |
| counterparty_live_dossier | 569 | 322 | 3 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 3 other servers
These registry entries have the same tool names and the same schema sizes.
- io.github.89rat/code402 rail.hcrb.in
- io.github.89rat/openfang-rail hcrb.in
- io.github.89rat/x402-checks api.code402.dev
More servers
Servers that mention code402.
- openfang-rail io.github.89rat/openfang-rail · alive
- io.github.89rat/code402 · alive
- io.github.89rat/x402-checks · alive
- io.github.89rat/code402-verify-mcp · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 11:22 | alive | 328 ms | 58 | 17k | 9.7k |
| 2026-11-10 12:12 | alive | 336 ms | 57 | 16k | 8.8k |
| 2026-11-09 12:38 | no DNS | ||||
| 2026-10-28 10:23 | newer protocol |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.