io.github.fiberfinder/telecom-truth
REMOTE · MCP.FIBERFINDER.AI
US telecom availability and intelligence by address, with FCC provenance. Fiber-first.
Available components
Last scanned (8 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 841 tokens (~168/item across 5 items; 5 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_availability” rewrote its description, which is the text the model reads security
- Tool “location_intelligence” rewrote its description, which is the text the model reads security
- Schema quality: 141 → 168 ▼ functional
- Server version: 1.4.0 → 1.4.1 functional
- “check_availability” added an optional parameter “city” cosmetic
- “check_availability” added an optional parameter “state” cosmetic
- “check_availability” added an optional parameter “zip” cosmetic
- “check_availability” reworded the description of “address” cosmetic
- “check_availability” reworded the description of “lng” cosmetic
- “location_intelligence” reworded the description of “lat” cosmetic
- “location_intelligence” reworded the description of “lng” cosmetic
- 28 Sept 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 Sept 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
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 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
- 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
- 9 Aug 26 0
- Tool “provider_profile” rewrote its description, which is the text the model reads security
- 8 Aug 26 0
- Server version: 1.2.0 → 1.4.0 functional
- Tool “area_intelligence” changed its title: City coverage intelligence cosmetic
- Tool “check_availability” changed its title: Check internet availability cosmetic
- Tool “industry_overview” changed its title: US telecom industry overview cosmetic
- Tool “location_intelligence” changed its title: Neighborhood (hex) intelligence cosmetic
- Tool “provider_profile” changed its title: Provider profile cosmetic
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 5 Nov 2026 · Probed https://mcp.fiberfinder.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fiberfinder.ai | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 487511d2d63fffc813ac47f04e9b5aa5 |
| SANs: fiberfinder.ai, mcp.fiberfinder.ai, *.mcp.fiberfinder.ai | ||||||
| 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 insecure
Validation of mcp.fiberfinder.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| fiberfinder.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fiberfinder.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fiberfinder.ai/mcp | HTTPS enforced | 301 | https://mcp.fiberfinder.ai/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 →
area_intelligence City coverage intelligence ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. 'Goshen' |
| state | string | yes | Two-letter state, e.g. 'IN' |
No output schema declared.
No examples provided.
check_availability Check internet availability ~269
Internet availability and fiber context for a US address or area. Give one geography shape: a street address (for example '520 South Main Street, Goshen, Indiana 46526'), lat+lng, FCC location_id, 5-digit ZIP, city+state (for example Warsaw, IN), state, or a city alone for disambiguation candidates. Address answers are one FCC location; city/state/ZIP answers are explicitly area-level and never a guarantee at a door. Every answer states precision, grain, source, as_of, and a canonical live page.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address, e.g. '520 South Main Street, Goshen, Indiana 46526' |
| city | string | – | US city, e.g. 'Warsaw'. Pass state when known; city alone returns candidates. |
| lat | number | – | Latitude (use with lng as an alternative to address) |
| lng | number | – | Longitude (use with lat) |
| location_id | string | – | FCC location id from a previous check (skips address resolution) |
| state | string | – | Two-letter USPS code or full state name, e.g. 'IN' or 'Indiana' |
| zip | string | – | 5-digit US ZIP, e.g. '46580' |
No output schema declared.
No examples provided.
industry_overview US telecom industry overview ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
location_intelligence Neighborhood (hex) intelligence ~152
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. Give lat+lng (for example Goshen, IN: 41.5820, -85.8344), or an H3 res-8 hex_id directly.
| Name | Type | Req | Description |
|---|---|---|---|
| hex_id | string | – | H3 res-8 cell id (alternative to lat/lng) |
| lat | number | – | Latitude, e.g. 41.5820 for Goshen, IN |
| lng | number | – | Longitude, e.g. -85.8344 for Goshen, IN |
No output schema declared.
No examples provided.
provider_profile Provider profile ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Provider name or brand as a user said it |
No output schema declared.
No examples provided.
How do I install the io.github.fiberfinder/telecom-truth MCP server?
io.github.fiberfinder/telecom-truth is a hosted endpoint at https://mcp.fiberfinder.ai/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.fiberfinder.ai
claude mcp add --transport http fiberfinder-telecom-truth 'https://mcp.fiberfinder.ai/mcp'
What is the io.github.fiberfinder/telecom-truth MCP server?
io.github.fiberfinder/telecom-truth is an MCP server listed in the public MCP registry as io.github.fiberfinder/telecom-truth. US telecom availability and intelligence by address, with FCC provenance. Fiber-first. This page covers its hosted endpoint (https://mcp.fiberfinder.ai/mcp).
Is the io.github.fiberfinder/telecom-truth MCP server safe to use?
io.github.fiberfinder/telecom-truth scores 83 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.fiberfinder/telecom-truth MCP server expose?
io.github.fiberfinder/telecom-truth exposes 5 tools: check_availability, provider_profile, area_intelligence, location_intelligence, industry_overview. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.
Does the io.github.fiberfinder/telecom-truth MCP server require authentication?
No. We connected to io.github.fiberfinder/telecom-truth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.fiberfinder/telecom-truth MCP server still maintained?
io.github.fiberfinder/telecom-truth is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.