Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/noaa-spaceweather-mcp-server

REMOTE · NOAA-SPACEWEATHER.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 28

NOAA SWPC space weather: storm scales, Kp index, aurora forecasts, solar wind, activity, alerts.

+7 this week 87 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1863 tokens (~310/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the io.github.cyanheads/noaa-spaceweather-mcp-server server?

io.github.cyanheads/noaa-spaceweather-mcp-server is a hosted endpoint at https://noaa-spaceweather.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · noaa-spaceweather.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-noaa-spaceweather-mcp-server 'https://noaa-spaceweather.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-noaa-spaceweather-mcp-server": {
      "url": "https://noaa-spaceweather.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-noaa-spaceweather-mcp-server": {
      "type": "http",
      "url": "https://noaa-spaceweather.caseyjhand.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cyanheads-noaa-spaceweather-mcp-server]
url = "https://noaa-spaceweather.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-noaa-spaceweather-mcp-server": {
      "type": "remote",
      "url": "https://noaa-spaceweather.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-noaa-spaceweather-mcp-server --url 'https://noaa-spaceweather.caseyjhand.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-noaa-spaceweather-mcp-server:
    url: "https://noaa-spaceweather.caseyjhand.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-noaa-spaceweather-mcp-server": {
      "Transport": "http",
      "Url": "https://noaa-spaceweather.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-noaa-spaceweather-mcp-server -t streamable-http -u 'https://noaa-spaceweather.caseyjhand.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cyanheads-noaa-spaceweather-mcp-server": {
      "type": "http",
      "url": "https://noaa-spaceweather.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • Tool “noaa_spaceweather_get_solar_wind” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_solar_activity” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_conditions” rewrote its description, which is the text the model reads security
    • Server version: 0.2.1 → 0.3.1 functional
    • “noaa_spaceweather_get_solar_wind” reworded the description of “resolution” cosmetic
  • 22 Sept 26 0
    • Tool “noaa_spaceweather_get_aurora_forecast” rewrote its description, which is the text the model reads security
    • Server version: 0.2.0 → 0.2.1 functional
  • 17 Sept 26 −2
    • Tool “noaa_spaceweather_get_solar_wind” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_conditions” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_solar_activity” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_kp_index” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_aurora_forecast” rewrote its description, which is the text the model reads security
    • Tool “noaa_spaceweather_get_alerts” rewrote its description, which is the text the model reads security
    • Schema quality: 187 → 284 ▼ functional
    • Schema quality: 187 → 226 ▼ functional
    • Server version: 0.1.14 → 0.2.0 functional
    • Server version: 0.1.13 → 0.1.14 functional
    • “noaa_spaceweather_get_conditions” added an optional parameter “include_discussion” cosmetic
    • “noaa_spaceweather_get_solar_activity” added an optional parameter “flare_hours” cosmetic
    • “noaa_spaceweather_get_solar_wind” added an optional parameter “resolution” cosmetic
    • “noaa_spaceweather_get_solar_wind” reworded the description of “window_hours” cosmetic
    • “noaa_spaceweather_get_alerts” reworded the description of “max_age_hours” cosmetic
    • “noaa_spaceweather_get_alerts” reworded the description of “active_only” cosmetic
  • 16 Sept 26 0
    • Server version: 0.1.12 → 0.1.13 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
Diagnostics

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 28 Sept 2026 · Probed https://noaa-spaceweather.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of noaa-spaceweather.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
noaa-spaceweather.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://noaa-spaceweather.caseyjhand.com/mcp Verified 200
http (plaintext) http://noaa-spaceweather.caseyjhand.com/mcp HTTPS enforced 301 https://noaa-spaceweather.caseyjhand.com/mcp
MCP tools · 6 exposed · ~1,741 tokens

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 →

Tool Tokens
noaa_spaceweather_get_alerts ~355

Active SWPC alerts, watches, and warnings — parsed into structured records with product type, NOAA scale and level, issue time, serial number, validity window, and plain text. Covers geomagnetic storms, radio blackouts, and radiation storms. With active_only=false, also returns informational summaries, expired notices, and cancellations. max_age_hours controls how far back to look for candidates (default 48 h) — under active_only=true it does not cut off a product whose validity end is still in the future, and under active_only=false it is a literal age cutoff. The SWPC feed keeps all historical records and has no built-in expiry.

NameTypeReqDescription
active_onlyboolean–When true (default), return only in-force Warnings, Watches, and Alerts. Excluded: Summaries and unrecognized products; products whose validity end has passed; cancellation notices; any product a lat…
max_age_hoursnumber–How far back to look for products, in hours (default 48). The SWPC feed retains all historical records, so this bounds the candidate set rather than declaring what is current. Under active_only=true…
NameTypeReqDescription
activeOnlyboolean–Echo of active_only: true for the in-force set, false for every product in the window.
alertsarray–Matching SWPC products.
appliedCutoffstring–ISO 8601 UTC start of the applied window. Present only under active_only=true.
appliedWindowHoursnumber–max_age_hours as applied. Present only under active_only=true.
errorobject–Present when the call failed. Absent on success.
exclusionsobject–Records active_only=true left out, each counted under its first reason in field order; with totalCount they sum to the feed total. Present only under active_only=true, when something was excluded.
fetchedAtstring–ISO 8601 fetch time.
noticestring–Set when no products were returned.
totalCountnumber–Records in alerts.

No examples provided.

noaa_spaceweather_get_aurora_forecast ~230

OVATION model aurora forecast for the next ~30–60 min: global grid of aurora probability percentages by latitude/longitude (1° resolution). With optional coordinates, returns the local aurora probability at the nearest grid point, the geomagnetic latitude those coordinates convert to, the minimum Kp and G level needed for aurora at that geomagnetic latitude, the sun’s elevation there at the forecast time (aurora is not visible in daylight), the strongest aurora within 1000 km poleward (visible low on the horizon when bright), and a plain-language go/no-go verdict. Without coordinates, returns only global metadata. Data updates every ~5 minutes. Supply coordinates as geographic (WGS84); aurora bands are geomagnetic, and the tool converts between them.

NameTypeReqDescription
latitudenumber–Geographic latitude in degrees (−90 to 90). Provide with longitude for a local aurora probability lookup.
longitudenumber–Geographic longitude in degrees (−180 to 180). Provide with latitude for a local aurora probability lookup.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
forecastTimestring–ISO 8601 time the forecast is valid for.
gridPointCountnumber–OVATION grid point count.
localLookup––Coordinate lookup; null when no coordinates were given.
observationTimestring–ISO 8601 OVATION observation time.
topAuroraPercentnumber–Highest aurora probability on the globe (0–100%).
topAuroraRegionstring–Location of the highest grid point, e.g. "67°N, 20°W"; "Unknown" when every cell is 0%.

No examples provided.

noaa_spaceweather_get_conditions ~182

Current space-weather snapshot: NOAA R/S/G storm scales (the previous UTC day, today, and the 3-day forecast), latest Kp index with its G-scale equivalent and aurora-visibility latitude, and a plain-language status summary. Optionally includes the SWPC forecast discussion explaining what is driving the forecast. The quickest way to answer "is anything happening right now?" — use before deciding whether to drill into solar wind (noaa_spaceweather_get_solar_wind), aurora (noaa_spaceweather_get_aurora_forecast), or alert details (noaa_spaceweather_get_alerts).

NameTypeReqDescription
include_discussionboolean–Also fetch SWPC's forecaster-written Forecast Discussion, which explains why the forecast looks the way it does (CME versus coronal-hole stream, expected arrival). Costs one extra upstream request.
NameTypeReqDescription
auroraLatitudestring–Aurora guidance for currentKp, e.g. "Aurora possible to ~55° geomagnetic latitude".
currentGScalenumber–G level (0–5) for currentKp.
currentKpnumber–Latest observed planetary K-index (0–9).
discussion––SWPC Forecast Discussion; null unless include_discussion is true.
errorobject–Present when the call failed. Absent on success.
forecastarray–3-day scale forecast, oldest first; starts with today (the date of observedAt).
observedAtstring–ISO 8601 UTC time of the scales data period, e.g. "2026-06-04T15:00:00Z".
summarystring–Plain-language status, e.g. "G2 moderate geomagnetic storm in progress."
todayobject–Observed R/S/G levels for today.
yesterday––R/S/G levels assessed for the previous UTC day (a date, no time). Null when the feed lacks that period or a level; null never means level 0.

No examples provided.

noaa_spaceweather_get_kp_index ~220

Planetary K-index (0–9 geomagnetic activity scale) — recent observed 3-hour values with their NOAA G-scale equivalents and aurora-latitude guidance, plus the 3-day Kp forecast series. Kp is the primary driver of aurora visibility and geomagnetic storm severity. SWPC reports Kp in thirds and starts each G level at that level’s "minus" value: Kp 4.67 (5−) is G1, Kp 6.67 (7−) is G3 (aurora to ~50° geomagnetic), Kp 8.67 (9−) is still G4, and only Kp 9 is G5 extreme. Use noaa_spaceweather_get_conditions for a combined snapshot including storm scales; use this tool when you need the Kp time series or forecast detail.

NameTypeReqDescription
window_daysinteger–Number of past days of observed Kp to return (1–7, default 1). Larger windows show trend context.
NameTypeReqDescription
auroraLatitudestring–Aurora guidance for currentKp.
currentGScalenumber–G level (0–5) for currentKp.
currentKpnumber–Latest observed Kp; 0 when the window has none.
errorobject–Present when the call failed. Absent on success.
forecastarray–Kp forecast series: estimated and predicted entries, no observed history.
observedarray–Observed Kp in the window, oldest first.
observedCountnumber–Entries in observed.

No examples provided.

noaa_spaceweather_get_solar_activity ~265

Solar flare and radiation storm picture: discrete flare events from the past week with peak class and R-scale level, recent GOES X-ray flux with flare-class labels (A/B/C/M/X) and class magnitude, the daily F10.7 cm solar radio flux, 3-day flare-class probabilities (C/M/X), active solar regions with per-region flare probabilities, and GOES integral proton flux at ≥10 MeV with NOAA S-scale. For operators tracking HF radio blackout (R-scale, driven by X-ray) and radiation storm risk (S-scale, driven by protons). Each active region carries the C/M/X flare counts SWPC attributed to it that UTC day, which identify the region driving current activity — the flare events themselves carry no region.

NameTypeReqDescription
flare_hoursinteger–How far back to report discrete flare events, in hours before now, filtered on each flare’s onset time (1–168, default 24). The feed keeps a rolling 7 days, so 168 returns everything it carries. When…
include_regionsboolean–Include active solar region details (default true). Set false to skip region data and reduce response size.
NameTypeReqDescription
activeRegionsarray–Active regions; empty when include_regions=false or none are active.
errorobject–Present when the call failed. Absent on success.
f107––Latest Noon report, SWPC's daily F10.7 value; null when the feed has none.
fetchedAtstring–ISO 8601 fetch time.
latestProton––Newest ≥10 MeV proton reading; null when the feed is empty.
latestXray––Newest X-ray reading; null when the feed is empty.
noticestring–Set when no flare began in the flare_hours window: names the newest flare in the feed, or says the feed has none.
probabilitiesarray–3-day flare probability forecast.
recentFlaresarray–Flares with onset inside flare_hours, oldest first; empty when none began.
recentXrayarray–X-ray readings from the past hour, oldest first.
sScalenumber–Current S level (0–5) from latestProton; 0 without a reading.
sScaleTextstring–S level descriptor, e.g. "S2 moderate radiation storm".

No examples provided.

noaa_spaceweather_get_solar_wind ~489

Real-time solar wind measurements from the active spacecraft at L1: proton speed (km/s), density (n/cm³), temperature (K), and the critical Bz component (southward Bz = negative = storm driver). Returns the recent plasma and magnetic field time series within the requested window, oldest first, each record tagged with the reporting spacecraft and bounded to 200 records per series unless resolution is set to "full" — or omitted entirely under "summary", which keeps the latest readings, Bz status, and window extremes (peak speed, density, and Bt; most southward Bz; minutes of southward Bz) for "what is Bz doing now" questions. Bz < −10 nT for sustained periods is a primary geomagnetic storm trigger — use alongside noaa_spaceweather_get_kp_index to see whether elevated solar wind has translated into a geomagnetic storm.

NameTypeReqDescription
resolutionstring–Detail level of the returned plasma and mag series. "summary" returns both series empty and keeps every headline field — about 2 KB whatever the window. "reduced" (default) bounds each series to at m…
window_hoursinteger–Hours of recent solar wind history to return (1–168, default 3). Records update ~every 1 min, but the feed only carries roughly the last 24 hours — a larger window returns the whole feed, not more hi…
NameTypeReqDescription
btMaxInWindownumber|null–Peak Bt in nT across the whole window; null when it has no Bt.
bzMinInWindownumber|null–Most southward Bz in nT across the whole window; null when it has no Bz.
bzMinTimeTagstring|null–ISO 8601 time of bzMinInWindow; null when it is null.
bzSouthMinutesInWindownumber–Minutes of Bz < 0: 1-minute mag records across the whole window. Feed gaps are not counted. 0 when none.
bzStatusstring–Bz status from latestMag, e.g. "Southward Bz -14 nT — storm-driving conditions."; "Bz data unavailable." without a reading.
densityMaxInWindownumber|null–Peak proton density in particles/cm³ across the whole window; null when none.
errorobject–Present when the call failed. Absent on success.
feedStalenessHoursnumber|null–Hours from the newest record in either feed to now; null when both are empty.
latestFeedMagTimestring|null–ISO 8601 time of the newest mag record in the feed, window aside; null when none.
latestFeedPlasmaTimestring|null–ISO 8601 time of the newest plasma record in the feed, window aside; null when none.
latestMag––Newest mag record in the window; null when the window has none.
latestPlasma––Newest plasma record in the window; null when the window has none.
magarray–Mag records in the window, oldest first. "reduced": at most 200, each its bucket's most southward Bz; the last equals latestMag. Empty under "summary".
magBucketRecordsnumber–Mag records per emitted record, 1 if untouched. Present only after a reduction.
magCountnumber–Records in mag (magWindowRecords has the pre-reduction total); under "summary", the records the window held.
magWindowRecordsnumber–Mag records in the window before reduction. Present after a reduction or under "summary".
noticestring–What shaped the response: an empty window (with the newest feed record), series bounded to 200 records, or series omitted under "summary".
plasmaarray–Plasma records in the window, oldest first. "reduced": at most 200, each its bucket's fastest speed, newest last. Empty under "summary".
plasmaBucketRecordsnumber–Plasma records per emitted record, 1 if untouched. Present only after a reduction.
plasmaCountnumber–Records in plasma (plasmaWindowRecords has the pre-reduction total); under "summary", the records the window held.
plasmaWindowRecordsnumber–Plasma records in the window before reduction. Present after a reduction or under "summary".
speedMaxInWindownumber|null–Peak speed in km/s across the whole window; null when it has no speed.
speedMaxTimeTagstring|null–ISO 8601 time of speedMaxInWindow; null when it is null.

No examples provided.

Common questions

What is the io.github.cyanheads/noaa-spaceweather-mcp-server server?

io.github.cyanheads/noaa-spaceweather-mcp-server is listed in the public MCP registry as io.github.cyanheads/noaa-spaceweather-mcp-server. NOAA SWPC space weather: storm scales, Kp index, aurora forecasts, solar wind, activity, alerts. This page covers its hosted endpoint (https://noaa-spaceweather.caseyjhand.com/mcp).

Is the io.github.cyanheads/noaa-spaceweather-mcp-server server safe to use?

io.github.cyanheads/noaa-spaceweather-mcp-server scores 87 out of 100 on VerifyMCP. 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.cyanheads/noaa-spaceweather-mcp-server server expose?

io.github.cyanheads/noaa-spaceweather-mcp-server exposes 6 tools: noaa_spaceweather_get_conditions, noaa_spaceweather_get_alerts, noaa_spaceweather_get_kp_index, noaa_spaceweather_get_solar_wind, noaa_spaceweather_get_solar_activity, noaa_spaceweather_get_aurora_forecast. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.

Does the io.github.cyanheads/noaa-spaceweather-mcp-server server require authentication?

No. We connected to io.github.cyanheads/noaa-spaceweather-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/noaa-spaceweather-mcp-server server still maintained?

io.github.cyanheads/noaa-spaceweather-mcp-server is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.