itu-zones-mcp
Summarizes: a read-only, no-auth MCP server serving IARU's 90 amateur ITU zones with citations.
Zone lookup (
itu_zones_lookup): give a zone number (1–90) and get every prefix, subdivision, boundary wording, ADIF code and IARU citation; zones 76–77 and 79–89 have no entry in this edition.Reverse lookup by entity (
itu_zones_codes_for): find the ITU zones covering an ADIF DXCC entity or one of its subdivisions (e.g.dxcc: 291, subdivision: "AZ"), including the IARU's boundary wording where an entity is split by a line (e.g. W7 states at 110W).Free-text search (
itu_zones_search): find zones whose name, prefixes, area wording or attributes match all words in a query such as "Antarctica", "UA0" or "110W"; limit 1–200 (default 50).Date validity (
itu_zones_valid_on): check whether a zone was valid on a given date — always yes here since the chapter defines no validity window; provided for parity with other owner-list servers.Source provenance (
itu_zones_source_info): owner, edition, terms, plus the owner's file URL and SHA-256 for independent verification.Version identity (
get_version_info): server version and the IARU edition served (fleet identity attestation).All tools are read-only, idempotent, closed-world (no network, no authentication) and every answer names its source.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@itu-zones-mcp which ITU zone is Arizona in?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
itu-zones-mcp
Source: the IARU's HF Managers Handbook, chapter 9.8, "Definition of ITU-Zones when used by radio amateurs" (IARU Region 1, v8.2; the chapter's pages are dated November 2000). The zone border-lines for amateur use are kept there under IARU Region 1 recommendation REC/99/LH/C4.2; the list was drafted by G3HTA from the ITU's CIRAF zones and approved by all three IARU regions. The 90 ITU zones are the IARU's: this package serves facts from that chapter, each citing its page and zone, and links to the handbook rather than copying it. Our GPL-3.0-or-later license covers our code, not the IARU's data.
Checked against: AD1C's country files (Jim Reisert, AD1C), ADIF 3.1.8's subdivision zones, and ARRL's DXCC list. The tests fetch AD1C's and ARRL's files from their sites to validate the facts; neither is included here. where they differ, the owner's list wins (see docs/TRANSCRIPTION.md).
MCP server for ITU zones as the IARU publishes them for amateur use: the 90 zones of chapter 9.8, "Definition of ITU-Zones when used by radio amateurs," of the IARU Region 1 HF Managers Handbook (v8.2), used by the IARU HF Championship and ITU-zone awards. Each zone's prefixes are given in ADIF's own DXCC and subdivision codes, with the IARU's own wording where it splits an area by a line.
Part of the qso-graph project. No network, no authentication: the facts from the owner's list ship with the package, and every answer names its source.
Install
uvx itu-zones-mcp # run it; nothing to installRelated MCP server: adif-mcp
Tools
Tool | Description | Key Parameters |
| One zone: every prefix, subdivision and boundary the IARU lists, with the citation | code |
| Which zones cover an ADIF DXCC entity, or one of its subdivisions | dxcc, subdivision |
| Find zones by prefix or wording | text, limit |
| Whether a zone was valid on a date (ITU zones have no validity window) | code, on_date |
| Owner, edition, terms, and the owner's file's URL and SHA-256 | — |
| Service version + the owner's edition served (fleet identity attestation) | — |
Quick Start
No credentials needed—just install and configure your MCP client.
Configure your MCP client
itu-zones-mcp works with any MCP-compatible client. Add the server config and restart—tools appear automatically.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}ChatGPT Desktop
{
"mcpServers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"itu-zones": {
"command": "uvx",
"args": ["itu-zones-mcp"]
}
}
}Ask questions
"Which ITU zone is Arizona in?"
"What does ITU zone 75 cover?"
"Which ITU zones does Antarctica span?"
MCP Inspector
itu-zones-mcp --transport streamable-http --port 8017Then open the MCP Inspector at http://localhost:8017.
Development
git clone https://github.com/qso-graph/itu-zones-mcp.git
cd itu-zones-mcp
uv sync --group dev
uv run pytestscripts/fetch_published.py fetches the owner's documents into published/ (not committed) and checks their SHA-256 hashes; uv run pytest --live runs the tests that need them. scripts/build.py regenerates derived/ and load.sql, a PostgreSQL load for QSO Graph's reference data (load QG ADIF's adif schema first).
License
itu-zones-mcp's own code is GPL-3.0-or-later. See LICENSE. The data it serves is the owner's, credited at the top of this page: our license doesn't cover it, and we claim no rights in it. The owner's document itself is not included; data/SOURCE.json records its URL and SHA-256 so anyone can check the facts against it. Files we built from the facts (data/derived/) are ours and labelled as ours. How the owner's text was read is recorded in docs/TRANSCRIPTION.md. See NOTICE.
Available Tools
6 toolsget_version_infoGet Version InfoARead-onlyIdempotent
Get itu-zones-mcp's version and the edition of the IARU's list it serves.
Inputs: no named parameters. Returns: object
itu_zones_codes_forItu Zones Codes ForARead-onlyIdempotent
Which ITU zones cover an ADIF DXCC entity, or one of its subdivisions. Where the IARU splits an entity by a line (W7 states at 110W), each zone is returned with the IARU's boundary wording.
Inputs: dxcc (required), subdivision. Returns: object
itu_zones_lookupItu Zones LookupARead-onlyIdempotent
One ITU zone: every prefix, subdivision and boundary the IARU lists for it, with ADIF codes and the citation. Zones 76-77 and 79-89 have no entry in this edition.
Inputs: code (required). Returns: object
itu_zones_searchItu Zones SearchARead-onlyIdempotent
Find codes whose name, prefixes, area wording or attributes contain every word of text.
Inputs: text (required), limit. Returns: object
itu_zones_source_infoItu Zones Source InfoARead-onlyIdempotent
Who owns this list, which edition is served, its terms, and the owner's files' URLs and SHA-256s.
Inputs: no named parameters. Returns: object
itu_zones_valid_onItu Zones Valid OnARead-onlyIdempotent
Whether an ITU zone was valid on a date. The chapter gives no validity window, so every zone it lists is valid; the tool exists so every owner-list server answers the same questions.
Inputs: code (required), on_date (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: zone lookup, text search, entity-to-zone mapping, date validity, and source metadata. The only mild overlap is get_version_info versus itu_zones_source_info, both of which mention the served edition.
Four tools use the itu_zones_ prefix, but get_version_info breaks that pattern and the suffixes mix verbs and noun phrases (lookup, search, codes_for, valid_on, source_info). The set is readable but not consistently verb_noun.
Six tools is well-scoped for a read-only reference server, with each tool covering a distinct query mode. No tool feels redundant or extraneous.
The surface covers zone lookup, search, DXCC entity mapping, date validity, source provenance, and versioning. Minor gaps remain, such as listing all zones or reverse prefix lookup, but search largely mitigates them.
Maintenance
Related MCP Connectors
Human-reviewed zoning answers with ordinance citations for covered US municipalities.
Offline, keyless lookup of the US civil aircraft registry — decode N-numbers, search records.
Free, keyless postal/ZIP code lookup: place name(s), state/region, and coordinates.
Postal lookups for 120 countries with cited sources; deep US tier: demographics, climate, area codes
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.6228 PyPI4GPL 3.0
- AlicenseAqualityAmaintenanceProvides safe, typed access to Amateur Radio logging data with ADIF validation, parsing, spec search, and geospatial utilities for Maidenhead locators.8763 PyPI5GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables querying a local SQLite index of FCC ULS licensing data to look up licenses by callsign, licensee, or FRN, find licensed transmitter sites near a coordinate, and see who is authorized on a frequency or band. Runs over STDIO or Streamable HTTP with no API key required at request time.101 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables querying WAZ zone definitions, mapping ADIF DXCC entities and subdivisions to zone codes, searching zones by name or prefix, and checking zone validity with source citations. Runs locally without network access or authentication.6106 PyPIGPL 3.0