FCC Broadband Map
REMOTE · MCP.OLYPORT.COM · SCANNED SEP 24
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 → Why this is hard to 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 Usability68
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the FCC Broadband Map MCP server?
FCC Broadband Map is a hosted endpoint at https://mcp.olyport.com/fcc-broadband/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.olyport.com
claude mcp add --transport http com-olyport-fcc-broadband 'https://mcp.olyport.com/fcc-broadband/mcp'
{
"mcpServers": {
"com-olyport-fcc-broadband": {
"url": "https://mcp.olyport.com/fcc-broadband/mcp"
}
}
} {
"servers": {
"com-olyport-fcc-broadband": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://mcp.olyport.com/fcc-broadband/mcp"
}
}
} assistant mcp add com-olyport-fcc-broadband -t streamable-http -u '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.
- 26 Aug 26 77
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- 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 0
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 24 Sept 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 |
Background: What to check on a remote MCP endpoint →
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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
What is the FCC Broadband Map MCP server?
FCC Broadband Map is an MCP server listed in the public MCP registry as com.olyport/fcc-broadband. Broadband availability, providers, speeds, and BEAD classification from the FCC. This page covers its hosted endpoint (https://mcp.olyport.com/fcc-broadband/mcp).
Is the FCC Broadband Map MCP server safe to use?
FCC Broadband Map scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FCC Broadband Map MCP server expose?
FCC Broadband Map exposes 4 tools: get_broadband_by_location, get_broadband_summary_by_county, get_broadband_summary_by_state, get_providers_by_county. Their descriptions and schemas cost roughly 929 tokens of context every time the server is loaded.
Does the FCC Broadband Map MCP server require authentication?
No. We connected to FCC Broadband Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FCC Broadband Map MCP server still maintained?
FCC Broadband Map is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.