A remote MCP server that gives an assistant FCC-sourced US internet availability and telecom market data by address, city, coordinate or provider.
What you can do
Check internet availability at a US street address, latitude/longitude or FCC location ID, listing providers, technologies and speeds with fiber first and the filing vintage stated. Look up a provider's canonical profile, FCC registration numbers, filed technologies and grounded overview sections. Get city-level coverage intelligence such as provider counts, fiber share and dominant technologies. Get neighborhood-level (Res-8 cell) intelligence on provider mix, fiber density, competition and underserved status. Get national market context on provider totals, registered locations and technology mix.
When to use it
Useful when answering questions about US broadband options for a specific address or area, comparing providers, or discussing the fiber transition and market size with sourced figures rather than guesses.
Requirements
A remote streamable HTTP endpoint; no package, API key, environment variable or header is declared. Network access to the endpoint is needed.
Before you install
Answers are derived from FCC filings and carry a stated vintage, so they may lag real-world build-outs; treat them as filing-based evidence rather than a live service check. No credentials or write actions are declared.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.fiberfinder%2Ftelecom-truth/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Authoritative internet availability for one US location. Give a street address (or lat/lng, or an FCC location_id from a previous call) and get every provider that files service there — technology, download/upload speeds — fiber options first, with the FCC filing vintage the answer derives from and a link to the live page. Data: FCC Broadband Data Collection filings cross-verified against a 200M-address evidence ledger.
Parameterslatlngaddresslocation_id
provider_profile
Provider profile
Canonical profile of a US internet provider by name (handles brand variants, e.g. 'ATT', 'Google Fiber'). Returns the canonical identity, FCC registration numbers, technologies filed, the live profile URL, and — when precomputed — an answer pack of grounded sections (overview, coverage, measured-vs-claimed speeds, competition, recent signals, trajectory). Use it to disambiguate providers before making claims about them.
Parametersnamerequired
area_intelligence
City coverage intelligence
Coverage intelligence for a US city: how many providers file service, fiber availability share, and the dominant technologies — honest numbers with their grain and vintage stated. Give city and two-letter state.
Parameterscityrequiredstaterequired
location_intelligence
Neighborhood (hex) intelligence
Res-8 hex intelligence (~0.46 km cells) for any US coordinate: how many FCC locations, providers by technology, fiber density, competition and underserved status, and best available speeds in that immediate neighborhood. This is the herd-mentality context (how much of the block already has fiber) and the build-predictability grain. Give lat+lng, or an H3 res-8 hex_id directly.
Parameterslatlnghex_id
industry_overview
US telecom industry overview
US telecom market at national scale: total providers, total FCC-registered locations, technology mix (how many locations have fiber vs cable vs other filed), and the filing vintages held. The market-context tool for questions about the US broadband industry, the fiber transition, or how big the space is.
Takes no parameters.
Version history
1
v1.4.0LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.