uk-radio-mcp
Related Servers
Alternatives to uk-radio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables radio hobbyists to explore likely services, channels, and signal types across the radio spectrum from 108 MHz to 1 GHz via classification, channel queries, service search, read-only SQL, and local reference-model queries.GPL 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 AI assistants to query OMISS amateur-radio data from omiss.net's public pages, including the net schedule, nets currently on the air, member lookup, past net check-ins, the Statehood schedule, officers, awards and net statistics. No login or API key is required, with polite rate limiting and caching built in.14147 PyPIGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to sync, search, and retrieve amateur radio repeater data from RepeaterBook.com through three typed tools.78 PyPI5MIT
- AlicenseAqualityBmaintenanceEnables radio line-of-sight checks over locally cached FABDEM terrain for points and routes, including Earth curvature, k-factor refraction, Fresnel-zone clearance, coverage gaps, and verdicts at named stops. It also supports terrain elevation/profile queries and tile prefetching for offline use.6AGPL 3.0
- AlicenseAqualityAmaintenanceEnables querying WSPR beacon data including live spots, band activity, top beacons, propagation paths, and SNR trends through any MCP-compatible AI assistant.9158 PyPIGPL 3.0
TDQS
Scored across 9 tools
Two pairs overlap: search_licences (which itself accepts a licensee substring) versus search_licensee, and lookup_dmr_id versus radioid_api (both pull RadioID.net data, one from the daily dump and one live). The descriptions do explain the distinctions, but an agent could easily pick the wrong one for 'find licences held by X'.
All names are snake_case and readable, but the convention is mixed: verb_noun (refresh_register, search_licences, export_whistler) alongside noun_verb or bare-noun names (repeaterbook_search, radioreference_call, radioid_api). The upstream-source tools read as a different family from the register tools.
Nine tools is well within a sensible range and each maps to a concrete capability: cache management, source discovery, two register queries, DMR lookup/API, two third-party source connectors, and a CSV export.
Core lifecycle is covered: discover sources, refresh the register, search by frequency/location/licensee, and export to a scanner. Gaps are minor but real — export supports only the Whistler EZ Scan format, and there is no per-licence detail/ID lookup beyond search results.