US telecom availability and intelligence by address, with FCC provenance. Fiber-first.
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
City name, e.g. 'Goshen'
Two-letter state, e.g. 'IN'
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.
| Argument | Type | Description |
|---|---|---|
| city* | string | City name, e.g. 'Goshen' |
| state* | string | Two-letter state, e.g. 'IN' |
{
"type": "object",
"required": [
"city",
"state"
],
"properties": {
"city": {
"type": "string",
"description": "City name, e.g. 'Goshen'"
},
"state": {
"type": "string",
"description": "Two-letter state, e.g. 'IN'"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| lat | number | Latitude (use with lng as an alternative to address) |
| lng | number | Longitude |
| address | string | US street address, e.g. '520 South 5th Street, Goshen, Indiana' |
| location_id | string | FCC location id from a previous check (skips address resolution) |
{
"type": "object",
"properties": {
"lat": {
"type": "number",
"description": "Latitude (use with lng as an alternative to address)"
},
"lng": {
"type": "number",
"description": "Longitude"
},
"address": {
"type": "string",
"description": "US street address, e.g. '520 South 5th Street, Goshen, Indiana'"
},
"location_id": {
"type": "string",
"description": "FCC location id from a previous check (skips address resolution)"
}
}
}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.
No arguments.
{
"type": "object",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| lat | number | Latitude |
| lng | number | Longitude |
| hex_id | string | H3 res-8 cell id (alternative to lat/lng) |
{
"type": "object",
"properties": {
"lat": {
"type": "number",
"description": "Latitude"
},
"lng": {
"type": "number",
"description": "Longitude"
},
"hex_id": {
"type": "string",
"description": "H3 res-8 cell id (alternative to lat/lng)"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| name* | string | Provider name or brand as a user said it |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Provider name or brand as a user said it"
}
}
}