Pay-per-call checks an AI agent runs before it moves money or trusts a counterparty. No API keys, no accounts, no signup. Each paid tool call settles in USDC on Base via the x402 protocol, straight from the agent's wallet ($0.001-$0.10 per call), through the Coinbase CDP facilitator, in about two seconds. **Start with the free `payment_info` tool.** It costs nothing, explains how payment works, and lists the price of every other tool. A client without wallet support can still call it. **20 tools in five groups:** - **Free** - `payment_info`: how to pay, what each tool costs, where payments settle. - **On-chain safety** - token safety verdicts (is this ERC-20 a scam, a honeypot, or safe to hold), wallet risk profiles, on-chain payment verification, canonical token checks on Base. - **Finance validators** - IBAN, VAT, BIC/SWIFT, LEI, ISIN: deterministic check-digit and format validation with enrichment. - **Web security** - TLS certificate checks, SPF/DMARC/DKIM email-spoofing posture, brand typosquat and homoglyph detection. - **Base chain data** - live gas oracle, block info, token supply, token activity, address portfolio. Every response carries an evidence record - what was checked, against which sources, how fresh it is, and what the answer does **not** establish - and is Ed25519-signed. **No LLM inference anywhere:** every response is a deterministic computation or a live read of external state, so the same input returns the same answer forever. These are informational signals. None is a compliance control, none discharges a legal obligation, and a valid signature proves a response came from this service unaltered - not that the answer is correct. **Docs:** [llms.txt](https://chainverdict.xyz/llms.txt) - [OpenAPI](https://chainverdict.xyz/openapi.json) - [Methodology](https://chainverdict.xyz/v1/methodology) - [Verify a response](https://pulse.chainverdict.xyz/verify) - [Full portfolio and price list](https://pulse.chainverdict.xyz/.well-known/portfolio.json) - [Website](https://chainverdict.xyz) **Example prompts:** - "What does this cost? Call payment_info." - "Get a token safety verdict for 0x... on Base." - "Profile the wallet 0x... before I pay it." - "Validate this IBAN and this VAT number." - "Is example.com's email spoofable? Check SPF/DMARC."
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, 79.6/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 (1375 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) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 20 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
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 95% of peers
- This listing 88 · peer median 81
- Latency
- Faster than 11% of peers
- This listing 852 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/alexander-balieu/chainverdict/mcpcurl -X POST https://server.smithery.ai/alexander-balieu/chainverdict/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'