Remote MCP · Endpoint

ContextFetch MCP server

Yes, as of 52 minutes ago: the request timed out.

DownLast checked 52 minutes ago

Server URL

https://api.contextfetch.dev/mcp

The last check failed: the request timed out.

Registry name
dev.contextfetch/mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
14 tools
Uptime, last 30 days
78.6% from 14 checks
Described by its publisher as
Web search and any page as LLM-ready Markdown for AI agents. Free keyless tier, no signup.
Listing
From the official MCP registry (active).
Recent checks of ContextFetch
CheckedResultHandshake
52 minutes agoFailed - the request timed out—
3 days agoFailed - the request timed out—
12 days agoHandshake completed461 ms
13 days agoHandshake completed326 ms
14 days agoHandshake completed327 ms
15 days agoHandshake completed362 ms
17 days agoHandshake completed360 ms
18 days agoHandshake completed325 ms
18 days agoHandshake completed383 ms
20 days agoHandshake completed370 ms
22 days agoHandshake completed329 ms
25 days agoHandshake completed513 ms
27 days agoFailed - the TLS certificate could not be verified—
29 days agoHandshake completed339 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 ContextFetch and makes no claim about it beyond what these checks measured.