Remote MCP · Endpoint

FindBroadband MCP server

No. FindBroadband answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://www.findbroadbanddeals.com/api/mcp/standard

The last check completed an MCP handshake.

Registry name
com.findbroadbanddeals/broadband-deals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find cheap broadband deals
Listing
From the official MCP registry (active).
Recent checks of FindBroadband
CheckedResultHandshake
13 minutes agoHandshake completed319 ms
10 days agoHandshake completed314 ms
10 days agoHandshake completed204 ms
11 days agoHandshake completed210 ms
13 days agoHandshake completed289 ms
14 days agoHandshake completed2.54 s
14 days agoHandshake completed246 ms
15 days agoHandshake completed248 ms
17 days agoHandshake completed218 ms
19 days agoHandshake completed321 ms
21 days agoHandshake completed289 ms
24 days agoHandshake completed268 ms
26 days agoHandshake completed281 ms
28 days agoHandshake completed174 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 FindBroadband and makes no claim about it beyond what these checks measured.