Remote MCP · Endpoint
BlockVectra: multi-chain RPC & Data API MCP server
No. BlockVectra: multi-chain RPC & Data API answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://docs.blockvectra.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.blockvectra/docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 125 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Keyless Robinhood Chain/EVM docs. RPC per-chain policy; indexed data/account need an API key.
- Repository
- https://github.com/blockvectra/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 125 ms |
| 9 days ago | Handshake completed | 224 ms |
| 10 days ago | Handshake completed | 120 ms |
| 11 days ago | Handshake completed | 177 ms |
| 12 days ago | Handshake completed | 69 ms |
| 14 days ago | Handshake completed | 188 ms |
| 14 days ago | Handshake completed | 379 ms |
| 15 days ago | Handshake completed | 206 ms |
| 17 days ago | Handshake completed | 153 ms |
| 19 days ago | Handshake completed | 73 ms |
| 21 days ago | Handshake completed | 86 ms |
| 24 days ago | Handshake completed | 135 ms |
| 26 days ago | Handshake completed | 118 ms |
| 28 days ago | Handshake completed | 158 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.
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 BlockVectra: multi-chain RPC & Data API and makes no claim about it beyond what these checks measured.