Remote MCP · Endpoint

Thru Explorer MCP MCP server

No. Thru Explorer MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scan.thru.org/api/mcp

The last check completed an MCP handshake.

Registry name
org.thru/thru-explorer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Thru blockchain explorer: blocks, transactions, accounts, and program ABIs on the Thru RISC-V L1
Website
https://thru.org/docs/api-ref/explorer-mcp/overview/
Listing
From the official MCP registry (active).
Recent checks of Thru Explorer MCP
CheckedResultHandshake
1 hour agoHandshake completed46 ms
1 day agoHandshake completed36 ms
2 days agoHandshake completed34 ms
3 days agoHandshake completed48 ms
4 days agoHandshake completed36 ms
5 days agoHandshake completed35 ms
6 days agoHandshake completed36 ms
8 days agoHandshake completed54 ms
11 days agoHandshake completed58 ms
13 days agoHandshake completed35 ms
15 days agoHandshake completed110 ms
18 days agoHandshake completed36 ms
20 days agoHandshake completed27 ms
22 days agoHandshake completed27 ms
24 days agoHandshake completed39 ms
26 days agoHandshake completed48 ms
27 days agoHandshake completed41 ms
29 days agoHandshake completed41 ms
29 days agoHandshake completed36 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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.

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 Thru Explorer MCP and makes no claim about it beyond what these checks measured.