Remote MCP · Endpoint

dev.fetchgate/fetchgate MCP server

No. dev.fetchgate/fetchgate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fetchgate.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.fetchgate/fetchgate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.
Website
https://fetchgate.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.fetchgate/fetchgate
CheckedResultHandshake
1 hour agoHandshake completed53 ms
1 day agoHandshake completed69 ms
2 days agoHandshake completed535 ms
3 days agoHandshake completed83 ms
4 days agoHandshake completed198 ms
5 days agoHandshake completed78 ms
6 days agoHandshake completed156 ms
9 days agoHandshake completed610 ms
12 days agoHandshake completed145 ms
14 days agoHandshake completed204 ms
16 days agoHandshake completed222 ms
18 days agoHandshake completed127 ms
20 days agoHandshake completed152 ms
22 days agoHandshake completed185 ms
24 days agoHandshake completed124 ms
26 days agoHandshake completed51 ms
27 days agoHandshake completed36 ms
28 days agoHandshake completed401 ms

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