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
244 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 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 completed244 ms
2 days agoHandshake completed190 ms
4 days agoHandshake completed171 ms
5 days agoHandshake completed244 ms
7 days agoHandshake completed237 ms
8 days agoHandshake completed1.29 s
9 days agoHandshake completed167 ms
12 days agoHandshake completed168 ms
13 days agoHandshake completed238 ms
15 days agoHandshake completed171 ms
16 days agoHandshake completed220 ms
18 days agoHandshake completed179 ms
19 days agoHandshake completed254 ms
20 days agoHandshake completed175 ms
20 days agoHandshake completed225 ms
21 days agoHandshake completed231 ms
22 days agoHandshake completed645 ms

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

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.