qrz-mcp
Related Servers
Alternatives to qrz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.8343 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for ARRL Logbook of The World (LoTW) that enables querying confirmations, uploaded QSOs, DXCC credits, and user activity through any MCP-compatible AI assistant. Part of the qso-graph project, it is read-only and requires LoTW credentials for authenticated tools.6221 PyPI1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets an LLM operate an amateur radio shack: query live APRS traffic, predict satellite passes, schedule SDR captures, and monitor FT8/WSPR band activity.MIT
- AlicenseAqualityAmaintenanceAn MCP server for eQSL.cc that allows users to download incoming electronic QSL cards, verify specific contacts, and check Authenticity Guaranteed status. It enables natural language interaction with amateur radio logs and confirmation records through any MCP-compatible AI assistant.5315 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for Summits on the Air (SOTA) — live spots, activation alerts, summit info, and nearby summits through any MCP-compatible AI assistant.5225 PyPI1GPL 3.0
- AlicenseAqualityAmaintenanceMCP server for Parks on the Air (POTA) providing live activator spots, park details, activator/hunter stats, and scheduled activations through any MCP-compatible AI assistant.8305 PyPI2GPL 3.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: version info, logbook download, DXCC entity resolution, filtered QSO queries, logbook statistics, and callsign lookup. No overlapping functionality.
All tools start with 'qrz_' prefix and use descriptive names, but there is some inconsistency in verb usage (e.g., 'get_version_info' vs 'qrz_download' vs 'qrz_dxcc'). However, the pattern is generally clear and predictable.
Six tools cover the core operations for a QRZ integration (lookup, logbook management, version checking) without being excessive. The scope is well-defined.
The set covers essential operations: callsign lookup, DXCC resolution, logbook retrieval and download, and status. Missing write operations like adding QSOs, but that may be out of scope given QRZ's API constraints.