Remote MCP · Endpoint

Tanod Chain MCP server

No. Tanod Chain answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://tanod.dev/mcp/chain

The last check completed an MCP handshake.

Registry name
dev.tanod/chain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
EVM and Solana reads: balances, tokens, eth_call, logs, receipts, gas, blocks, transactions, ENS.
Website
https://tanod.dev/
Listing
From the official MCP registry (active).
Recent checks of Tanod Chain
CheckedResultHandshake
3 hours agoHandshake completed315 ms
13 hours agoHandshake completed329 ms
2 days agoHandshake completed583 ms
4 days agoHandshake completed348 ms
7 days agoHandshake completed382 ms
9 days agoHandshake completed876 ms
11 days agoHandshake completed298 ms
14 days agoHandshake completed842 ms
15 days agoHandshake completed745 ms
18 days agoHandshake completed730 ms
20 days agoHandshake completed777 ms
21 days agoHandshake completed314 ms
23 days agoHandshake completed808 ms

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

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