Remote MCP · Endpoint
4fetch MCP server
Yes, as of 1 hour ago: the request timed out.
DownLast checked 1 hour ago
Server URL
https://api.4fetch.com/mcp/v1/fetch
The last check failed: the request timed out.
- Registry name
- io.github.amit755/4fetch
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Fetch a URL and get clean Markdown with metadata. No API key required; rate-limited per IP.
- Website
- https://4fetch.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the request timed out | — |
| 1 day ago | Failed - the request timed out | — |
| 2 days ago | Failed - the request timed out | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 0 responding of 3.
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 4fetch and makes no claim about it beyond what these checks measured.