io.github.qso-graph/qrz-mcp
PYPI · QRZ-MCP
QRZ.com MCP server. Callsign lookup, DXCC resolution, logbook queries via QRZ XML API.
Available components
Last scanned (19 hours ago)
Scores higher than 80% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to qso-graph/qrz-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 662 tokens (~110/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 0
- Package version: 0.4.1 → 0.6.2 functional
- 29 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.6.0 → 0.6.2 functional
- Package version: 0.6.0 → 0.6.1 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 0.5.0 → 0.6.0 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.1 → 0.5.0 functional
- Package version: 0.4.1 → 0.4.4 functional
- Package version: 0.4.1 → 0.4.3 functional
- Package version: 0.4.1 → 0.4.2 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/qrz-mcp@0.6.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | qso-graph/qrz-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/qrz-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3570632309 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:cb9202df08133965d93e008f6b7a824c9c7d44f38bb3ca801682f31c5c72c572 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_version_info Get Version Info ~82
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
qrz_download Qrz Download ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., '20m'). |
| end_date | – | – | Date range end (YYYY-MM-DD). |
| mode | – | – | Filter by mode (e.g., 'FT8'). |
| persona | string | yes | Persona name configured in adif-mcp. |
| start_date | – | – | Date range start (YYYY-MM-DD). |
Structured output declared, but exposes no named fields.
No examples provided.
qrz_dxcc Qrz Dxcc ~66
Resolve a DXCC entity from a callsign or numeric entity code.
| Name | Type | Req | Description |
|---|---|---|---|
| persona | string | yes | Persona name configured in adif-mcp. |
| query | string | yes | Callsign (e.g., VP8PJ) or DXCC code (e.g., 291). |
Structured output declared, but exposes no named fields.
No examples provided.
qrz_logbook_fetch Qrz Logbook Fetch ~233
Query QSOs from a QRZ logbook with optional filters. Transparently paginates to collect up to `limit` records. QRZ returns records oldest first, so by default `limit` keeps the OLDEST matches. Set `newest_first` for the most recent QSOs instead (for example, "my last 10 contacts" is limit=10 with newest_first=true).
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., '20m'). |
| callsign | – | – | Filter by contacted station. |
| confirmed_only | boolean | – | Only return confirmed QSOs. |
| dxcc | – | – | Filter by DXCC entity code. |
| end_date | – | – | Date range end (YYYY-MM-DD). |
| limit | integer | – | Maximum records to return (default 250). |
| mode | – | – | Filter by mode (e.g., 'FT8'). |
| newest_first | boolean | – | Return the newest `limit` matches, newest first. |
| persona | string | yes | Persona name configured in adif-mcp. |
| start_date | – | – | Date range start (YYYY-MM-DD). |
Structured output declared, but exposes no named fields.
No examples provided.
qrz_logbook_status Qrz Logbook Status ~44
Get QRZ logbook statistics (QSO count, DXCC total, date range).
| Name | Type | Req | Description |
|---|---|---|---|
| persona | string | yes | Persona name configured in adif-mcp. |
Structured output declared, but exposes no named fields.
No examples provided.
qrz_lookup Qrz Lookup ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | string | yes | Callsign to look up (e.g., W1AW). |
| persona | string | yes | Persona name configured in adif-mcp. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/qrz-mcp server?
io.github.qso-graph/qrz-mcp runs locally as a PyPI package, launched with uvx qrz-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · qrz-mcp
claude mcp add qso-graph-qrz-mcp -- uvx qrz-mcp
What is the io.github.qso-graph/qrz-mcp server?
io.github.qso-graph/qrz-mcp is listed in the public MCP registry as io.github.qso-graph/qrz-mcp. QRZ.com MCP server. Callsign lookup, DXCC resolution, logbook queries via QRZ XML API. This page covers its PyPI package (qrz-mcp).
Is the io.github.qso-graph/qrz-mcp server safe to use?
io.github.qso-graph/qrz-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.qso-graph/qrz-mcp server expose?
io.github.qso-graph/qrz-mcp exposes 6 tools: get_version_info, qrz_lookup, qrz_dxcc, qrz_logbook_status, qrz_download, qrz_logbook_fetch. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Is the io.github.qso-graph/qrz-mcp server still maintained?
io.github.qso-graph/qrz-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.qso-graph/qrz-mcp server under?
io.github.qso-graph/qrz-mcp declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.