Remote MCP · Endpoint

Developer Utilities & Validators (Tanod) MCP server

No. Developer Utilities & Validators (Tanod) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tanod.dev/mcp/util

The last check completed an MCP handshake.

Registry name
dev.tanod/util
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Cloud GPU prices per hour, plus developer helpers: hash, HMAC, JWT, IDs, JSON, cron, time zones.
Listing
From the official MCP registry (active).
Recent checks of Developer Utilities & Validators (Tanod)
CheckedResultHandshake
1 hour agoHandshake completed303 ms
7 hours agoHandshake completed328 ms
2 days agoHandshake completed283 ms
4 days agoHandshake completed339 ms
7 days agoHandshake completed316 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed366 ms
14 days agoHandshake completed291 ms
15 days agoHandshake completed3.67 s
18 days agoHandshake completed305 ms
20 days agoHandshake completed250 ms
21 days agoHandshake completed252 ms
23 days agoHandshake completed261 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Developer Utilities & Validators (Tanod) and makes no claim about it beyond what these checks measured.