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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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. Returns: service_name, service_version (PyPI), and spec_version (QRZ API). |
| 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_dxccA | 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
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.