# Reported issues for qrz-mcp

Pod holds 5 of 5 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to [qrz-mcp](/mcp/qrz-mcp).

## Most discussed

### require() prefers password over api_key, so saving both sends the password as the API key

Another issue I ran into with setting up my API key for QRZ for connectivity to Claude Desktop.  Initial testing has been successful, YMMV depending on what you were envisioning.

## Summary

`PersonaManager.require()` returns `creds.password or creds.api_key`, so the password wins whenever both are stored. For providers that authenticate with an API key (notably `qrz_logbook`), saving both `--password` and `--api-key` makes the consuming server send the **password** as the key.

## How it…

[Read the thread](https://github.com/qso-graph/qrz-mcp/issues/10) · 2026-09-19 · closed · outside contributor · 2 comments

### Date filters fail, paging can't work, and there's no way to fetch the newest QSOs (AFTER/BEFORE, top-level AFTERLOGID)

Installed and started trying to use the mcp server with Claude desktop.  I ran into issues for connectivity to qrz.com.  I asked Claude to analyze and fix the issue, which it did.  Initial testing has been completed; but YMMV depending on what you were envisioning for the project.

## Summary

Three problems in `LogbookClient` (0.3.3) that are separate from #3 (ADIF parsing) and #5 (status field names). Findings come from a live 3,663-QSO logbook plus QRZ's [Logbook API…

[Read the thread](https://github.com/qso-graph/qrz-mcp/issues/9) · 2026-09-19 · closed · outside contributor · 2 comments

### Logbook fetch/download return 0 records: ADIF parser doesn't handle HTML-escaped QRZ responses

## Summary

`qrz_logbook_fetch` and `qrz_download` return **0 records** for logbooks that clearly contain QSOs. `qrz_logbook_status` correctly reports the count (e.g. 30 QSOs), but the fetch/download ADIF parser silently drops every record.

## Root cause

The QRZ Logbook API returns the ADIF payload **HTML-entity-escaped** — fields arrive as `&lt;call:6&gt;` / `&lt;eor&gt;`, not `<call:6>` / `<eor>`.

`_parse_adif_records()` in `src/qrz_mcp/logbook_client.py` matches on literal angle brackets:…

[Read the thread](https://github.com/qso-graph/qrz-mcp/issues/3) · 2026-08-28 · closed · outside contributor · 2 comments

### Wrong persona create command

https://github.com/qso-graph/qrz-mcp/blob/3e1d53a7a43649e2b74dc7cd8e53d9d1e73967fe/README.md?plain=1#L36

```bash
❯ qso-auth persona create Micael --callsign PU2UMK
usage: qso-auth persona [-h] {list,add,remove,remove-all,show,set-active,set-credential} ...
qso-auth persona: error: argument persona_cmd: invalid choice: 'create' (choose from list, add, remove, remove-all, show, set-active, set-credential)
```

[Read the thread](https://github.com/qso-graph/qrz-mcp/issues/2) · 2026-08-28 · closed · outside contributor · 2 comments

### qrz_logbook_status silently returns 0/empty for dxcc, start_date and end_date: STATUS field names don't match the API response

## Summary

`qrz_logbook_status` returns `dxcc: 0`, `start_date: ""` and `end_date: ""` for logbooks that clearly have those values. `count`, `confirmed` and `callsign` are correct, so the tool looks like it is working — the wrong fields fail silently rather than erroring.

Found while verifying the fix for #3 against a live logbook.

## Root cause

`LogbookClient.status()` reads key names that the QRZ `ACTION=STATUS` response does not use.

Verbatim live response (key redacted, `PU2UMK`, 30…

[Read the thread](https://github.com/qso-graph/qrz-mcp/issues/5) · 2026-08-28 · closed · outside contributor · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/qso-graph/qrz-mcp/issues).