hamqth-mcp
MCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.
Part of the qso-graph project. Authenticated tools use qso-graph-auth for persona and credential management.
Install
uvx hamqth-mcp # run it; nothing to install
Tools
| Tool | Auth | Description |
|---|---|---|
hamqth_lookup |
Yes | Callsign lookup (name, grid, DXCC, coordinates, QSL preferences) |
hamqth_dxcc |
No | Resolve DXCC entity from callsign or ADIF code |
hamqth_bio |
Yes | Fetch operator biography |
hamqth_activity |
Yes | Recent DX cluster, RBN, and logbook activity |
hamqth_dx_spots |
No | Live DX cluster spots — filter by band and/or callsign |
hamqth_rbn |
No | Reverse Beacon Network decodes — filter by band, mode, continent, callsign |
hamqth_verify_qso |
No | Verify a QSO via HamQTH SAVP protocol |
get_version_info |
No | Service version + upstream HamQTH API version (fleet identity attestation) |
Quick Start
1. Create a free HamQTH account
Sign up at hamqth.com — it's free, no subscription required.
2. Set up credentials
hamqth-mcp uses qso-graph-auth personas for credential management:
# Install qso-graph-auth if you haven't
uv tool install qso-graph-auth
# A persona (your callsign and the dates it covers), then HamQTH for it
qso-auth persona add --name ki7mt --callsign KI7MT --start 2020-01-01
qso-auth provider enable ki7mt hamqth
qso-auth creds set ki7mt hamqth # asks for your username, then your password (hidden)
All three steps are needed: without provider enable, the server reports that the persona has no hamqth ref.
3. Configure your MCP client
hamqth-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
ChatGPT Desktop
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
4. Ask questions
"Look up the callsign OK2CQR"
"What DXCC entity is VP8PJ?"
"Show me the biography for OK2CQR"
"What's the recent activity for KI7MT?"
"Show me DX spots for 3Y0K"
"What RBN decodes are there for 3Y0K on CW?"
"Show me 20m DX spots"
"Verify my QSO with OK2CQR on 20m on March 5"
Testing Without Credentials
The DXCC tool (hamqth_dxcc) works without any credentials — it uses a public endpoint.
For testing all tools without a HamQTH account:
HAMQTH_MCP_MOCK=1 hamqth-mcp
MCP Inspector
hamqth-mcp --transport streamable-http --port 8005
Then open the MCP Inspector at http://localhost:8005.
Development
git clone https://github.com/qso-graph/hamqth-mcp.git
cd hamqth-mcp
uv sync --group dev
uv run pytest
Known Quirks
- Sessions: HamQTH's XML sessions expire after an hour. The server signs in again after 55 minutes, so a long-running session never sees an expired one.
License
GPL-3.0-or-later
Metadata
Release files for hamqth-mcp 0.4.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hamqth_mcp-0.4.6.tar.gz | 174.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hamqth_mcp-0.4.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 198.6 kB
Release files / hamqth_mcp-0.4.6.tar.gz
| Download URL | hamqth_mcp-0.4.6.tar.gz |
|---|---|
| Size | 174.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5cef1dd72c51f9d11c1a3747daf7363308524d0bedad2269f6f701fbfed1333
|
|
BLAKE2b-256 checksum How to use checksums |
fa7de788dfc45e9dfc482730a05b1ce874b5866f54048d16469833ff07651550
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / hamqth_mcp-0.4.6-py3-none-any.whl
| Download URL | hamqth_mcp-0.4.6-py3-none-any.whl |
|---|---|
| Size | 24.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
140ba302a822a919e6bb6ab5b6f682ec454350d61f1d196738c7c480b1ad84b7
|
|
BLAKE2b-256 checksum How to use checksums |
19b6e6de564f8df7b0ec7d023884cea11795a68c22ac5f74d58020255af3b4c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log