qrz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QRZ_MCP_MOCK | No | Set to '1' to run in mock mode without real QRZ credentials. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
MCP server for QRZ.com — callsign lookup, DXCC resolution, logbook queries
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get qrz-mcp service version and upstream QRZ API version. Returns the running PyPI version of qrz-mcp and the QRZ.com XML + Logbook API contract in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol. |
| qrz_lookupA | Look up a callsign on QRZ.com (name, grid, DXCC, license class, QSL info, image). Requires a QRZ XML Subscription ($35.95/yr) for full fields. |
| qrz_dxccB | Resolve a DXCC entity from a callsign or numeric entity code. |
| qrz_logbook_statusA | Get QRZ logbook statistics (QSO count, DXCC total, date range). |
| qrz_downloadA | Download your complete QRZ logbook as raw ADIF text. Returns the .adi file content — save to disk for import into your logger. Transparently paginates to collect all records. Rate-limited to avoid API bans. |
| qrz_logbook_fetchA | Query QSOs from a QRZ logbook with optional filters. Transparently paginates to collect up to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools mostly target distinct actions: version metadata, callsign lookup, DXCC resolution, logbook status, bulk logbook download, and filtered QSO fetch. The main overlap is between qrz_download and qrz_logbook_fetch, since both retrieve logbook data, though one is a full ADIF export and the other is a filtered query.
Most domain tools use a qrz_ prefix, but get_version_info breaks the pattern with get_. The suffixes also mix verbs and nouns (lookup, dxcc, status, download, fetch), making the convention readable but not fully consistent.
Six tools are well-scoped for a QRZ callsign and logbook service. Each tool covers a distinct capability without obvious redundancy or excessive surface area.
The surface covers version info, callsign lookup, DXCC resolution, logbook stats, bulk download, and filtered QSO retrieval. It is read-only and lacks logbook write operations such as adding or updating QSOs, but core read workflows are well covered.