io.github.qso-graph/wspr-mcp
PYPI · WSPR-MCP
WSPR beacon analytics MCP server. Band openings, path analysis, solar correlation.
Available components
Last scanned (17 hours ago)
Scores higher than 93% of PyPI servers
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to qso-graph/wspr-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1312 tokens (~145/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −4
- Stability: pass → 0.67 functional
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +22
- Malware scan: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- 29 Oct 26 0
- Package version: 0.6.0 → 0.6.1 functional
- 27 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.5.0 → 0.6.0 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.4.0 → 0.5.0 functional
- Package version: 0.4.0 → 0.4.3 functional
- Package version: 0.4.0 → 0.4.2 functional
- Package version: 0.4.0 → 0.4.1 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/wspr-mcp@0.6.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | qso-graph/wspr-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/wspr-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560641975 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:2121f34bede134b0e4e1cf7af4705c475f33e78328d1bd8c645dc61b5a946a6d |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 16 packages
| Packages resolved | 16 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_version_info Get Version Info ~78
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
wspr_band_activity Wspr Band Activity ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | – | – | Time window in hours (1-6, default 1). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_grid_activity Wspr Grid Activity ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m). Empty for all bands. |
| grid | string | yes | Maidenhead grid square — 2 char (DN) or 4 char (DN13). |
| hours | – | – | Time window in hours (1-72, default 24). |
| limit | – | – | Maximum recent spots to return (1-200, default 50). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_longest_paths Wspr Longest Paths ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m, 10m). Empty for all bands. |
| hours | – | – | Time window in hours (1-72, default 24). |
| limit | – | – | Maximum paths to return (1-50, default 20). |
| min_distance | – | – | Minimum distance in km (e.g., 15000 for near-antipodal). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_propagation Wspr Propagation ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter to a specific band (e.g., 20m). Empty for all bands. |
| hours | – | – | Time window in hours (1-72, default 24). |
| rx | string | yes | Second endpoint — callsign (e.g., G8JNJ) or grid (e.g., IO91). |
| tx | string | yes | First endpoint — callsign (e.g., KI7MT) or grid (e.g., DN13). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_snr_trend Wspr Snr Trend ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter to a specific band (e.g., 20m). Empty for all bands. |
| hours | – | – | Time window in hours (1-72, default 24). |
| rx | string | yes | Second endpoint — callsign (e.g., G8JNJ) or grid (e.g., IO91). |
| tx | string | yes | First endpoint — callsign (e.g., K9AN) or grid (e.g., EN50). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_spots Wspr Spots ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m, 40m, 10m). Empty for all bands. |
| callsign | – | – | Filter by TX or RX callsign (e.g., KI7MT, K9AN). Empty for all. |
| grid | – | – | Filter by grid square prefix (e.g., DN13, FN31). Matches TX or RX. |
| hours | – | – | Time window in hours (1-72, default 24). |
| limit | – | – | Maximum spots to return (1-200, default 50). |
| max_snr | – | – | Maximum SNR in dB (e.g., -5). Filter out strong signals. |
| min_distance | – | – | Minimum path distance in km (e.g., 5000 for DX only). |
| min_snr | – | – | Minimum SNR in dB (e.g., -20). Filter out weak signals. |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_top_beacons Wspr Top Beacons ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m). Empty for all bands. |
| hours | – | – | Time window in hours (1-72, default 24). |
| limit | – | – | Number of results (1-50, default 20). |
| sort_by | – | – | Ranking criteria — "spots" (most heard) or "distance" (farthest reach). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_top_spotters Wspr Top Spotters ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | Filter by band (e.g., 20m). Empty for all bands. |
| hours | – | – | Time window in hours (1-72, default 24). |
| limit | – | – | Number of results (1-50, default 20). |
| sort_by | – | – | Ranking criteria — "spots" (most received) or "distance" (farthest heard). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/wspr-mcp server?
io.github.qso-graph/wspr-mcp runs locally as a PyPI package, launched with uvx wspr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · wspr-mcp
claude mcp add qso-graph-wspr-mcp -- uvx wspr-mcp
What is the io.github.qso-graph/wspr-mcp server?
io.github.qso-graph/wspr-mcp is listed in the public MCP registry as io.github.qso-graph/wspr-mcp. WSPR beacon analytics MCP server. Band openings, path analysis, solar correlation. This page covers its PyPI package (wspr-mcp).
Is the io.github.qso-graph/wspr-mcp server safe to use?
io.github.qso-graph/wspr-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.qso-graph/wspr-mcp server expose?
io.github.qso-graph/wspr-mcp exposes 9 tools: get_version_info, wspr_spots, wspr_band_activity, wspr_top_beacons, wspr_top_spotters, and 4 more. Their descriptions and schemas cost roughly 1,220 tokens of context every time the server is loaded.
Is the io.github.qso-graph/wspr-mcp server still maintained?
io.github.qso-graph/wspr-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.qso-graph/wspr-mcp server under?
io.github.qso-graph/wspr-mcp declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.