Remote MCP · Endpoint
Bitview MCP server
No. Bitview answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.bitview.space/
The last check completed an MCP handshake.
- Registry name
- io.github.bitcoinresearchkit/bitview
- Transport
- Streamable HTTP
- Protocol negotiated
- 2026-07-28
- Handshake latency
- 478 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 100% from 17 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/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 478 ms |
| 2 days ago | Handshake completed | 342 ms |
| 4 days ago | Handshake completed | 288 ms |
| 5 days ago | Handshake completed | 306 ms |
| 7 days ago | Handshake completed | 328 ms |
| 8 days ago | Handshake completed | 354 ms |
| 9 days ago | Handshake completed | 326 ms |
| 12 days ago | Handshake completed | 281 ms |
| 13 days ago | Handshake completed | 306 ms |
| 15 days ago | Handshake completed | 350 ms |
| 16 days ago | Handshake completed | 331 ms |
| 18 days ago | Handshake completed | 295 ms |
| 19 days ago | Handshake completed | 296 ms |
| 20 days ago | Handshake completed | 295 ms |
| 20 days ago | Handshake completed | 303 ms |
| 21 days ago | Handshake completed | 272 ms |
| 22 days ago | Handshake completed | 345 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Bitview and makes no claim about it beyond what these checks measured.