spaceweather-mcp
A Model Context Protocol server for space weather and geomagnetic conditions — solar flares, the solar wind, geomagnetic storms (Kp/Dst), radiation storms, sunspot regions, aurora forecasts, and a catalogued event history — so an AI agent can answer "what's the sun/space weather doing right now, and will I see aurora?" from authoritative data.
Sibling to seismic-mcp: that one reconciles earthquakes across agencies; this one reports solar/geomagnetic conditions. They install side by side.
Status
15 tools across 4 data sources — all live and verified. Everything is U.S./NASA public domain except the Kyoto Dst index, which is non-commercial and clearly labeled (and kept segregated from the public-domain feeds).
Tools
NOAA SWPC (public domain)
| Tool | Returns |
|---|---|
get_conditions_now |
One-call snapshot: Kp, Bz/Bt, wind speed/density, G/S/R, storm flag, summary |
get_kp_index |
Observed planetary Kp series (~1 week) |
get_kp_forecast |
NOAA 3-day Kp forecast |
get_solar_wind |
L1 magnetic field + plasma (window: 1-day/7-day) |
get_alerts |
Recent SWPC alerts/watches/warnings |
get_noaa_scales |
G/S/R scales for today + 3 days |
get_27day_outlook |
Daily F10.7 flux, Ap, largest Kp for 27 days |
get_solar_flares |
Recent GOES X-ray flares (C/M/X class events) |
get_radiation_storm |
Current proton flux + NOAA S-scale (radiation storm) |
get_solar_regions |
Today's sunspot regions + C/M/X flare probabilities |
get_aurora_forecast |
OVATION aurora probability (pass lat/lon for a local %) |
NASA DONKI (public domain) — get_space_weather_events (CME / GST / FLR / SEP / IPS / HSS event catalog)
USGS Geomagnetism (public domain) — list_observatories, get_observatory (magnetometer X/Y/Z/F)
Kyoto WDC (non-commercial) — get_dst (hourly disturbance storm-time index)
Run
uv run spaceweather-mcp # stdio MCP server
uv run pytest # tests
Add to claude_desktop_config.json (after publishing to PyPI):
{ "mcpServers": { "spaceweather": { "command": "uvx", "args": ["spaceweather-mcp"] } } }
Data sources, attribution & licensing
- NOAA SWPC (
services.swpc.noaa.gov) — U.S. public domain. Credit NOAA SWPC. - NASA DONKI via CCMC (
kauai.ccmc.gsfc.nasa.gov/DONKI) — U.S. public domain (no API key needed). Credit NASA/CCMC DONKI. - USGS Geomagnetism (
geomag.usgs.gov) — U.S. public domain. Credit the U.S. Geological Survey. (Sourced directly from USGS, not via INTERMAGNET, to keep public-domain status.) - Kyoto WDC for Geomagnetism — Dst index, non-commercial use only: acknowledge "WDC for Geomagnetism, Kyoto", cite the Dst DOI; real-time values are provisional. The non-commercial restriction is documented in the
get_dsttool description and theDstReadingschema (both surfaced to MCP clients), and this feed is kept separate from the public-domain ones.
⚠️ Only the Kyoto Dst feed is non-commercial. It is segregated, and its non-commercial terms are stated in the tool/schema docs the client sees, so a downstream commercial user is not silently bound by those terms.
Deliberately not included: INTERMAGNET and SILSO sunspot number (both CC BY-NC — would taint the otherwise commercially-usable server); JPL Horizons ephemeris (different domain). F10.7 is available via get_27day_outlook; GFZ Hp30/Hp60 high-cadence indices (CC BY 4.0) are a possible future add.
Safety
Informational only. Not for operational decisions affecting power grids, aviation, satellites, or human safety — consult official NOAA SWPC products for those. Real-time values are preliminary and routinely revised.
Metadata
Release files for spaceweather-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spaceweather_mcp-0.1.0.tar.gz | 95.2 kB | Without provenance | Details for spaceweather_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spaceweather_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for spaceweather_mcp-0.1.0-py3-none-any.whl |
Total release size: 119.0 kB
Release files / spaceweather_mcp-0.1.0.tar.gz
| Download URL | spaceweather_mcp-0.1.0.tar.gz |
|---|---|
| Size | 95.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebd223d1809e181f2af9524865bd823b283d038a25ce61e3a3924ce8c4b096b9
|
|
BLAKE2b-256 checksum How to use checksums |
4e56803e3a2682206ba9bfbc60da32d0ee09c4e17445d6069bc0ede146d40395
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / spaceweather_mcp-0.1.0-py3-none-any.whl
| Download URL | spaceweather_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53175389d437070ab75e69b61727617e0bc65a34bed1574f57ce586d9d533c1f
|
|
BLAKE2b-256 checksum How to use checksums |
e904756ff0b03c027565d787494eb6c06aef750c036862c8d914139151554739
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for spaceweather-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.