io.github.qso-graph/solar-mcp
PYPI · SOLAR-MCP
Solar indices and space weather MCP server. SFI, SSN, Kp, DSCOVR, NOAA alerts.
Available components
Last scanned (56 minutes ago)
Scores higher than 93% of PyPI servers
Category Maps and Location
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/solar-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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 617 tokens (~88/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +9
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.57 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.5.0 → 0.5.1 functional
- 27 Oct 26 0
- Package version: 0.4.0 → 0.5.0 functional
- 26 Oct 26 0
- Schema quality: 70 → 88 ▼ functional
- Package version: 0.3.0 → 0.4.0 functional
- Package version: 0.3.0 → 0.3.3 functional
- Package version: 0.3.0 → 0.3.2 functional
- Package version: 0.3.0 → 0.3.1 functional
- 24 Oct 26 +1
- Stability: 0.97 → 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 5 Nov 2026 · Analysed pypi/solar-mcp@0.5.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/solar-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qso-graph/solar-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560503265 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f3d8ea993057821f2c6c4fc547052f7d1a3440b1df13beba2d962870334c0c89 |
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 ~76
Get solar-mcp service version and upstream spec version. Returns the running PyPI version of solar-mcp and the NOAA SWPC endpoint set revision currently 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.
solar_alerts Solar Alerts ~41
Get active NOAA space weather alerts and warnings. Shows current solar flare alerts, geomagnetic storm warnings, radiation storm alerts, and other SWPC bulletins.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solar_band_outlook Solar Band Outlook ~187
Get HF band-by-band propagation outlook based on current conditions. Derives a propagation assessment for each HF band (160m through 6m) from the current SFI and Kp values. Useful for deciding which band to operate on right now. Each band is rated "<status> — <comment>", the status one of five words defined in BAND-OUTLOOK.md: Excellent (wide open, strong long-lasting DX), Good (regular DX openings in the band's usual hours), Fair (short, patchy or weak openings; DX possible, not dependable), Poor (likely closed for DX, or degraded by absorption and noise), Sporadic (not graded from the indices: 6m opens by sporadic-E, and by F2 at high solar flux). The thresholds are rules of thumb on SFI and Kp, not a propagation model.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solar_conditions Solar Conditions ~72
Get current solar conditions — SFI, Kp, and NOAA space weather scales. Returns the latest 10.7 cm solar flux index (SFI), planetary Kp index, and NOAA R/S/G scales (radio blackout, solar radiation, geomagnetic storm). Includes an HF band outlook derived from current indices.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solar_forecast Solar Forecast ~54
Get the NOAA 27-day solar flux and geomagnetic forecast. Shows predicted SFI and Kp values for the next 27 days, useful for planning DX operations, contests, and POTA/SOTA activations.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solar_wind Solar Wind ~69
Get real-time DSCOVR L1 solar wind data. Shows interplanetary magnetic field (Bz component), solar wind speed, and proton density from the DSCOVR satellite at L1 (~1.5M km sunward). Southward Bz (negative) drives geomagnetic storms.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solar_xray Solar Xray ~57
Get GOES X-ray flux and solar flare status. Shows the current X-ray classification (A, B, C, M, X) from GOES satellite data. M and X class flares can cause HF radio blackouts.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.qso-graph/solar-mcp server?
io.github.qso-graph/solar-mcp runs locally as a PyPI package, launched with uvx solar-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 · solar-mcp
claude mcp add qso-graph-solar-mcp -- uvx solar-mcp
What is the io.github.qso-graph/solar-mcp server?
io.github.qso-graph/solar-mcp is listed in the public MCP registry as io.github.qso-graph/solar-mcp. Solar indices and space weather MCP server. SFI, SSN, Kp, DSCOVR, NOAA alerts. This page covers its PyPI package (solar-mcp).
Is the io.github.qso-graph/solar-mcp server safe to use?
io.github.qso-graph/solar-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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/solar-mcp server expose?
io.github.qso-graph/solar-mcp exposes 7 tools: get_version_info, solar_conditions, solar_forecast, solar_alerts, solar_wind, and 2 more. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.
Is the io.github.qso-graph/solar-mcp server still maintained?
io.github.qso-graph/solar-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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/solar-mcp server under?
io.github.qso-graph/solar-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.