Remote MCP · Endpoint

Bitview MCP server

Yes, as of 1 hour ago: the server rejected the MCP handshake.

DownLast checked 1 hour ago

Server URL

https://mcp.bitview.space/

The last check failed: the server rejected the MCP handshake.

Registry name
io.github.bitcoinresearchkit/bitview
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
66.7% from 18 checks
Described by its publisher as
Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key.
Website
https://mcp.bitview.space/
Repository
https://github.com/bitcoinresearchkit/mono
Listing
From the official MCP registry (active).
Recent checks of Bitview
CheckedResultHandshake
1 hour agoFailed - the server rejected the MCP handshake—
1 day agoFailed - the server rejected the MCP handshake—
2 days agoFailed - the server rejected the MCP handshake—
3 days agoFailed - the server rejected the MCP handshake—
4 days agoFailed - the server rejected the MCP handshake—
5 days agoFailed - the server rejected the MCP handshake—
6 days agoHandshake completed427 ms
9 days agoHandshake completed310 ms
12 days agoHandshake completed293 ms
14 days agoHandshake completed349 ms
16 days agoHandshake completed1.30 s
18 days agoHandshake completed323 ms
20 days agoHandshake completed478 ms
22 days agoHandshake completed342 ms
24 days agoHandshake completed288 ms
26 days agoHandshake completed306 ms
27 days agoHandshake completed328 ms
29 days agoHandshake completed354 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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