Remote MCP · Endpoint

Tanod MCP server

No. Tanod answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tanod.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.tanod/tanod
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
855 ms
Tools exposed
143 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Pay-per-call agent tools: PDF, OCR, translation, news search, prediction markets, web, chain reads.
Website
https://tanod.dev/
Listing
From the official MCP registry (active).
Recent checks of Tanod
CheckedResultHandshake
1 hour agoHandshake completed855 ms
1 day agoHandshake completed1.41 s
4 days agoHandshake completed319 ms
6 days agoHandshake completed322 ms
9 days agoHandshake completed858 ms
11 days agoHandshake completed322 ms
13 days agoHandshake completed307 ms
15 days agoHandshake completed332 ms
17 days agoHandshake completed356 ms
19 days agoHandshake completed276 ms
21 days agoHandshake completed762 ms
22 days agoHandshake completed809 ms
23 days agoHandshake completed857 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 and makes no claim about it beyond what these checks measured.