# fcc-spectrum-mcp-server (remote · fcc-spectrum.caseyjhand.com)

Search FCC radio licenses, find nearby licensed sites, and see who is licensed on a frequency.

- Trust score: 88/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `fcc-spectrum.caseyjhand.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/fcc-spectrum.md), [page](https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/fcc-spectrum)
- npm · `@cyanheads/fcc-spectrum-mcp-server`: 39/100, [markdown](https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/cyanheads-fcc-spectrum-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/cyanheads-fcc-spectrum-mcp-server)

## Channel facts

- Endpoint: `https://fcc-spectrum.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3018 tokens (~503/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the fcc-spectrum-mcp-server server?

fcc-spectrum-mcp-server is a hosted endpoint at https://fcc-spectrum.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.

### Claude

```bash
claude mcp add --transport http cyanheads-fcc-spectrum-mcp-server 'https://fcc-spectrum.caseyjhand.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cyanheads-fcc-spectrum-mcp-server": {
      "url": "https://fcc-spectrum.caseyjhand.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyanheads-fcc-spectrum-mcp-server": {
      "type": "http",
      "url": "https://fcc-spectrum.caseyjhand.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cyanheads-fcc-spectrum-mcp-server]
url = "https://fcc-spectrum.caseyjhand.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add cyanheads-fcc-spectrum-mcp-server --url 'https://fcc-spectrum.caseyjhand.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-fcc-spectrum-mcp-server:
    url: "https://fcc-spectrum.caseyjhand.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cyanheads-fcc-spectrum-mcp-server": {
      "Transport": "http",
      "Url": "https://fcc-spectrum.caseyjhand.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyanheads-fcc-spectrum-mcp-server -t streamable-http -u 'https://fcc-spectrum.caseyjhand.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-fcc-spectrum-mcp-server": {
      "type": "http",
      "url": "https://fcc-spectrum.caseyjhand.com/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-11-01 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 88, +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.

### 2026-10-29 (score 87, +1)

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

### 2026-10-27 (score 86, +1)

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

### 2026-10-26 (score 85, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 602 → 503
- [functional] First check of Schema quality: 100
- [functional] Schema quality: excellent → good
- [functional] New resource “fcc-spectrum-guide”
- [functional] Server version: 0.2.1 → 0.3.0

### 2026-10-25 (score 82, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fcc_spectrum_get_license” rewrote its description, which is the text the model reads
- [functional] Server version: 0.2.0 → 0.2.1

### 2026-10-24 (score 82, +1)

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

### 2026-10-22 (score 81, +1)

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

## MCP tools (5)

### `fcc_spectrum_search_licenses` (~566 tokens)

Search FCC ULS licenses

Search FCC ULS licenses and spectrum leases by callsign, licensee name, FCC Registration Number (FRN), market code, radio service, status, and licensee state, returning one row per record with its unique system identifier (USI) for fcc_spectrum_get_license. At least one of callsign, licensee, frn, market_code, radio_service, or state is required; status only narrows. Defaults to active records; pass status "any" to include expired, cancelled, and terminated ones. Licensee name matching is word-based (every word must appear as a word prefix), not fuzzy.

Input parameters:

- `callsign` (string): Exact callsign or lease ID, e.g. "KNKA123" or "L000012345". Case, spaces, and one trailing portable suffix ("/4") are normalized. ULS reuses callsigns, so several records can match.
- `cursor` (string): nextCursor from the previous page of the same search; omit for the first page.
- `frn` (string): FCC Registration Number, up to 10 digits; spaces and hyphens are removed and it is left-padded with zeros.
- `licensee` (string): Licensee name words, with at least one letter or digit; every word must match the start of a word in the name, in any order (e.g. "verizon wireless"). A word joined by - or & ("T-Mobile", "AT&T") mat…
- `limit` (integer): Positive integer records per page; values above 100 are clamped to 100 with a notice.
- `market_code` (string): Market code of a geographic-area license, matched exactly, e.g. "PEA016", "CMA020", "D06037", or "NW" (nationwide); results carry it as marketCode. Case, spaces, and hyphens are ignored, and the digi…
- `radio_service` (string): Two-character radio service code, e.g. "CD" (paging) or "BR" (BRS); see fcc_spectrum_list_reference topic "radio_services".
- `state` (string): Licensee mailing state: a two-letter USPS code (incl. DC, PR, VI, GU, AS, MP) or a full state name. This is the licensee's address, not the site location.
- `status` (string): License status: A active, L pending legal, X term pending, E expired, C canceled, T terminated, P parent station canceled, or "any" for every status. Defaults to A.

Output parameters:

- `appliedFilters` (object): Filters as the server applied them, normalized values and defaults included.
- `cap` (number): The page limit applied.
- `dataAsOf` (string): Creation time of the newest applied ULS file (ISO 8601).
- `error` (object): Present when the call failed. Absent on success.
- `licenses` (array): Matching records, ranked by name-match relevance when licensee is given and in callsign order otherwise.
- `nextCursor` (string): Pass as cursor with the same filters for the next page; absent on the last page.
- `notice` (string): Why nothing matched, what redaction excluded, or how to page further.
- `shown` (number): Records on this page.
- `totalCount` (number): Records matching the filters, across every page.
- `truncated` (boolean): True when more records follow this page.

### `fcc_spectrum_get_license` (~551 tokens)

Get an FCC ULS license

Fetch one FCC ULS license or spectrum lease in full by callsign or unique system identifier (USI): licensee (the lessee on a lease), status and key dates, its locations with coordinates, elevation, structure height, and ASR number, each location's antennas, each antenna's authorized frequencies with power, ERP/EIRP, station class, transmitter, and emission designators, and the microwave paths it transmits on (receive location and antenna, receive coordinates, receiving callsign); geographic-area licenses list their market and spectrum blocks, and lease links are shown in both directions. Large records are paged: one call lists whole locations up to 50 sites, 100 antennas, and 100 paths, up to max_frequencies frequency rows, and 100 leases, and names the location_offset or lease_offset that reads the rest; location_number starts the locations at a location number the search tools return. Technical detail is kept for active, pending-legal, and term-pending records only. A callsign shared by several records returns the active one, else the most recent.

Input parameters:

- `callsign` (string): Callsign or lease ID, e.g. "KNKA123" or "L000012345". Case, spaces, and one trailing portable suffix ("/4") are normalized. Pass this or usi, not both.
- `lease_offset` (integer): Lease to start at, counted from 0 in lease-ID order; pass nextLeaseOffset from the previous call to read the next 100.
- `location_number` (integer): Location number to start at: the locationNumber of a fcc_spectrum_find_transmitters or fcc_spectrum_search_frequencies result. A number the record does not file starts at the next one it does. Pass t…
- `location_offset` (integer): Location to start at, counted from 0 in location-number order; pass nextLocationOffset from the previous call to read the next locations. To start at a location number instead, pass location_number.
- `max_frequencies` (integer): Positive integer frequency-row budget across the locations this call lists; values above 1000 are clamped to 1000 with a notice. Rows beyond it are dropped from the last locations first. Large microw…
- `usi` (string): Unique system identifier, as digits: the usi field of fcc_spectrum_search_licenses, fcc_spectrum_find_transmitters, or fcc_spectrum_search_frequencies results. Pass this or callsign, not both.

Output parameters:

- `candidates` (array): Up to 5 records whose callsign starts with the one requested; present when a callsign lookup found nothing.
- `cap` (number): The max_frequencies cap applied.
- `dataAsOf` (string): Creation time of the newest applied ULS file (ISO 8601).
- `error` (object): Present when the call failed. Absent on success.
- `found` (boolean): True when a record matched; false returns guidance and candidates instead.
- `guidance` (string): Why nothing matched and where to look next; present when found is false.
- `license` (object): The record; present when found is true.
- `locationTotal` (number): Location numbers the record files; present when found is true.
- `locations` (array): Locations with antennas, frequency rows, and paths, one entry per location number (a number filed at several sites lists them in sites): whole locations from location_offset or location_number up to…
- `nextLeaseOffset` (number): Pass as lease_offset to read the leases after these; absent when none follow.
- `nextLocationOffset` (number): Pass as location_offset to read the locations after these; absent when none follow.
- `notice` (string): What this call left out and the call that reads it, where an unfiled location_number started the locations, or why an offset or location number listed nothing.
- `otherCallsignRecords` (array): Other records under the same callsign (ULS reuses callsigns); present when found is true.
- `pathTotal` (number): Microwave paths the record files across all its locations; 0 when technicalRetained is false, since paths are kept only for status A, L, or X. Present when found is true, except on an index built bef…
- `shown` (number): Frequency rows returned.
- `siteTotal` (number): Sites the record files, each site of a shared location number counted; present when found is true.
- `technicalRetained` (boolean): False when the status is not A, L, or X (active, pending legal, term pending): sites and frequencies are kept only for those, so locations is empty.
- `truncated` (boolean): True when this call leaves part of the record out: locations after the ones listed, frequency rows beyond max_frequencies, or leases after the ones listed.

### `fcc_spectrum_find_transmitters` (~617 tokens)

Find FCC-licensed sites near a point

Find FCC-licensed sites within a radius of a coordinate, nearest first, each with its callsign, licensee, distance, coordinates, filed location type and class, ground elevation, structure height, and authorized frequencies. Filter by frequency or band, radio service, location type, location class, and live status (active by default). Unset location_class keeps all filed roles, including receive and passive locations; filed classes describe authorization, not actual on-air activity. Coordinates are decimal degrees or DMS strings. Mobile and temporary-fixed operating areas are returned at their center with radiusKm and match when the center lies within radius_km. Locations without valid coordinates are omitted; market-area licenses without site records are found with fcc_spectrum_search_frequencies.

Input parameters:

- `cursor` (string): nextCursor from the previous page of the same search; omit for the first page.
- `frequency_high` (number): Band upper edge in unit; requires frequency_low.
- `frequency_low` (number): Only sites authorized on this frequency, in unit; with frequency_high, the band's lower edge. Matches any assignment whose occupied band overlaps.
- `latitude` (number, required): Search center latitude: decimal degrees (47.6205, "47.6205") or a DMS string with hemisphere ("47-37-13.8 N", "47°37'13.8"N").
- `limit` (integer): Positive integer sites per page; values above 100 are clamped to 100 with a notice.
- `location_class` (string): One filed FCC location class, case-insensitive: C Centerpoint, L IQ/QQ Area of Operation Desc, P Passive Repeater Location, R Receive Location, T Transmit Location. Omit for every class; filed classe…
- `location_type` (string): One ULS location type code, case-insensitive: "F" keeps fixed sites only, "M" mobile and "T" temporary-fixed operating areas; see fcc_spectrum_list_reference topic "location_types". Omit for every ty…
- `longitude` (number, required): Search center longitude: decimal degrees (-122.3493) or a DMS string with hemisphere ("122-20-57.5 W").
- `max_frequencies_per_site` (integer): Positive integer frequency budget per site; values above 50 are clamped to 50 with a notice. frequencyCount carries the full count.
- `radio_service` (string): Two-character radio service code, e.g. "IG" (industrial/business pool); see fcc_spectrum_list_reference topic "radio_services".
- `radius_km` (number): Search radius in km (0.1–100).
- `status` (string): A active (default), L pending legal, X term pending, or "any" for all three. Other statuses keep no site records.
- `unit` (string): Unit of the frequencies: kHz, MHz (default), or GHz.

Output parameters:

- `appliedFilters` (object): Filters as the server applied them, normalized values and defaults included.
- `cap` (number): The page limit applied.
- `dataAsOf` (string): Creation time of the newest applied ULS file (ISO 8601).
- `error` (object): Present when the call failed. Absent on success.
- `nextCursor` (string): Pass as cursor with the same inputs for the next page; absent on the last page.
- `notice` (string): Why nothing matched and how to widen the search, or how to page further.
- `searchCenter` (object): The search circle as the server applied it (DMS input converted).
- `shown` (number): Sites on this page.
- `sites` (array): FCC-licensed sites, nearest first; filed classes can include transmit, receive, and passive roles.
- `totalCount` (number): Sites within the radius matching the filters, across every page.
- `truncated` (boolean): True when more sites follow this page.

### `fcc_spectrum_search_frequencies` (~662 tokens)

Search FCC ULS authorizations by frequency

Find FCC ULS authorizations whose occupied band overlaps a frequency or band. Site assignments (land mobile, microwave, paging, cellular sites) return one row per site and frequency with the site's state and coordinates; market-area licenses and leases (PCS, AWS, 700 MHz, 3.45 and 3.7 GHz, and other auctioned blocks) return one row per spectrum block with its market code and name; 3.5 GHz Priority Access Licenses file no frequency, so list them with fcc_spectrum_search_licenses and radio_service PL. Filter by state, radio service, licensee, FRN, market code, and live status (active by default). For transmitter sites near a coordinate, use fcc_spectrum_find_transmitters.

Input parameters:

- `cursor` (string): nextCursor from the previous page of the same search; omit for the first page.
- `frequency_high` (number): Band upper edge in unit; omit to search a single frequency.
- `frequency_low` (number, required): Frequency in unit; with frequency_high, the band's lower edge. Matches any authorization whose occupied band overlaps.
- `frn` (string): Licensee's FCC Registration Number, up to 10 digits; spaces and hyphens are removed and it is left-padded with zeros. Individual licensees match and are returned redacted.
- `kind` (string): site: transmitter-site assignments only; market: market-area spectrum blocks only; both (default).
- `licensee` (string): Licensee name words, with at least one letter or digit; every word must match the start of a word in the name, in any order. A word joined by - or & ("T-Mobile", "AT&T") matches its pieces side by si…
- `limit` (integer): Positive integer rows per page; values above 200 are clamped to 200 with a notice.
- `market_code` (string): Market code of the license, matched exactly, e.g. "PEA016", "CMA020", or "NW" (nationwide); market rows carry it as marketCode. Applies to site and market rows alike, since cellular (CMA) licenses fi…
- `radio_service` (string): Two-character radio service code, e.g. "WU" (700 MHz upper band); see fcc_spectrum_list_reference topic "radio_services".
- `state` (string): Two-letter USPS code or full state name. Sites match on their filed state, or the state derived from their coordinates. Market blocks match when their FCC market area reaches the state (a multi-state…
- `status` (string): A active (default), L pending legal, X term pending, or "any" for all three. Other statuses keep no frequency records.
- `unit` (string): Unit of the frequencies: kHz, MHz (default), or GHz.

Output parameters:

- `appliedFilters` (object): Filters as the server applied them, normalized values and defaults included.
- `assignments` (array): Matching site assignments and market blocks, frequency ascending.
- `cap` (number): The page limit applied.
- `dataAsOf` (string): Creation time of the newest applied ULS file (ISO 8601).
- `error` (object): Present when the call failed. Absent on success.
- `nextCursor` (string): Pass as cursor with the same inputs for the next page; absent on the last page. A page over a dense band can hold fewer rows than limit and still carry one.
- `notice` (string): Why nothing matched, what the state and redaction rules skipped, or how to page further.
- `shown` (number): Rows on this page.
- `totalCount` (number): Rows matching the filters, across every page; at least this many when totalIsLowerBound is true.
- `totalIsLowerBound` (boolean): True when a dense band was counted only in part, so totalCount is a lower bound; absent when the count is exact.
- `truncated` (boolean): True when more rows follow this page.

### `fcc_spectrum_list_reference` (~214 tokens)

List FCC ULS reference codes and coverage

Decode FCC ULS codes used by the other tools — radio service codes, station classes, license statuses, location types, antenna types, applicant types, amateur operator classes — or report coverage: which service groups this index holds, record counts, and when each was last updated. Works before the index is built. Station classes describe licensed categories, not actual on-air activity.

Input parameters:

- `filter` (string): radio_services and station_classes only: keep entries whose code and label contain every token given, in any order (e.g. "700 public safety" or "FB2"). Case- and accent-insensitive; punctuation separ…
- `topic` (string, required): What to list: a code vocabulary (radio_services, station_classes, license_statuses, location_types, antenna_types, applicant_types, operator_classes) or coverage, the index build state and loaded ser…

Output parameters:

- `dataAsOf` (string): Creation time of the newest applied ULS file (ISO 8601); absent before the index is built.
- `entries` (array): Decoded codes, in code order; present for every topic except coverage.
- `error` (object): Present when the call failed. Absent on success.
- `groups` (array): Every weekly service group this server can index, with whether it is loaded; present for coverage.
- `index` (object): Index build state; present for coverage.
- `notice` (string): Guidance when a filter matched nothing, was not applied, the index is not built yet, or its antenna or path coverage needs a full rebuild.
- `redactIndividuals` (boolean): True when individual licensees are redacted and excluded from name search; present for coverage.
- `topic` (string): The topic answered.

## Diagnostics

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

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 88
- 2026-10-30: 87
- 2026-10-29: 87
- 2026-10-28: 86
- 2026-10-27: 86
- 2026-10-26: 85
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-09: 76
- 2026-10-04: 73
- 2026-10-03: 73
- 2026-10-02: 72

## Common questions

### What is the fcc-spectrum-mcp-server server?

fcc-spectrum-mcp-server is listed in the public MCP registry as io.github.cyanheads/fcc-spectrum-mcp-server. Search FCC radio licenses, find nearby licensed sites, and see who is licensed on a frequency. This page covers its hosted endpoint (https://fcc-spectrum.caseyjhand.com/mcp).

### Is the fcc-spectrum-mcp-server server safe to use?

fcc-spectrum-mcp-server scores 88 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 fcc-spectrum-mcp-server server expose?

fcc-spectrum-mcp-server exposes 5 tools: fcc_spectrum_search_licenses, fcc_spectrum_get_license, fcc_spectrum_find_transmitters, fcc_spectrum_search_frequencies, fcc_spectrum_list_reference. Their descriptions and schemas cost roughly 2,610 tokens of context every time the server is loaded.

### Does the fcc-spectrum-mcp-server server require authentication?

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

### Is the fcc-spectrum-mcp-server server still maintained?

fcc-spectrum-mcp-server 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.

## Links

- Remote endpoint: https://fcc-spectrum.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/fcc-spectrum-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/fcc-spectrum.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/fcc-spectrum.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-fcc-spectrum-mcp-server/fcc-spectrum