# FCC Broadband Map (remote · mcp.olyport.com)

Broadband availability, providers, speeds, and BEAD classification from the FCC

- Trust score: 64/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.olyport.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp.md), [page](https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp)

## Channel facts

- Endpoint: `https://mcp.olyport.com/fcc-broadband/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-olyport-fcc-broadband https://mcp.olyport.com/fcc-broadband/mcp
```

### Codex

```toml
[mcp_servers.com-olyport-fcc-broadband]
url = "https://mcp.olyport.com/fcc-broadband/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-olyport-fcc-broadband": {
      "type": "remote",
      "url": "https://mcp.olyport.com/fcc-broadband/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-olyport-fcc-broadband --url https://mcp.olyport.com/fcc-broadband/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-olyport-fcc-broadband:
    url: "https://mcp.olyport.com/fcc-broadband/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 63, +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.

### 2026-07-31 (score 62, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 58, +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.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (4)

### `get_broadband_by_location` (~287 tokens)

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).

Input parameters:

- `as_of_date` (string)
- `latitude` (number, required)
- `longitude` (number, required)
- `speed_download` (integer)
- `speed_upload` (integer)
- `technology_code` (integer)

Output parameters:

- `result` (string)

### `get_broadband_summary_by_county` (~215 tokens)

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).

Input parameters:

- `as_of_date` (string)
- `county_fips` (string, required)
- `speed_download` (integer)
- `speed_upload` (integer)

Output parameters:

- `result` (string)

### `get_broadband_summary_by_state` (~186 tokens)

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).

Input parameters:

- `as_of_date` (string)
- `speed_download` (integer)
- `speed_upload` (integer)
- `state_fips` (string, required)

Output parameters:

- `result` (string)

### `get_providers_by_county` (~241 tokens)

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).

Input parameters:

- `as_of_date` (string)
- `county_fips` (string, required)
- `speed_download` (integer)
- `speed_upload` (integer)
- `technology_code` (integer)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp#diagnostics

## Score history

- 2026-08-04: 64
- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://mcp.olyport.com/fcc-broadband/mcp
- Website: https://olyport.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-olyport-fcc-broadband/fcc-broadband-mcp