hamqth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HAMQTH_MCP_MOCK | No | Set to 1 to use mock data for testing without credentials | 1 |
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": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get hamqth-mcp service version and upstream HamQTH API version. Returns the running PyPI version of hamqth-mcp and the HamQTH.com 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. |
| hamqth_lookupA | Look up a callsign on HamQTH (free, no subscription required). Returns name, grid, DXCC, coordinates, QSL preferences, and more. Field availability depends on what the operator has published. |
| hamqth_dxccB | Resolve a DXCC entity from a callsign or ADIF entity code. Public endpoint — no authentication required. |
| hamqth_bioC | Fetch an operator's biography from HamQTH. |
| hamqth_activityB | Get recent DX cluster, RBN, and logbook activity for a callsign. |
| hamqth_dx_spotsA | Live DX cluster spots from HamQTH (public, no auth required). Spots update every ~15 seconds. Max 200 spots per request. |
| hamqth_rbnB | Reverse Beacon Network spots from HamQTH (public, no auth required). |
| hamqth_verify_qsoA | Verify a QSO via HamQTH SAVP protocol (public, no auth required). Checks if a QSO exists in HamQTH's database for both parties. |
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 8 tools
Most tools have distinct purposes, but hamqth_activity overlaps with both hamqth_dx_spots and hamqth_rbn because it aggregates DX cluster and RBN data. Descriptions clarify per-callsign activity versus live feeds, so the ambiguity is moderate rather than severe.
Seven of eight tools use a consistent hamqth_ snake_case prefix. get_version_info breaks the prefix pattern and verb/noun style varies, but the names are still predictable and readable.
Eight tools are well-scoped for a read-only HamQTH lookup and spot service. Each tool corresponds to a meaningful API capability, with no evident padding.
The set covers lookup, bio, DXCC, spots, RBN, activity, QSO verification, and version info. For a read-only data service this provides a complete workflow without obvious dead ends.