Remote MCP · Endpoint

Block402 MCP server

Yes, as of 5 hours ago: the server returned an HTTP error.

DownLast checked 5 hours ago

Server URL

https://api.block402.xyz/mcp

The last check failed: the server returned an HTTP error.

Registry name
xyz.block402/block402
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Bitcoin RPC for AI agents. 7 read tools; x402 USDC on Base mainnet. Discovery is free.
Listing
From the official MCP registry (active).
Recent checks of Block402
CheckedResultHandshake
5 hours agoFailed - the server returned an HTTP error—
4 days agoHandshake completed1.06 s
14 days agoHandshake completed93 ms
15 days agoHandshake completed175 ms
15 days agoHandshake completed112 ms
17 days agoHandshake completed219 ms
18 days agoHandshake completed111 ms
19 days agoHandshake completed106 ms
20 days agoHandshake completed130 ms
21 days agoHandshake completed93 ms
23 days agoHandshake completed216 ms
26 days agoHandshake completed463 ms
28 days agoHandshake completed86 ms

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

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 Block402 and makes no claim about it beyond what these checks measured.