Remote MCP · Endpoint

Checkpoint402 MCP server

No. Checkpoint402 answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.checkpoint402.com/mcp

The last check completed an MCP handshake.

Registry name
com.checkpoint402/checkpoint402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
99 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call tx explainer, DeFi yields, token safety, SEC 8-K and OFAC data via x402 (USDC on Base).
Listing
From the official MCP registry (active).
Recent checks of Checkpoint402
CheckedResultHandshake
5 hours agoHandshake completed99 ms
9 days agoHandshake completed112 ms
10 days agoHandshake completed97 ms
11 days agoHandshake completed100 ms
12 days agoHandshake completed97 ms
14 days agoHandshake completed103 ms
14 days agoHandshake completed98 ms
15 days agoHandshake completed101 ms
17 days agoHandshake completed104 ms
19 days agoHandshake completed133 ms
21 days agoHandshake completed106 ms
24 days agoHandshake completed103 ms
26 days agoHandshake completed98 ms
28 days agoHandshake completed97 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Checkpoint402 and makes no claim about it beyond what these checks measured.