Remote MCP · Endpoint

cloud.fetcher/fetcher MCP server

No. cloud.fetcher/fetcher answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.fetcher.cloud/mcp

The last check completed an MCP handshake.

Registry name
cloud.fetcher/fetcher
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
196 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.
Website
https://fetcher.cloud/
Repository
https://github.com/fetchercloud/fetcher-cloud
Listing
From the official MCP registry (active).
Recent checks of cloud.fetcher/fetcher
CheckedResultHandshake
1 hour agoHandshake completed196 ms
2 days agoHandshake completed59 ms
4 days agoHandshake completed46 ms
6 days agoHandshake completed335 ms
7 days agoHandshake completed226 ms
9 days agoHandshake completed206 ms
10 days agoHandshake completed269 ms
11 days agoHandshake completed243 ms
14 days agoHandshake completed31 ms
15 days agoHandshake completed289 ms
17 days agoHandshake completed471 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed172 ms
20 days agoHandshake completed154 ms
21 days agoHandshake completed202 ms
22 days agoHandshake completed193 ms
23 days agoHandshake completed271 ms
24 days agoHandshake completed182 ms

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

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 cloud.fetcher/fetcher and makes no claim about it beyond what these checks measured.