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.668 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.6137 PyPI3GPL 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.61 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.6247 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.8115 PyPIGPL 3.0
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: version info, distance/heading calculations, parsing, validation, spec reading, and enumeration listing/searching. The only mild overlap is between list_enumerations and search_enumerations, and read_specification_resource could partially duplicate enumeration data, but the descriptions clarify the boundaries.
All tool names use snake_case and follow a verb_noun pattern (get_version_info, calculate_distance, parse_adif, list_enumerations, validate_adif_record). The convention is consistent across the entire set.
Eight tools is well-scoped for an ADIF support server covering reference lookup, validation, parsing, and Maidenhead calculations. No tool feels redundant, and the set does not appear artificially inflated or thin.
The surface covers reading, parsing, validating, spec/enumeration lookup, and calculations, but lacks any tool to create, write, or export ADIF records. This is a notable gap if the server is meant to support full ADIF lifecycle workflows.