adif-mcp
Related Servers
Alternatives to adif-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables read-only access to Turbo HAMLOG amateur radio logs, allowing natural-language search and aggregation of contacts, station history, award progress, and statistics by importing logs from ADIF/CSV or HAMLOG.HDB via the DLL.91MIT
- 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.6113 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.6269 PyPI4GPL 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.114 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables read-only querying of live and past amateur-radio nets and check-ins from NetLogger, with caching, rate limiting, and a consistent contract for future sources.6166 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.8126 PyPIGPL 3.0
TDQS
Scored across 8 tools
Most tools target distinct actions (parsing, validation, spec reading, geo math), and the list vs search enumeration pair is clarified by descriptions. The calculate_distance vs calculate_heading pair and read_specification_resource vs list_enumerations overlap slightly, but outputs are well differentiated.
All tools follow a consistent snake_case verb_noun pattern (get_version_info, calculate_distance, parse_adif, list_enumerations, search_enumerations, validate_adif_record). No mixed conventions.
Eight tools is well-scoped for an ADIF reference/validation server, with each tool covering a distinct capability (version, geo, parsing, spec, enumerations, validation). Nothing feels padded or missing for the stated purpose.
The read/validate/spec-reference surface is solid, covering parsing, validation, enumerations, and spec lookup. However, there is no write/export or record-modification tool, which is a noticeable but workable gap for an ADIF-focused server.