Remote MCP · Endpoint

com.blockscout/mcp-server MCP server

No. com.blockscout/mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.blockscout.com/mcp

The last check completed an MCP handshake.

Registry name
com.blockscout/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
468 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for Blockscout
Website
https://blockscout.com/
Repository
https://github.com/blockscout/mcp-server
Listing
From the official MCP registry (active).
Recent checks of com.blockscout/mcp-server
CheckedResultHandshake
1 hour agoHandshake completed468 ms
2 days agoHandshake completed622 ms
4 days agoHandshake completed264 ms
5 days agoHandshake completed159 ms
7 days agoHandshake completed263 ms
8 days agoHandshake completed333 ms
9 days agoHandshake completed155 ms
12 days agoHandshake completed156 ms
13 days agoHandshake completed408 ms
15 days agoHandshake completed211 ms
16 days agoHandshake completed229 ms
17 days agoHandshake completed384 ms
18 days agoHandshake completed149 ms
19 days agoHandshake completed152 ms
20 days agoHandshake completed155 ms
21 days agoHandshake completed158 ms
22 days agoHandshake completed392 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.

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 com.blockscout/mcp-server and makes no claim about it beyond what these checks measured.