
Connects your AI assistant to HamQTH.com's amateur radio database for callsign lookups, DX cluster spots, and Reverse Beacon Network data. You get eight tools covering operator info (name, grid, DXCC, QSL preferences), biographies, recent activity, live propagation data filtered by band or mode, and QSO verification through the SAVP protocol. Most tools require a free HamQTH account managed through the qso-graph persona system, but DXCC resolution and some queries work unauthenticated. Built for ham radio operators who want to query callsigns, track DX activity, or verify contacts without leaving their editor or chat interface.
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.
uvx hamqth-mcp # run it; nothing to install
| 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) |
Sign up at hamqth.com — it's free, no subscription required.
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.
hamqth-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Add to .claude/settings.json:
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"hamqth": {
"command": "uvx",
"args": ["hamqth-mcp"]
}
}
}
"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"
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
hamqth-mcp --transport streamable-http --port 8005
Then open the MCP Inspector at http://localhost:8005.
git clone https://github.com/qso-graph/hamqth-mcp.git
cd hamqth-mcp
uv sync --group dev
uv run pytest
GPL-3.0-or-later