Remote MCP · Endpoint

FluxProof MCP server

No. FluxProof answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fluxproof.tryneverclosed.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.equinoxaifinance-rgb/fluxproof
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP.
Listing
From the official MCP registry (active).
Recent checks of FluxProof
CheckedResultHandshake
1 hour agoHandshake completed159 ms
10 hours agoHandshake completed222 ms
1 day agoHandshake completed255 ms
2 days agoHandshake completed178 ms
4 days agoHandshake completed162 ms
4 days agoHandshake completed173 ms
5 days agoHandshake completed243 ms
6 days agoHandshake completed154 ms
8 days agoHandshake completed102 ms
11 days agoHandshake completed209 ms
13 days agoHandshake completed178 ms
16 days agoHandshake completed184 ms
18 days agoHandshake completed312 ms
20 days agoHandshake completed299 ms
22 days agoHandshake completed81 ms

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

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