Remote MCP · Endpoint

ProofFetch MCP server

No. ProofFetch answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://prooffetch.tryneverclosed.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.equinoxaifinance-rgb/proof-fetch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
638 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cited web text extraction for agents: 25 free extractions per key, then 500 for $5.00 via Stripe.
Listing
From the official MCP registry (active).
Recent checks of ProofFetch
CheckedResultHandshake
4 hours agoHandshake completed638 ms
10 days agoHandshake completed417 ms
11 days agoHandshake completed367 ms
11 days agoHandshake completed379 ms
13 days agoHandshake completed159 ms
14 days agoHandshake completed260 ms
15 days agoHandshake completed196 ms
16 days agoHandshake completed234 ms
17 days agoHandshake completed53 ms
19 days agoHandshake completed277 ms
22 days agoHandshake completed120 ms
24 days agoHandshake completed345 ms
26 days agoHandshake completed139 ms
29 days agoHandshake completed121 ms

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

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