Checkpoint402 MCP

A human read this entry. That is the one thing true of everything on the list. Beyond that: the endpoint answered an x402 request when we knocked it, on the date shown. That date is the claim — not a word, a date. None of it is a delivery test. We have not paid for this and graded what came back, so read it as "we checked what is stated above," never as "this is worth the money."

How we check →

Remote streamable-http MCP server with five paid data tools plus a free `list_services`: `explain_transaction` (any Base or Ethereum tx in plain English), `find_defi_yields` (risk-tiered pools via DefiLlama), `new_token_safety_feed` (new tokens with a safety score), `sec_8k_company_events` (SEC 8-K filings, impact-tagged) and `ofac_sanctions_screen` (name or wallet against the OFAC SDN list). $0.03–$0.10 USDC per call on Base via x402; errors are never charged. Listed in the official MCP Registry as `com.checkpoint402/checkpoint402`. Example tool call: `explain_transaction {"hash":"0xcbb626797fd53a67c9342c1541bc5e56a447b77a3efe490b5d7b2876be3b7205"}`. ([Site](https://checkpoint402.com)) ([OpenAPI](https://api.checkpoint402.com/openapi.json)) ([Registry](https://registry.modelcontextprotocol.io/v0.1/servers?search=com.checkpoint402))