Remote MCP · Endpoint

FetchPan MCP server

No. FetchPan answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://fetchpan.com/mcp

The last check completed an MCP handshake.

Registry name
com.fetchpan/fetchpan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
415 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Direct download URLs from Baidu, Quark, PikPak, Rapidgator and more. First files free, no sign-up.
Listing
From the official MCP registry (active).
Recent checks of FetchPan
CheckedResultHandshake
57 minutes agoHandshake completed415 ms
13 hours agoHandshake completed375 ms
1 day agoHandshake completed406 ms
2 days agoHandshake completed502 ms
4 days agoHandshake completed855 ms
7 days agoHandshake completed421 ms
9 days agoHandshake completed961 ms
12 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
23 days agoCredentials required—

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with FetchPan and makes no claim about it beyond what these checks measured.