
Spaceweather Mcp
io.github.hoon1983Published by GitHub account hoon1983v0.1.0Updated Oct 24, 2026
Space weather & geomagnetic conditions (NOAA SWPC, NASA DONKI, USGS, Kyoto) via MCP.
Overview
A local MCP server that gives an assistant live space weather and geomagnetic data from NOAA SWPC, NASA DONKI, USGS and Kyoto, including aurora forecasts.
- What you can do
- Read current conditions and Kp index, Kp forecast, solar wind, NOAA alerts and G/S/R scales, 27-day outlook, solar flares, radiation storms and sunspot regions with flare probabilities, plus aurora probability for a given latitude and longitude (NOAA SWPC). Look up catalogued CME, geomagnetic storm, flare, SEP, IPS and HSS events (NASA DONKI). List and read USGS geomagnetic observatories with magnetometer X/Y/Z/F values. Retrieve the hourly Kyoto Dst disturbance storm-time index.
- When to use it
- Useful when you want an assistant to answer questions about current solar and geomagnetic activity, storm levels, flare risk or aurora chances, drawing on authoritative public feeds rather than general knowledge. Not intended for operational or safety-critical decisions.
- Requirements
- Runs as a local stdio process, installed from the PyPI package spaceweather-mcp (for example via uvx). No API keys, accounts or environment variables are declared. Network access to the NOAA SWPC, NASA DONKI, USGS and Kyoto data services is needed.
Installation
In SourceWeft
- Open Spaceweather Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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)
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
Add to claude_desktop_config.json (after publishing to PyPI):
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.
Source: README.md at commit 8d26086
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts