Remote MCP · Endpoint
BlockRazor Docs MCP server
No. BlockRazor Docs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.blockrazor.io/docs
The last check completed an MCP handshake.
- Registry name
- io.blockrazor/docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 291 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Official BlockRazor documentation for sending and receiving transations faster.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 291 ms |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 547 ms |
| 3 days ago | Handshake completed | 533 ms |
| 4 days ago | Handshake completed | 499 ms |
| 5 days ago | Handshake completed | 232 ms |
| 6 days ago | Handshake completed | 333 ms |
| 9 days ago | Handshake completed | 517 ms |
| 12 days ago | Handshake completed | 554 ms |
| 14 days ago | Handshake completed | 493 ms |
| 16 days ago | Handshake completed | 372 ms |
| 18 days ago | Handshake completed | 509 ms |
| 20 days ago | Handshake completed | 980 ms |
| 22 days ago | Handshake completed | 450 ms |
| 24 days ago | Handshake completed | 226 ms |
| 26 days ago | Handshake completed | 283 ms |
| 27 days ago | Handshake completed | 498 ms |
| 28 days ago | Handshake completed | 575 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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.
Listing data comes from the official MCP registry. Glide is not affiliated with BlockRazor Docs and makes no claim about it beyond what these checks measured.