Remote MCP · Endpoint

Web Reader & Search (Tanod) MCP server

No. Web Reader & Search (Tanod) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tanod.dev/mcp/web

The last check completed an MCP handshake.

Registry name
dev.tanod/web
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
279 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Web search for agents: page to Markdown, screenshots, news search, metadata, sitemaps and RDAP.
Listing
From the official MCP registry (active).
Recent checks of Web Reader & Search (Tanod)
CheckedResultHandshake
1 hour agoHandshake completed279 ms
7 hours agoHandshake completed315 ms
2 days agoHandshake completed834 ms
4 days agoHandshake completed6.11 s
7 days agoHandshake completed962 ms
9 days agoHandshake completed302 ms
11 days agoHandshake completed289 ms
14 days agoHandshake completed323 ms
15 days agoHandshake completed2.07 s
18 days agoHandshake completed245 ms
20 days agoHandshake completed309 ms
21 days agoHandshake completed265 ms
23 days agoHandshake completed303 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 Web Reader & Search (Tanod) and makes no claim about it beyond what these checks measured.