Remote MCP · Endpoint

BlockVectra: multi-chain RPC & Data API MCP server

No. BlockVectra: multi-chain RPC & Data API answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
86 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Keyless docs/discovery. RPC follows chain policy; indexed data and account tools need an API key.
Website
https://blockvectra.com/en/agents/
Repository
https://github.com/blockvectra/mcp
Listing
From the official MCP registry (active).
Recent checks of BlockVectra: multi-chain RPC & Data API
CheckedResultHandshake
1 hour agoHandshake completed86 ms
2 days agoHandshake completed135 ms
4 days agoHandshake completed118 ms
6 days agoHandshake completed158 ms
8 days agoHandshake completed304 ms
10 days agoHandshake completed164 ms
12 days agoHandshake completed91 ms
14 days agoHandshake completed109 ms
16 days agoHandshake completed86 ms
17 days agoHandshake completed100 ms
18 days agoHandshake completed63 ms
20 days agoHandshake completed89 ms
22 days agoHandshake completed90 ms
24 days agoHandshake completed120 ms

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

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 BlockVectra: multi-chain RPC & Data API and makes no claim about it beyond what these checks measured.