Remote MCP · Endpoint

cloud.fetcher/fetcher MCP server

No. cloud.fetcher/fetcher answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
47 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 19 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
2 hours agoHandshake completed47 ms
14 hours agoHandshake completed283 ms
1 day agoHandshake completed221 ms
3 days agoHandshake completed236 ms
4 days agoHandshake completed40 ms
4 days agoHandshake completed285 ms
5 days agoHandshake completed70 ms
6 days agoHandshake completed324 ms
8 days agoHandshake completed448 ms
11 days agoHandshake completed190 ms
13 days agoHandshake completed207 ms
16 days agoHandshake completed299 ms
18 days agoHandshake completed413 ms
20 days agoHandshake completed196 ms
22 days agoHandshake completed59 ms
24 days agoHandshake completed46 ms
26 days agoHandshake completed335 ms
28 days agoHandshake completed226 ms
29 days agoHandshake completed206 ms

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

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.