itu-zones-mcp
Related Servers
Alternatives to itu-zones-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.6GPL 3.0
- AlicenseBqualityCmaintenanceEnables clients to look up DARC local-club DOK codes and special event DOKs — district, club, purpose, callsign and sponsoring club — and to check whether a code was valid on a given QSO date, or to search by club, town, district or purpose. Runs fully offline with no network or authentication, and every answer cites its published source.6GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables 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.1Apache 2.0
- AlicenseAqualityAmaintenanceProvides safe, typed access to Amateur Radio logging data with ADIF validation, parsing, spec search, and geospatial utilities for Maidenhead locators.81,634 PyPI4GPL 3.0
- AlicenseAqualityBmaintenanceMCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.61,758 PyPI3GPL 3.0
- AlicenseAqualityCmaintenanceEnables users to resolve historical US land and jurisdiction questions: which county held a given spot on a specific date, where a federal land description (PLSS) falls on the ground, and which National Archives series and file hold the case behind a land patent. All lookups are read-only and can be used alongside archive-search tools to route records requests to the right office.9MIT
TDQS
Scored across 6 tools
The query tools (lookup, search, codes_for, valid_on) each target a distinct question and are clearly separable. The only mild overlap is between get_version_info (service/edition versioning) and itu_zones_source_info (data ownership/edition terms), which both surface metadata and could be confused at a glance.
Five of six tools use a consistent snake_case itu_zones_ prefix (lookup, search, codes_for, valid_on, source_info), giving a predictable pattern. get_version_info breaks the prefix convention, a minor deviation from an otherwise uniform scheme.
Six tools is well-scoped for a focused reference-lookup server. Each tool covers a distinct query type with no filler or redundancy.
The surface covers lookup by zone, reverse lookup by DXCC entity/subdivision, text search, validity checks, and provenance/version metadata, matching the apparent domain well. A tool to enumerate or list all zones is absent, but agents can largely work around this via search.