Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Checkpoint402

REMOTE · API.CHECKPOINT402.COM

Pay-per-call tx explainer, DeFi yields, token safety, SEC 8-K and OFAC data via x402 (USDC on Base).

+3 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1634 tokens (~233/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1393 → 1634 ▼ functional
    • New tool “token_safety_check” functional
  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.checkpoint402.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.checkpoint402.com CN=YE2,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA384 6ab750f91115e8e7284d7ce8b00c42178df
SANs: api.checkpoint402.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.checkpoint402.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
checkpoint402.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.checkpoint402.com/mcp Verified 200
http (plaintext) http://api.checkpoint402.com/mcp HTTPS enforced 301 https://api.checkpoint402.com/mcp
MCP tools · 7 exposed · ~910 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_transaction ~96

Paid: $0.03 USDC per successful call via x402 (not charged on errors). Explains any Base or Ethereum transaction in plain English: who sent what to whom, which tokens/NFTs moved, the function called, success/failure and fee — plus the structured decoded data.

NameTypeReqDescription
chainstring–Chain (default base)
hashstringyesTransaction hash (0x + 64 hex chars)

No output schema declared.

No examples provided.

find_defi_yields ~200

Paid: $0.05 USDC per successful call via x402 (not charged on errors). Top DeFi yields across 16k+ pools, filtered by asset, chain, minimum TVL and risk, each with a simple explained risk tier (outlier APY, thin TVL, reward-heavy, IL exposure). Data: DefiLlama.

NameTypeReqDescription
assetstring–Token symbol, e.g. USDC, ETH
chainstring–Chain name, e.g. Base, Ethereum, Arbitrum
limitnumber–Results, 1-50 (default 10)
maxRiskstring–Highest risk tier to include (default medium; use high to include outlier APYs)
minTvlUsdnumber–Minimum pool TVL in USD (default 1,000,000)
stablecoinOnlyboolean–Only stablecoin pools

No output schema declared.

No examples provided.

list_services ~31

Free. Lists every Checkpoint402 data service with its price, inputs, example output link and how payment works.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

new_token_safety_feed ~140

Paid: $0.10 USDC per successful call via x402 (not charged on errors). Newly launched token pools on Base, Ethereum or BSC, each with a 0-100 safety score and explicit red flags (honeypot, unverified code, mintable, owner powers, high tax, unlocked liquidity, whale concentration). Data: GeckoTerminal + GoPlus.

NameTypeReqDescription
chainstring–Chain (default base)
limitnumber–Results, 1-20 (default 10)
minScorenumber–Only tokens with safety score >= this, 0-100 (default 0)

No output schema declared.

No examples provided.

ofac_sanctions_screen ~150

Paid: $0.05 USDC per successful call via x402 (not charged on errors). Screens a person/company name (fuzzy, alias-aware) and/or a crypto wallet address against the US Treasury OFAC SDN list, refreshed twice daily, including the extended-remarks file where most sanctioned crypto addresses are listed.

NameTypeReqDescription
addressstring–Crypto wallet address (EVM, BTC, TRX, …)
limitnumber–Max name candidates, 1-20 (default 5)
namestring–Person or company name
thresholdnumber–Name-match threshold 0.7-1 (default 0.92)

No output schema declared.

No examples provided.

sec_8k_company_events ~161

Paid: $0.10 USDC per successful call via x402 (not charged on errors). Latest SEC 8-K filings — market-wide within minutes of filing, or for one ticker — with each item code translated to plain English, high-impact events flagged (earnings, CEO changes, M&A, bankruptcy, cyber incidents) and AI summaries of the filing text.

NameTypeReqDescription
highImpactOnlyboolean–Only filings with a high-impact item
itemstring–Only filings with this 8-K item code, e.g. 5.02
limitnumber–Results, 1-20 (default 10)
tickerstring–Stock ticker; omit for the market-wide latest feed

No output schema declared.

No examples provided.

token_safety_check ~132

Paid: $0.02 USDC per successful call via x402 (not charged on errors). Is this token a scam? Checks any token on Base, Ethereum or BSC and returns a 0-100 safety score, a verdict, red flags (honeypot, hidden fees, owner powers, unlocked liquidity, whale concentration, creator's past honeypots), good signs and a plain-English summary. Data: GoPlus + DexScreener.

NameTypeReqDescription
addressstringyesToken contract address (0x + 40 hex chars)
chainstring–Chain (default base)

No output schema declared.

No examples provided.

Install

How do I install the Checkpoint402 MCP server?

Checkpoint402 is a hosted endpoint at https://api.checkpoint402.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.checkpoint402.com

# add to Claude Code
claude mcp add --transport http com-checkpoint402-checkpoint402 'https://api.checkpoint402.com/mcp'
Common questions

What is the Checkpoint402 MCP server?

Checkpoint402 is an MCP server listed in the public MCP registry as com.checkpoint402/checkpoint402. Pay-per-call tx explainer, DeFi yields, token safety, SEC 8-K and OFAC data via x402 (USDC on Base). This page covers its hosted endpoint (https://api.checkpoint402.com/mcp).

Is the Checkpoint402 MCP server safe to use?

Checkpoint402 scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Checkpoint402 MCP server expose?

Checkpoint402 exposes 7 tools: list_services, explain_transaction, find_defi_yields, new_token_safety_feed, token_safety_check, and 2 more. Their descriptions and schemas cost roughly 910 tokens of context every time the server is loaded.

Does the Checkpoint402 MCP server require authentication?

No. We connected to Checkpoint402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Checkpoint402 MCP server still maintained?

Checkpoint402 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.