Remote MCP · Endpoint
io.github.cyanheads/fcc-broadband-mcp-server MCP server
No. io.github.cyanheads/fcc-broadband-mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://fcc-broadband.caseyjhand.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cyanheads/fcc-broadband-mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 279 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- FCC broadband availability, coverage analysis, and digital divide data for US geographies.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 279 ms |
| 1 day ago | Handshake completed | 746 ms |
| 2 days ago | Handshake completed | 323 ms |
| 3 days ago | Handshake completed | 281 ms |
| 4 days ago | Handshake completed | 264 ms |
| 5 days ago | Handshake completed | 241 ms |
| 6 days ago | Handshake completed | 332 ms |
| 9 days ago | Handshake completed | 271 ms |
| 11 days ago | Handshake completed | 264 ms |
| 14 days ago | Handshake completed | 307 ms |
| 16 days ago | Handshake completed | 789 ms |
| 18 days ago | Handshake completed | 83 ms |
| 20 days ago | Handshake completed | 141 ms |
| 22 days ago | Handshake completed | 140 ms |
| 24 days ago | Handshake completed | 114 ms |
| 26 days ago | Handshake completed | 108 ms |
| 27 days ago | Handshake completed | 120 ms |
| 29 days ago | Handshake completed | 389 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.cyanheads/fcc-broadband-mcp-server and makes no claim about it beyond what these checks measured.