Remote MCP · Endpoint

fetcher.sh — web data for agents MCP server

No. fetcher.sh — web data for agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fetcher.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.fetcher/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
189 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
111 web-data endpoints across 11 services. Pay per call in USDC via x402.
Website
https://fetcher.sh/
Listing
From the official MCP registry (active).
Recent checks of fetcher.sh — web data for agents
CheckedResultHandshake
1 hour agoHandshake completed189 ms
1 day agoHandshake completed206 ms
2 days agoHandshake completed678 ms
3 days agoHandshake completed240 ms
4 days agoHandshake completed244 ms
5 days agoHandshake completed318 ms
6 days agoHandshake completed198 ms
9 days agoHandshake completed526 ms
12 days agoHandshake completed381 ms
14 days agoHandshake completed1.53 s
16 days agoHandshake completed289 ms
18 days agoHandshake completed203 ms
20 days agoHandshake completed244 ms
22 days agoHandshake completed190 ms
24 days agoHandshake completed171 ms
26 days agoHandshake completed244 ms
27 days agoHandshake completed237 ms
28 days agoHandshake completed1.29 s

The last 18 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 fetcher.sh — web data for agents and makes no claim about it beyond what these checks measured.