FCC Broadband Map
REMOTE · MCP.OLYPORT.COM · SCANNED AUG 3
Broadband availability, providers, speeds, and BEAD classification from the FCC
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 929 tokens (~232/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.olyport.com
claude mcp add --transport http com-olyport-fcc-broadband https://mcp.olyport.com/fcc-broadband/mcp
[mcp_servers.com-olyport-fcc-broadband] url = "https://mcp.olyport.com/fcc-broadband/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-olyport-fcc-broadband": {
"type": "remote",
"url": "https://mcp.olyport.com/fcc-broadband/mcp",
"enabled": true
}
}
} openclaw mcp add com-olyport-fcc-broadband --url https://mcp.olyport.com/fcc-broadband/mcp --transport streamable-http
mcp_servers:
com-olyport-fcc-broadband:
url: "https://mcp.olyport.com/fcc-broadband/mcp" {
"mcpServers": {
"com-olyport-fcc-broadband": {
"type": "http",
"url": "https://mcp.olyport.com/fcc-broadband/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.olyport.com/fcc-broadband/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.olyport.com | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6ab1c2dfb0fcb68c1046393bb51c5b1117b |
| SANs: mcp.olyport.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of mcp.olyport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| olyport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.olyport.com/fcc-broadband/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.olyport.com/fcc-broadband/mcp | HTTPS enforced | 308 | https://mcp.olyport.com/fcc-broadband/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_broadband_by_location ~287
Get broadband providers and availability at a specific lat/lon location. Returns a list of broadband providers serving the location with their advertised download/upload speeds and technology types. Includes BEAD classification (unserved/underserved/served) based on max available speeds. NOTE: The FCC Broadband Map API has bot protection and may reject requests. If you get an error, the API endpoint may have changed. The FCC updates this API frequently without notice. Args: latitude: Location latitude (e.g. 38.8977 for Washington DC). longitude: Location longitude (e.g. -77.0365 for Washington DC). technology_code: Filter by technology (0=All, 10=Copper, 40=Cable, 50=Fiber, 60=Satellite, 70=Fixed Wireless). speed_download: Minimum download speed in Mbps (default 25). speed_upload: Minimum upload speed in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | — | — |
| latitude | number | yes | — |
| longitude | number | yes | — |
| speed_download | integer | — | — |
| speed_upload | integer | — | — |
| technology_code | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_broadband_summary_by_county ~215
Get broadband availability statistics for a county. Returns aggregated broadband data including provider counts, technology availability, and BEAD-relevant metrics (unserved/underserved/served location percentages). NOTE: County-level summary endpoints may not be directly available in all API versions. This tool attempts multiple endpoint patterns. Args: county_fips: 5-digit county FIPS code (e.g. '11001' for Washington DC, '53033' for King County WA). Always a string, never an integer. speed_download: Minimum download speed threshold in Mbps (default 25). speed_upload: Minimum upload speed threshold in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | — | — |
| county_fips | string | yes | — |
| speed_download | integer | — | — |
| speed_upload | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_broadband_summary_by_state ~186
Get state-level broadband availability summary. Returns aggregated broadband statistics for the state including provider counts and technology deployment. Useful for BEAD program analysis to identify states with significant unserved/underserved populations. Args: state_fips: 2-digit state FIPS code (e.g. '53' for Washington, '11' for DC). Always a string, never an integer. speed_download: Minimum download speed threshold in Mbps (default 25). speed_upload: Minimum upload speed threshold in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | — | — |
| speed_download | integer | — | — |
| speed_upload | integer | — | — |
| state_fips | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_providers_by_county ~241
Get list of broadband providers serving a county. Returns provider names, technology types, and speed tiers available in the specified county. Useful for BEAD applications to identify which providers serve an area and what technologies they deploy. Args: county_fips: 5-digit county FIPS code (e.g. '11001' for Washington DC, '53033' for King County WA). Always a string, never an integer. technology_code: Filter by technology (0=All, 10=Copper, 40=Cable, 50=Fiber, 60=Satellite, 70=Fixed Wireless). speed_download: Minimum download speed threshold in Mbps (default 25). speed_upload: Minimum upload speed threshold in Mbps (default 3). as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | — | — |
| county_fips | string | yes | — |
| speed_download | integer | — | — |
| speed_upload | integer | — | — |
| technology_code | integer | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.