wspr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 wspr-mcp service version and upstream spec version. Returns the running PyPI version of wspr-mcp and the wspr.live ClickHouse schema revision 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. |
| wspr_spotsB | Get recent WSPR spots. WSPR beacons transmit every 2 minutes on precise frequencies. Each spot is a 2-minute integration proving a propagation path exists. |
| wspr_band_activityA | Get per-band WSPR activity summary. Shows spot counts, TX/RX station counts, average and max distance, and average SNR for each band. The best indicator of which bands are open right now. |
| wspr_top_beaconsA | Get top WSPR transmitters ranked by spot count or max distance. Shows the most active or most far-reaching WSPR beacon operators. Useful for finding who's putting out a big signal on a band. |
| wspr_top_spottersA | Get top WSPR receivers ranked by spot count or max distance. Shows the most prolific or most sensitive WSPR receiving stations. Useful for finding good receivers to monitor for propagation. |
| wspr_propagationA | Get WSPR-derived propagation between two locations. Shows which bands have been open between two endpoints, with spot counts, SNR statistics, and hours of opening. Accepts callsigns or grid squares (or a mix). Searches both directions automatically. |
| wspr_grid_activityA | Get all WSPR activity in or out of a Maidenhead grid square. Shows summary stats and recent spots for a geographic area. Use 2-character grid (e.g., DN) for a wide area or 4-character (e.g., DN13) for a specific region. |
| wspr_longest_pathsA | Get the longest WSPR paths in the given time window. WSPR's precise timing and low power make it the gold standard for detecting marginal propagation. Long paths here prove the band is open. |
| wspr_snr_trendA | Get SNR trend over time for a specific WSPR path. Shows hourly SNR buckets for a path between two endpoints. Useful for seeing when a band opens and closes on a specific path, and how signal strength varies over time. |
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 9 tools
Each tool targets a distinct view: band summary, grid summary, two-endpoint propagation, SNR over time, top lists, longest paths, and raw spots. The closest overlap is wspr_propagation vs wspr_snr_trend (both take two endpoints), but the latter is explicitly a time-series view, so boundaries are mostly clear.
Eight tools follow a clean wspr_<noun> snake_case pattern (wspr_band_activity, wspr_top_beacons, wspr_grid_activity) that is highly predictable. get_version_info breaks the prefix convention with a verb_noun style, a minor but noticeable deviation.
Nine tools is right-sized for a read-only propagation-data server, with each tool covering a different analytical lens (band, grid, path, time, leaderboards). Nothing feels redundant or padded.
The surface covers the core WSPR workflows: raw spots, band activity, grid activity, point-to-point propagation, SNR trends, leaderboards, and version/health info. A per-callsign activity or spot-filtering-by-station view is a small gap, but top_beacons/spotters partially compensate.