Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/fcc-broadband-mcp-server

REMOTE · FCC-BROADBAND.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21

FCC broadband availability, coverage analysis, and digital divide data for US geographies.

0 this week 82 Trust /100
Trust breakdown (7 categories)

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 Security66
  • 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 9 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3384 tokens (~338/item across 10 items; 9 tools + 1 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.cyanheads/fcc-broadband-mcp-server server?

io.github.cyanheads/fcc-broadband-mcp-server is a hosted endpoint at https://fcc-broadband.caseyjhand.com/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 · fcc-broadband.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-fcc-broadband-mcp-server 'https://fcc-broadband.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-fcc-broadband-mcp-server": {
      "url": "https://fcc-broadband.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-fcc-broadband-mcp-server": {
      "type": "http",
      "url": "https://fcc-broadband.caseyjhand.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cyanheads-fcc-broadband-mcp-server]
url = "https://fcc-broadband.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-fcc-broadband-mcp-server": {
      "type": "remote",
      "url": "https://fcc-broadband.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-fcc-broadband-mcp-server --url 'https://fcc-broadband.caseyjhand.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-fcc-broadband-mcp-server:
    url: "https://fcc-broadband.caseyjhand.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-fcc-broadband-mcp-server": {
      "Transport": "http",
      "Url": "https://fcc-broadband.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-fcc-broadband-mcp-server -t streamable-http -u 'https://fcc-broadband.caseyjhand.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cyanheads-fcc-broadband-mcp-server": {
      "type": "http",
      "url": "https://fcc-broadband.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 0
    • Server version: 0.2.2 → 0.2.3 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

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

  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 4 Sept 26 0
    • Stability: 0.97 → pass security
  • 3 Sept 26 0
    • Stability: pass → 0.97 functional
  • 26 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
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.2.1 → 0.2.2 functional
Diagnostics

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 21 Sept 2026 · Probed https://fcc-broadband.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of fcc-broadband.caseyjhand.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
fcc-broadband.caseyjhand.com. Verified address RRset verified with the apex keys
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=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fcc-broadband.caseyjhand.com/mcp Verified 200
http (plaintext) http://fcc-broadband.caseyjhand.com/mcp HTTPS enforced 301 https://fcc-broadband.caseyjhand.com/mcp
MCP tools · 9 exposed · ~3,124 tokens

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 →

Tool Tokens
fcc_compare_areas ~351

Compares broadband coverage metrics across multiple geographies of the same type and returns a ranked table sorted by unserved or underserved population. Answers "which counties in this state have the worst broadband access?" and drives BEAD funding prioritization. Provide up to 50 geography IDs, or set compare_all_states=true for all 50 states + DC. Data is from FCC Form 477 (as of June 2021).

NameTypeReqDescription
compare_all_statesbooleanWhen true, compares all 50 states + DC. Overrides geography_ids. Requires geography_type="state".
geography_idsarrayArray of FIPS GEOIDs to compare (up to 50). For all 50 states, omit and set compare_all_states=true.
geography_typestringyesGeographic level to compare. Must be uniform across all geographies in the comparison.
sort_bystring"unserved_pct" = share of population with no broadband (default). "unserved_pop" = raw headcount for BEAD funding. "coverage_pct" = share with any coverage. "competitive_pct" = share with 2+ provider…
speed_downstringDownload speed threshold in Mbps. 25 = FCC legacy standard. 100 = BEAD program standard.
tech_filterstringTechnology filter. "acfosw" = any wired or fixed wireless. "f" = fiber only. "c" = cable only. "a" = DSL. "s" = satellite. "w" = fixed wireless.
NameTypeReqDescription
appliedFiltersobjectFilters and parameters applied to this comparison.
areasarrayRanked comparison of geographies by the selected sort field.
dataVintagestringData vintage — Form 477 data as of June 2021.
errorobjectPresent when the call failed. Absent on success.
geographyTypestringGeography type compared.
sortBystringRanking field used.
speedDownMbpsnumberSpeed threshold in Mbps.
techFilterstringTechnology filter applied.
totalAreasnumberTotal number of areas compared.

No examples provided.

fcc_find_underserved ~396

Finds geographic areas with limited or no broadband coverage at a given speed threshold, ranked by unserved population. The core tool for BEAD program analysis and broadband equity research. Accepts a state abbreviation to narrow scope or runs nationwide. Defaults to rural areas where underservice is most concentrated. Data is from FCC Form 477 (as of June 2021).

NameTypeReqDescription
geography_typestringGeographic granularity for results. "county" is most useful for policy analysis and BEAD eligibility. "cd" = congressional district. "place" = census-designated place. "cbsa" = metro area.
limitintegerMaximum number of areas to return, ranked by unserved population (descending).
min_unserved_popintegerMinimum population with no coverage to include. Defaults to 1, which keeps fully covered areas out of a ranking of underserved ones. Set to 0 to rank every area regardless of unserved population, or…
speed_downstringDownload speed threshold in Mbps for defining "underserved." 25 = FCC legacy standard. 100 = BEAD program standard.
statestring2-letter USPS state or territory code (e.g., "WY", "MS", "PR") to limit scope. An unrecognized code is rejected, not ignored. Omit for nationwide search — returns top areas only.
tech_filterstringTechnology filter. "acfosw" = any wired or fixed wireless. "f" = fiber only. "c" = cable only.
urban_rural_filterstringDefaults to rural ("R") — where underservice is most concentrated. Use "U" to find underserved urban areas (digital redlining research). Set to "all" for both.
NameTypeReqDescription
appliedFiltersobjectFilters applied to this query.
areasarrayRanked list of underserved areas.
capnumberThe limit that was applied. Present when truncated.
dataVintagestringData vintage — Form 477 data as of June 2021.
errorobjectPresent when the call failed. Absent on success.
geographyTypestringGeography type returned.
noticestringGuidance about the result set — how to broaden the filters when nothing matched, and how to narrow the query when the upstream scan hit its row ceiling. Absent when neither applies.
scanRowCapnumberRaw upstream row ceiling that bound the scan. Present only when scanTruncated is true.
scanTruncatedbooleanTrue when the upstream row scan stopped at its ceiling before reaching the end of the matching data, so totalFound and the ranking cover only the portion that was scanned. Absent when the scan read e…
shownnumberNumber of areas returned after applying the limit. Present when truncated.
speedDownMbpsnumberSpeed threshold used in Mbps.
totalFoundnumberTotal number of areas found before applying the limit filter.
truncatedbooleanTrue when more areas matched than the limit returned. Absent when not truncated.
urbanRuralFilterstringUrban/rural filter applied.

No examples provided.

fcc_geocode_block ~211

Converts a latitude/longitude coordinate to a 15-digit census block FIPS code, plus county FIPS, county name, state FIPS, state code, and state name. This is the required prerequisite for fcc_search_availability since the broadband dataset is indexed by census block, not address. The block is resolved against 2010 census boundaries, the vintage the Form 477 deployment dataset is keyed by, so the returned blockFips can be passed straight to fcc_search_availability; a 2020-vintage block ID from another source will not match. Uses the FCC public Geo API — no authentication required.

NameTypeReqDescription
latitudenumberyesLatitude of the location in decimal degrees (e.g., 47.6062 for Seattle, WA). Must be within the continental US, Alaska, Hawaii, or US territories.
longitudenumberyesLongitude of the location in decimal degrees (e.g., -122.3321 for Seattle, WA). Negative for western hemisphere.
NameTypeReqDescription
blockFipsstring15-digit census block FIPS code on 2010 census boundaries (e.g., "530330081002024"). Pass this to fcc_search_availability to look up broadband providers.
censusVintagestringDecennial census whose block boundaries blockFips belongs to. Always "2010" — the vintage the Form 477 deployment dataset behind fcc_search_availability is keyed by.
countyFipsstring5-digit county FIPS code (e.g., "53033" for King County, WA).
countyNamestringHuman-readable county name (e.g., "King").
errorobjectPresent when the call failed. Absent on success.
stateCodestring2-letter state abbreviation (e.g., "WA").
stateFipsstring2-digit state FIPS code (e.g., "53" for Washington).
stateNamestringFull state name (e.g., "Washington").

No examples provided.

fcc_get_coverage_summary ~481

Returns a broadband coverage summary for a geography — population with zero, one, two, or three-plus providers at a given speed threshold, split by urban/rural and tribal/non-tribal segments. The primary tool for digital divide and equity analysis. Supports state, county, congressional district, census place, CBSA (metro area), tribal area, and national level. Data is from FCC Form 477 (as of June 2021). Use 100 Mbps as the speed threshold for BEAD program policy analysis.

NameTypeReqDescription
geography_idstringFIPS GEOID for the geography. State: 2-digit (e.g., "06" for California). County: 5-digit (e.g., "06037" for LA County). Congressional district: 4-digit state+district (e.g., "0601"). CBSA: 5-digit c…
geography_typestringyesGeographic aggregation level. "nation" = US-wide totals (geography_id not needed). "cd" = congressional district. "place" = census-designated place. "cbsa" = core-based statistical area (metro area).…
speed_downstringMinimum download speed threshold in Mbps. 25 = FCC legacy broadband definition. 100 = BEAD program standard (use this for current policy analysis). "0.2" = any service above 200 Kbps.
tech_filterstringTechnology filter. "acfosw" = any wired or fixed wireless (recommended baseline). "f" = fiber only. "c" = cable only. "a" = ADSL/DSL only. "s" = satellite only. "w" = fixed wireless only. Mix letters…
tribal_filterstringFilter to tribal ("T") or non-tribal ("N") areas. Use "T" to assess Native American connectivity gaps.
urban_rural_filterstringFilter to urban ("U") or rural ("R") areas only, or "all" for both combined. Rural breakdown is key for BEAD program analysis.
NameTypeReqDescription
appliedFiltersobjectFilters applied to this query.
breakdownarrayPer-segment breakdown by urban/rural and tribal/non-tribal.
competitivePctnumberPercentage with two or more providers.
coveragePctnumberPercentage of population with at least one provider at the given speed.
dataVintagestringData vintage — Form 477 data as of June 2021.
errorobjectPresent when the call failed. Absent on success.
geographyobjectThe queried geography.
populationobjectPopulation counts by provider availability tier.
speedDownMbpsnumberDownload speed threshold used in Mbps.
techFilterstringTechnology filter applied.
unservedPctnumberPercentage with zero providers — FCC "unserved" definition.

No examples provided.

fcc_get_provider ~127

Returns a national-level coverage profile for a specific holding company (by hoconum): technologies deployed and the population covered at each download speed tier. Population figures come from the FCC provider summary table and count each person once, regardless of how many technologies the provider uses to reach them. Use fcc_search_providers to find valid hoconum values. Data is from FCC Form 477 (as of June 2021).

NameTypeReqDescription
hoconumstringyesHolding company number from fcc_search_providers — digits only, e.g. "130317" for Comcast Corporation.
NameTypeReqDescription
dataVintagestringData vintage — Form 477 data as of June 2021.
errorobjectPresent when the call failed. Absent on success.
hoconumstringHolding company number.
holdingCompanyNamestringHolding company name.
speedTierPopulationarrayNational covered population by download speed tier, from the FCC all-technology rollup. Tiers with no coverage are omitted; empty when the provider reports no population coverage.
techCodesarrayTechnology codes this provider reports nationally. Empty when the provider reports no population coverage (e.g. business-only carriers).
techLabelsarrayHuman-readable technology descriptions.

No examples provided.

fcc_list_downloads ~440

Lists downloadable BDC data files for a specific as-of date — fixed availability by state and provider, mobile coverage, and challenge data — with file metadata (provider, state, technology, record count). Download URLs are included for each file. Requires FCC BDC API credentials (FCC_BDC_USERNAME and FCC_BDC_HASH_VALUE). Use fcc_list_filing_periods first to determine valid as_of_date values (BDC dates start June 2022); a date that is not on the calendar, or that falls before the first BDC period, is rejected without credentials, while a well-formed date the BDC API does not publish is rejected once credentials let the published set be read. One as-of date can carry thousands of per-provider files, so results come back a page at a time: totalFiles counts every file matching the filters, the response reports the offset and the count on this page, and it carries a nextOffset to pass back for the following page until the last one, which omits it.

NameTypeReqDescription
as_of_datestringyesBDC as-of date in YYYY-MM-DD format (e.g., "2024-06-30"). Get valid dates from fcc_list_filing_periods with include_bdc=true.
categorystringFile category. "State" = per-state coverage files. "Provider" = per-provider files. "Summary" = aggregate coverage tables.
data_typestring"availability" = ISP-reported coverage files (by state and provider). "challenge" = consumer and government dispute records.
limitintegerMaximum number of files to return on one page.
offsetintegerZero-based index of the first file to return, within the files matching the filters. Start at 0 and follow the nextOffset each response carries.
provider_namestringPartial provider holding company name to filter results (case-insensitive).
statestringFilter to one state's files (2-letter abbreviation, e.g., "WA").
technology_typestringFilter to a specific technology type of coverage data.
NameTypeReqDescription
appliedFiltersobjectFilters applied to this query.
asOfDatestringThe queried as-of date.
countnumberFiles actually returned on this page. Zero both when nothing matched and when the offset is past the end; the notice says which.
dataTypestringData type queried (availability or challenge).
errorobjectPresent when the call failed. Absent on success.
filesarrayDownloadable BDC files on this page, in the order the BDC API lists them.
nextOffsetnumberOffset to pass back for the next page. Omitted on the last page and when the offset is past the end.
noticestringWhere this page sits in the matching set and how to continue — or, when the page is empty, whether nothing matched the filters or the offset ran past the end.
offsetnumberZero-based index of the first file on this page.
pageSizenumberMaximum files one page returns — the limit that was applied.
totalFilesnumberFiles matching the filters across every page, not just this one. Compare against the count enrichment field to see how much of the set this page holds.
truncatedbooleanTrue when this page holds fewer files than totalFiles, so more pages exist.

No examples provided.

fcc_list_filing_periods ~156

Returns available data vintages: Form 477 filing periods (hardcoded Jun 2015 – Jun 2021, always available) and BDC as-of dates from the authenticated API (Jun 2022 onward, requires credentials). Call this before fcc_list_downloads to determine valid as_of_date values. Note: there is a data gap between June 2021 (last Form 477) and June 2022 (first BDC filing period).

NameTypeReqDescription
include_bdcbooleanWhen true, also fetches BDC as-of dates from the authenticated API (requires FCC_BDC_USERNAME and FCC_BDC_HASH_VALUE). When false (default), returns only hardcoded Form 477 periods.
NameTypeReqDescription
bdcCountnumberNumber of BDC periods returned (0 when credentials not configured or include_bdc=false).
dataNotestringNote on data availability and the Form 477 vs. BDC gap.
errorobjectPresent when the call failed. Absent on success.
form477CountnumberNumber of Form 477 periods returned (always available).
hasBdcCredentialsbooleanWhether BDC API credentials are configured in this deployment.
periodsarrayAvailable filing periods sorted newest first.

No examples provided.

fcc_search_availability ~379

Queries broadband providers and advertised speeds at a census block from FCC Form 477 data (as of June 2021). Answers "which ISPs serve this location and what speeds do they offer?" — the core tool for address-level broadband lookup. Requires a 15-digit census block FIPS code; use fcc_geocode_block to convert coordinates first. Data reflects ISP-reported availability at the block level, which may overstate actual coverage for some addresses.

NameTypeReqDescription
block_fipsstringyes15-digit census block FIPS code on 2010 census boundaries, the vintage this Form 477 dataset is keyed by (e.g., "530330081002024"). Obtain from fcc_geocode_block using address coordinates — a 2020-vi…
consumerbooleanFilter to consumer service (true) or business service (false). Omit to return both consumer and business offerings.
min_speed_downnumberMinimum advertised download speed in Mbps to include in results. Omit to return all providers regardless of speed.
tech_filterarrayTechnology codes to filter, from the complete Form 477 taxonomy: 0=All other, 10=Asymmetric xDSL, 11=ADSL2, 12=VDSL, 20=Symmetric xDSL, 30=Other copper wireline, 40=Cable modem, 41=Cable modem DOCSIS…
NameTypeReqDescription
appliedFiltersobjectFilters applied to this query.
blockFipsstringThe queried census block FIPS code.
dataVintagestringData vintage — all Form 477 data on FCC Open Data is as of June 2021. For newer BDC data, use fcc_list_downloads.
errorobjectPresent when the call failed. Absent on success.
noticestringRecovery hint when no providers are found — suggests how to broaden the query. Absent on successful results.
providersarrayISP offerings reported for this census block.
totalProvidersnumberTotal number of distinct holding companies offering service at this block.

No examples provided.

fcc_search_providers ~583

Searches for ISPs by holding company name, filtered by state and technology type. Returns a deduplicated list of matching providers with hoconum identifiers for follow-up calls to fcc_get_provider. Answers "which ISPs serve Washington with fiber?" and "find all Comcast entities." Geographic filtering is state-level; sub-state granularity requires cross-referencing block data. Against the live FCC API the search reads a bounded window of deployment rows to find which holding companies match, so when scanTruncated comes back true the providers are a sample of the matches rather than every one of them and no true match count is available; a narrower filter raises the share of matches the sample surfaces but cannot make it complete, and only a deployment running the local Form 477 mirror returns every match. The sample is of which companies come back — every company that does carries its complete national footprint, since statesServed and techCodes are resolved per company rather than read off the window, at the cost of one lookup per provider returned. Data is from FCC Form 477 (as of June 2021).

NameTypeReqDescription
limitintegerMaximum number of distinct providers to return.
name_searchstringPartial holding company name to search (case-insensitive). e.g., "Comcast", "T-Mobile", "Frontier". Omit to list all providers in a state.
statestring2-letter state abbreviation (e.g., "WA") to limit results to providers serving that state. Matches individual deployment filings, so every filter given must hold on one filing together — a provider i…
tech_filterarrayTechnology codes to filter, from the complete Form 477 taxonomy: 0=All other, 10=Asymmetric xDSL, 11=ADSL2, 12=VDSL, 20=Symmetric xDSL, 30=Other copper wireline, 40=Cable modem, 41=Cable modem DOCSIS…
NameTypeReqDescription
appliedFiltersobjectFilters applied to this query.
capnumberThe limit that was applied. Present when capped.
dataVintagestringData vintage — Form 477 data as of June 2021.
errorobjectPresent when the call failed. Absent on success.
noticestringGuidance about the result set — that the list was capped at the limit, that the upstream scan returned a sample rather than every match, and how to broaden the search when nothing matched. Absent whe…
providersarrayMatching providers, deduplicated by holding company.
scanRowCapnumberRaw upstream row ceiling that bound the scan. Present only when scanTruncated is true.
scanTruncatedbooleanTrue when the upstream row scan stopped at its ceiling before reaching the end of the matching data, so the providers returned are a sample of the matches rather than the complete set. Bounds which c…
shownnumberNumber of providers returned. Present when capped.
totalCountnumberDistinct providers matching the query, before the limit. Present only when the scan read every matching row — absent when scanTruncated is true, because the true match count is then unknown.
totalFoundnumberProviders in this response. Not the number matching the query — that is totalCount, and it is only knowable when the scan read every matching row.
truncatedbooleanTrue when results were capped at the limit and more providers may exist. Absent when not capped.

No examples provided.

Common questions

What is the io.github.cyanheads/fcc-broadband-mcp-server server?

io.github.cyanheads/fcc-broadband-mcp-server is listed in the public MCP registry as io.github.cyanheads/fcc-broadband-mcp-server. FCC broadband availability, coverage analysis, and digital divide data for US geographies. This page covers its hosted endpoint (https://fcc-broadband.caseyjhand.com/mcp).

Is the io.github.cyanheads/fcc-broadband-mcp-server server safe to use?

io.github.cyanheads/fcc-broadband-mcp-server scores 82 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 io.github.cyanheads/fcc-broadband-mcp-server server expose?

io.github.cyanheads/fcc-broadband-mcp-server exposes 9 tools: fcc_geocode_block, fcc_search_availability, fcc_get_coverage_summary, fcc_search_providers, fcc_get_provider, and 4 more. Their descriptions and schemas cost roughly 3,124 tokens of context every time the server is loaded.

Does the io.github.cyanheads/fcc-broadband-mcp-server server require authentication?

No. We connected to io.github.cyanheads/fcc-broadband-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/fcc-broadband-mcp-server server still maintained?

io.github.cyanheads/fcc-broadband-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.