io.github.qso-graph/wspr-mcp
PYPI · WSPR-MCP · SCANNED SEP 20
WSPR beacon analytics MCP server. Band openings, path analysis, solar correlation.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 127 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 488 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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
{
"mcpServers": {
"qso-graph-wspr-mcp": {
"command": "uvx",
"args": [
"wspr-mcp"
]
}
}
} {
"servers": {
"qso-graph-wspr-mcp": {
"command": "uvx",
"args": [
"wspr-mcp"
]
}
}
} codex mcp add qso-graph-wspr-mcp -- uvx wspr-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qso-graph-wspr-mcp": {
"type": "local",
"command": [
"uvx",
"wspr-mcp"
],
"enabled": true
}
}
} openclaw mcp add qso-graph-wspr-mcp --command uvx --arg wspr-mcp
mcp_servers:
qso-graph-wspr-mcp:
command: "uvx"
args: ["wspr-mcp"] {
"McpServers": {
"qso-graph-wspr-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"wspr-mcp"
]
}
}
} assistant mcp add qso-graph-wspr-mcp -t stdio -c uvx -a wspr-mcp
{
"mcpServers": {
"qso-graph-wspr-mcp": {
"command": "uvx",
"args": [
"wspr-mcp"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −14
- Malware scan: pass → unverified ▼ 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 20 Sept 2026 · Analysed pypi/wspr-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 15 packages
| Packages resolved | 15 |
|---|---|
| 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 →
wspr_activity Wspr Activity ~64
Get WSPR activity summary for a callsign. Shows TX/RX spot counts, active bands, unique reporters, maximum distance, and best SNR.
| Name | Type | Req | Description |
|---|---|---|---|
| callsign | string | yes | Callsign to look up (e.g., KI7MT, K9AN). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_band_activity Wspr Band Activity ~72
Get current per-band WSPR activity summary. Shows how many WSPR spots, TX stations, and RX stations are active on each band, with average path distance. Useful for seeing which bands are open right now. Returns: Per-band activity with spot counts, station counts, and average distance.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
wspr_propagation Wspr Propagation ~105
Get WSPR-derived propagation between two grid squares. Shows which bands have been open between two locations in the last 24 hours, with spot counts, average SNR, best SNR, and hours of opening. Based on actual WSPR beacon observations.
| Name | Type | Req | Description |
|---|---|---|---|
| rx_grid | string | yes | Receiver grid square (e.g., JN48, IO91). |
| tx_grid | string | yes | Transmitter grid square (e.g., DN13, FN31). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_spots Wspr Spots ~107
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 | string | – | Filter by band (e.g., 20m, 40m). Empty for all bands. |
| callsign | string | – | Filter by TX or RX callsign. Empty for all. |
| limit | integer | – | Maximum spots to return (default 50, max 200). |
Structured output declared, but exposes no named fields.
No examples provided.
wspr_top_paths Wspr Top Paths ~91
Get the longest/best WSPR paths in the last 24 hours. 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 | string | – | Filter by band (e.g., 20m). Empty for all bands. |
| limit | integer | – | Maximum paths to return (default 20). |
Structured output declared, but exposes no named fields.
No examples provided.
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 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 5 tools: wspr_spots, wspr_activity, wspr_band_activity, wspr_top_paths, wspr_propagation. Their descriptions and schemas cost roughly 439 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 20 September 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.