code402 Verify — Compliance MCP for AI Agents
https://verify.code402.dev/mcpCompliance verification MCP server for AI agents: IBAN, LEI, Luhn, Mod97, sanctions screening, onchain address checks, and chain RPC queries. 18 tools, WASM-backed banking functions. Paid per call via x402 (gasless EIP-3009 USDC on Base) — non-custodial. Free: receipt verification + price lookup + 3 paid probes/day.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 93.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 (191 ms). |
| Protocol revision | 10/10 | Speaks the current MCP revision 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 22/22 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 18 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 97% of peers
- This listing 90 · peer median 81
- Latency
- Faster than 93% of peers
- This listing 90 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
- Freshness + modern flags −1
— Keep the listing current in the registry or source it comes from.
Now: seen in a source within 7 days.
Listed in
Directories this entry was found in.
How to connect
https://verify.code402.dev/mcp
curl -X POST https://verify.code402.dev/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'