Remote MCP · Endpoint

ProofFetch Lite (proof_fetch, read_clean, url_watch) MCP server

Yes, as of 7 hours ago: the hostname does not resolve.

DownLast checked 7 hours ago

Server URL

https://favor-skilled-ben-plugin.trycloudflare.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.trycloudflare.favor-skilled-ben-plugin/prooffetch
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
15.4% from 13 checks
Described by its publisher as
SSRF-safe URL proof receipts, clean markdown, and SHA-256 change watch for agents.
Listing
From the official MCP registry (active).
Recent checks of ProofFetch Lite (proof_fetch, read_clean, url_watch)
CheckedResultHandshake
7 hours agoFailed - the hostname does not resolve—
13 hours agoFailed - the hostname does not resolve—
2 days agoFailed - the hostname does not resolve—
4 days agoFailed - the hostname does not resolve—
7 days agoFailed - the hostname does not resolve—
9 days agoFailed - the hostname does not resolve—
11 days agoFailed - the hostname does not resolve—
14 days agoFailed - the hostname does not resolve—
16 days agoFailed - the hostname does not resolve—
18 days agoFailed - the hostname does not resolve—
20 days agoFailed - the hostname does not resolve—
21 days agoHandshake completed196 ms
23 days agoHandshake completed63 ms

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

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 ProofFetch Lite (proof_fetch, read_clean, url_watch) and makes no claim about it beyond what these checks measured.