@cyanheads/noaa-spaceweather-mcp-server 0.1.13 → 0.2.0

package/AGENTS.md

@@ -1,11 +1,11 @@
 # Developer Protocol
 
 **Server:** noaa-spaceweather-mcp-server
-**Version:** 0.1.13
-**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.2`
+**Version:** 0.2.0
+**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.3`
 **Engines:** Bun ≥1.4.0, Node ≥24.0.0
 **MCP SDK:** `@modelcontextprotocol/server` ^2.0.0 (protocol revisions 2026-07-28 and 2025-*)
-**Zod:** ^4.6.4
+**Zod:** ^4.6.5
 
 > **Read the framework docs first:** `node_modules/@cyanheads/mcp-ts-core/CLAUDE.md` contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
 
@@ -217,7 +217,7 @@ Available skills:
 | `code-simplifier` | Post-session cleanup against `git diff` — modernize syntax, consolidate duplication, align with the codebase |
 | `polish-docs-meta` | Finalize docs, README, metadata, and agent protocol for shipping |
 | `git-wrapup` | Land working-tree changes as a commit stack — version bump, changelog, verify, commit by concern, release commit on top. No tag, no push to main; opens the release PR when the project declares release PR mode |
-| `release-pr-review` | Review pass on an open release PR — simplifier + correctness review, fixup commits autosquashed into the stack, PR body kept in sync. Release PR mode only |
+| `release-pr-review` | Review pass on an open release PR — simplifier + correctness review, fixes as ordinary commits on top of the stack, PR body kept in sync. Release PR mode only |
 | `release-and-publish` | Fast-forward merge (release PR mode) + tag + push + npm + MCP Registry + GH Release + Docker. Picks up from `git-wrapup` |
 | `maintenance` | Investigate changelogs, adopt upstream changes, sync skills to agent dirs |
 | `orchestrations` | Chain task skills into a gated multi-phase pipeline — build-out, QA-fix, update-ship — when you can spawn sub-agents |
@@ -268,6 +268,8 @@ When you complete a skill's checklist, check the boxes and add a completion time
 | `bun run changelog:check` | Verify `CHANGELOG.md` is in sync (used by devcheck) |
 | `bun run bundle` | Build, pack, and clean a `.mcpb` for one-click Claude Desktop install |
 
+**CI is one file.** `.github/workflows/codeql.yml` (scaffolded) is the only GitHub Actions workflow: CodeQL is GitHub-owned end to end, and the file runs only while the repo's CodeQL *default setup* is turned off. Verification — `devcheck`, tests, the release gates — runs locally; don't add a workflow that re-runs it.
+
 ---
 
 ## Bundling

package/CLAUDE.md

@@ -1,11 +1,11 @@
 # Developer Protocol
 
 **Server:** noaa-spaceweather-mcp-server
-**Version:** 0.1.13
-**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.2`
+**Version:** 0.2.0
+**Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.13.3`
 **Engines:** Bun ≥1.4.0, Node ≥24.0.0
 **MCP SDK:** `@modelcontextprotocol/server` ^2.0.0 (protocol revisions 2026-07-28 and 2025-*)
-**Zod:** ^4.6.4
+**Zod:** ^4.6.5
 
 > **Read the framework docs first:** `node_modules/@cyanheads/mcp-ts-core/CLAUDE.md` contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
 
@@ -217,7 +217,7 @@ Available skills:
 | `code-simplifier` | Post-session cleanup against `git diff` — modernize syntax, consolidate duplication, align with the codebase |
 | `polish-docs-meta` | Finalize docs, README, metadata, and agent protocol for shipping |
 | `git-wrapup` | Land working-tree changes as a commit stack — version bump, changelog, verify, commit by concern, release commit on top. No tag, no push to main; opens the release PR when the project declares release PR mode |
-| `release-pr-review` | Review pass on an open release PR — simplifier + correctness review, fixup commits autosquashed into the stack, PR body kept in sync. Release PR mode only |
+| `release-pr-review` | Review pass on an open release PR — simplifier + correctness review, fixes as ordinary commits on top of the stack, PR body kept in sync. Release PR mode only |
 | `release-and-publish` | Fast-forward merge (release PR mode) + tag + push + npm + MCP Registry + GH Release + Docker. Picks up from `git-wrapup` |
 | `maintenance` | Investigate changelogs, adopt upstream changes, sync skills to agent dirs |
 | `orchestrations` | Chain task skills into a gated multi-phase pipeline — build-out, QA-fix, update-ship — when you can spawn sub-agents |
@@ -268,6 +268,8 @@ When you complete a skill's checklist, check the boxes and add a completion time
 | `bun run changelog:check` | Verify `CHANGELOG.md` is in sync (used by devcheck) |
 | `bun run bundle` | Build, pack, and clean a `.mcpb` for one-click Claude Desktop install |
 
+**CI is one file.** `.github/workflows/codeql.yml` (scaffolded) is the only GitHub Actions workflow: CodeQL is GitHub-owned end to end, and the file runs only while the repo's CodeQL *default setup* is turned off. Verification — `devcheck`, tests, the release gates — runs locally; don't add a workflow that re-runs it.
+
 ---
 
 ## Bundling

package/README.md

@@ -7,7 +7,7 @@
 
 <div align="center">
 
-[![Version](https://img.shields.io/badge/Version-0.1.13-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/noaa-spaceweather-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^2.0.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/noaa-spaceweather-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/noaa-spaceweather-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^7.0.2-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.4.0-blueviolet.svg?style=flat-square)](https://bun.sh/)
+[![Version](https://img.shields.io/badge/Version-0.2.0-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/noaa-spaceweather-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^2.0.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/noaa-spaceweather-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/noaa-spaceweather-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^7.0.2-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.4.0-blueviolet.svg?style=flat-square)](https://bun.sh/)
 
 </div>
 
@@ -35,21 +35,23 @@ Space weather from NOAA's Space Weather Prediction Center (SWPC) — geomagnetic
 
 | Tool | Description |
 |:-----|:------------|
-| `noaa_spaceweather_get_conditions` | Current space-weather snapshot: NOAA R/S/G storm scales, latest Kp, and a plain-language status summary |
+| `noaa_spaceweather_get_conditions` | Current space-weather snapshot: NOAA R/S/G storm scales, latest Kp, a plain-language status summary, and optionally SWPC's forecast discussion explaining the forecast |
 | `noaa_spaceweather_get_kp_index` | Planetary K-index (0–9) — recent observed 3-hour values with G-scale equivalents and aurora-latitude guidance, plus 3-day forecast |
 | `noaa_spaceweather_get_aurora_forecast` | OVATION model aurora forecast: global probability grid, optional local lookup by coordinates with go/no-go verdict |
-| `noaa_spaceweather_get_solar_wind` | Real-time solar wind from the active L1 spacecraft: speed, proton density, temperature, and the critical Bz component — explains why current geomagnetic conditions exist |
-| `noaa_spaceweather_get_solar_activity` | Solar flare picture: GOES X-ray flux, 3-day flare-class probabilities, active solar regions with per-region probabilities, and solar radiation storm level |
+| `noaa_spaceweather_get_solar_wind` | Real-time solar wind from the active L1 spacecraft: speed, proton density, temperature, and the critical Bz component with the window's most southward reading — explains why current geomagnetic conditions exist |
+| `noaa_spaceweather_get_solar_activity` | Solar flare picture: discrete flare events with peak class and R-scale level, GOES X-ray flux, the daily F10.7 cm radio flux, 3-day flare-class probabilities, active solar regions with per-region probabilities, and solar radiation storm level |
 | `noaa_spaceweather_get_alerts` | Active SWPC alerts, watches, and warnings — structured records with product type, severity, issue time, validity window, and full message text |
 
 ## Capability reference
 
 ### `noaa_spaceweather_get_conditions` <sub>tool</sub>
 
-- No inputs — a single call composing storm scales and current Kp into one snapshot
-- Returns today's R/S/G storm scales plus a 3-day forecast series
+- `include_discussion` (bool, default false) is the only input — otherwise a single call composing storm scales and current Kp into one snapshot
+- Returns today's observed R/S/G storm levels plus SWPC's 3-day forecast series, which starts with today
+- Forecast days carry what SWPC issues: a G level, and for R and S a probability — R1–R2, R3 or greater, S1 or greater — with no level. A null level means SWPC forecasts none for that day, which is not the same as level 0
 - Current Kp with G-scale equivalent and aurora-visibility latitude guidance
-- Data sourced from the `noaa-scales.json` + `noaa-planetary-k-index.json` feeds
+- With `include_discussion`, the forecaster-written Forecast Discussion split into its topic sections (Solar Activity, Energetic Particle, Solar Wind, Geospace), each with its 24-hour summary and 3-day forecast text
+- Data sourced from the `noaa-scales.json` + `noaa-planetary-k-index.json` feeds, plus the `discussion.txt` product when the discussion is requested
 
 ---
 
@@ -57,6 +59,7 @@ Space weather from NOAA's Space Weather Prediction Center (SWPC) — geomagnetic
 
 - `window_days` (1–7, default 1) bounds the observed series; the forecast series is always SWPC's full 3-day forecast
 - Each observed/forecast record carries Kp, G-scale equivalent, G-scale label, and aurora-latitude guidance
+- G levels follow SWPC's minus-third band floors — G1 starts at Kp 4.67 (5−), G4 runs through 8.67 (9−), and only Kp 9 is G5
 - Forecast excludes the feed's embedded historical "observed" entries — only forward-looking `estimated`/`predicted` rows
 - `observedCount` reports how many observed readings matched the window
 
@@ -65,7 +68,7 @@ Space weather from NOAA's Space Weather Prediction Center (SWPC) — geomagnetic
 ### `noaa_spaceweather_get_aurora_forecast` <sub>tool</sub>
 
 - Without coordinates: global metadata only — grid point count, global peak probability, peak region
-- With `latitude`/`longitude` (WGS84, required together): nearest 1°-grid lookup, minimum Kp needed at that latitude, and a plain-language go/no-go verdict
+- With `latitude`/`longitude` (WGS84, required together): nearest 1°-grid lookup, the centered-dipole geomagnetic latitude those coordinates convert to, the minimum Kp and G level needed at that geomagnetic latitude, and a plain-language go/no-go verdict
 - `invalid_coordinates` error when only one of the pair is supplied
 - OVATION model updates every ~5 minutes; forecast horizon is ~30–60 minutes ahead
 
@@ -74,8 +77,9 @@ Space weather from NOAA's Space Weather Prediction Center (SWPC) — geomagnetic
 ### `noaa_spaceweather_get_solar_wind` <sub>tool</sub>
 
 - `window_hours` (1–168, default 3) slices client-side from a feed that carries roughly the last 24 hours at ~1-minute cadence
+- `resolution` (`reduced` default, or `full`) bounds each returned series to 200 records: the window is bucketed by record count and one real measurement is emitted per bucket — the bucket's fastest speed for plasma, its most southward Bz for mag — with the newest record in the window always last. A series already inside the bound comes back untouched, so a default 3-hour call is unaffected; `full` returns every record (~1,400 per series over 24 hours)
 - Plasma (speed, density, temperature) and magnetic field (Bx/By/Bz/Bt GSM) returned as separate oldest-first series
-- `bzStatus` surfaces southward Bz (the storm driver) as a plain-language field
+- `bzStatus` surfaces southward Bz (the storm driver) as a plain-language field, and `bzMinInWindow` with its time tag reports the window's most southward reading — both computed from the full window, before any reduction
 - `latestFeedPlasmaTime`/`latestFeedMagTime`/`feedStalenessHours` distinguish an empty window from a stale feed
 - Every record names its reporting spacecraft — no satellite is assumed as "the" active one
 
@@ -84,18 +88,23 @@ Space weather from NOAA's Space Weather Prediction Center (SWPC) — geomagnetic
 ### `noaa_spaceweather_get_solar_activity` <sub>tool</sub>
 
 - `include_regions` (default true) toggles per-region active-solar-region detail to control response size
-- GOES X-ray flux (0.1–0.8 nm) with flare-class letter (A/B/C/M/X); recent readings cover the past hour
+- `flare_hours` (1–168, default 24) bounds the discrete flare events returned, filtered on each flare's onset; the feed keeps a rolling 7 days, so 168 returns everything it carries
+- Flare events come with the classes SWPC publishes — onset, peak, and decay, each with magnitude — the peak flux, and the NOAA R-scale level (0–5) that flux implies. Decay time and class are null while a flare is still in progress, and an empty window names the newest flare the feed holds
+- GOES X-ray flux (0.1–0.8 nm) with flare-class letter (A/B/C/M/X), the class with magnitude (`flareClassFull`, derived by SWPC's truncation rule so it agrees with the published flare classes), and the unformatted flux alongside the display string; recent readings cover the past hour
+- Daily F10.7 cm solar radio flux in sfu with its 90-day mean, from the Noon Penticton report — the value SWPC reports for the day. It can be up to ~24 h old, so its observation time rides with it
 - 3-day C/M/X flare-class and proton-event probabilities, each duplicated under a legacy `*1Day` name and a date-neutral name
 - Integral proton flux (≥10 MeV) drives the reported NOAA S-scale (0–5)
+- Data sourced from the `goes/primary/xrays-6-hour.json`, `goes/primary/xray-flares-7-day.json`, `f107_cm_flux.json`, `solar_probabilities.json`, `goes/primary/integral-protons-plot-3-day.json`, and `solar_regions.json` feeds
 
 ---
 
 ### `noaa_spaceweather_get_alerts` <sub>tool</sub>
 
-- `active_only` (default true) — in-force Warnings/Watches/Alerts only; cancellations and Summaries excluded
-- `max_age_hours` (1–720, default 48) bounds how far back to look; the SWPC feed itself has no expiry
-- Each record carries product type, NOAA scale + level (0 means "no scale stated," not zero severity), parsed validity window, and full message text
-- `cancelled` flags a record that cancels a prior product rather than being active
+- `active_only` (default true) — in-force Warnings/Watches/Alerts only. A product stays in force until the feed says otherwise, so this also drops any product a later cancellation names by serial, and all but the newest Watch carrying `THIS SUPERSEDES ANY/ALL PRIOR WATCHES IN EFFECT` — alongside cancellations, Summaries, and products whose validity end has passed
+- `max_age_hours` (1–720, default 48) bounds how far back to look for candidates; the SWPC feed itself has no expiry. Under `active_only=true` it does not cut off a product whose validity end is still ahead, so a multi-day Watch survives until the last day it forecasts a storm for ends; under `active_only=false` it is a literal age cutoff
+- Each record carries product type, NOAA scale + level (0 means "no scale stated," not zero severity), serial number, parsed validity window, and full message text
+- `cancelled` flags a record that cancels a prior product rather than being active; the product it cancels is a separate record, excluded by the serial link rather than by this flag
+- Under `active_only=true` the response echoes the applied window and counts what it excluded, by reason — so an empty result reads as "quiet" or "everything was filtered" without a second call
 
 ---
 
@@ -106,8 +115,8 @@ Built on [`@cyanheads/mcp-ts-core`](https://github.com/cyanheads/mcp-ts-core): s
 SWPC-specific:
 
 - All SWPC feeds are public and keyless — no API keys required
-- Single `SpaceWeatherService` wraps all six NOAA SWPC JSON feeds with `fetchWithTimeout` + `withRetry`
-- Heterogeneous feed normalization: interleaved multi-spacecraft records (solar wind), keyed objects (storm scales), coordinate triples (OVATION)
+- Single `SpaceWeatherService` wraps every NOAA SWPC feed — the JSON products and the plain-text forecast discussion — behind one `fetchWithTimeout` + `withRetry` funnel, so both paths classify an upstream failure the same way
+- Heterogeneous feed normalization: interleaved multi-spacecraft records (solar wind), keyed objects (storm scales), coordinate triples (OVATION), section-delimited text (forecast discussion)
 - NOAA scale interpretation: raw Kp 6 → "G2 moderate storm — aurora possible to ~55° geomagnetic latitude"
 - Feed freshness surfaced per-response: solar wind updates ~1 min, aurora ~5 min, Kp 3-hour intervals
 
@@ -116,7 +125,7 @@ Agent-friendly output:
 - Observed timestamps on every response so agents can reason about data freshness
 - Plain-language summaries and verdicts alongside raw values — agents can display or reason without re-interpreting indices
 - Bz component surfaced as a first-class field in solar wind output (southward Bz = primary storm driver)
-- Typed error contracts with recovery hints: `feed_unavailable` → "Retry in 30–60 s"
+- Typed error contracts with recovery hints, split on whether retrying can help: a transient feed failure is `feed_unavailable` → "Retry in 30–60 s"; a feed path SWPC no longer serves is `feed_moved` → "Retrying will not help", raised on the first attempt
 
 ---
 

package/changelog/0.1.x/0.1.14.md

@@ -0,0 +1,32 @@
+---
+summary: "Kp→G-scale thresholds follow SWPC thirds, aurora forecast converts to geomagnetic latitude, get_alerts correctly excludes cancelled/superseded Watches, feed failures carry a typed reason, DST-safe forecast dates, NaN token repair"
+breaking: false
+security: false
+---
+
+# 0.1.14 — 2026-09-17
+
+## Added
+
+- **`get_alerts` `serialNumber` field** on every record, plus an `activeOnly` echo of the request scope — resolves the `Cancel Serial Number:` / `Continuation of Serial Number:` chains in the message body. ([#29](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/29))
+- **`get_alerts` exclusion disclosure** — under `active_only=true`, enrichment fields `appliedWindowHours`, `appliedCutoff`, and per-reason `exclusions` counts report what was filtered, so an empty result reads as "quiet" or "everything was filtered" without a second call. ([#29](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/29))
+- **`get_aurora_forecast` `localLookup.geomagneticLatitude` and `minGScale`** — the centered-dipole geomagnetic latitude the requested coordinates convert to, and the NOAA G level backing `minKpRequired`. ([#28](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/28))
+- **`feed_moved` error reason**, declared on all six tools — a permanent 4xx (or the scales feed missing its `"0"` period) now fails in one attempt with a "retrying will not help" recovery hint, instead of retrying or surfacing an unclassified error. ([#30](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/30))
+
+## Changed
+
+- **`get_solar_activity` per-region flare-probability fields** (`cFlareProbability`, `mFlareProbability`, `xFlareProbability`, `protonProbability`) now state they cover the UTC day after `observedDate`, matching what SWPC's feed reports. ([#22](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/22))
+
+## Fixed
+
+- **`kpToGScale()` follows SWPC's minus-third band floors** (G1 at Kp 4.67, G2 5.67, G3 6.67, G4 7.67, G5 9.00) instead of whole-number cutoffs — `get_kp_index` and `get_conditions` no longer disagree with SWPC's own `noaa_scale`. ([#27](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/27))
+- **`get_aurora_forecast` converts geographic coordinates to geomagnetic latitude** before the Kp lookup and wraps longitude at the antimeridian in the nearest-grid-point search — Denver and San Francisco no longer read "aurora not visible" during a storm. Shares one latitude-band table with `gScaleToAuroraLatitude()`. ([#28](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/28))
+- **`get_alerts` `active_only=true`** now drops a product named by a later cancellation's `Cancel Serial Number:` and all but the newest Watch carrying the supersede line, and keeps a Watch active past `max_age_hours` while a day it forecasts a storm for is still running. The empty-state text no longer claims "no active alerts" for an unfiltered request. ([#29](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/29))
+- **Feed failures carry a declared reason and recovery hint on the wire** — every SWPC feed error now reaches the client as `feed_unavailable` or `feed_moved` with `data.reason`, `data.recovery.hint`, and a `Recovery:` line in `content[]`. ([#30](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/30))
+- **`get_solar_activity` forecast dates use UTC epoch arithmetic** instead of local-calendar `setDate`/`getDate` — a 3-day window crossing a DST transition in the process timezone no longer duplicates a forecast day or drifts off midnight UTC. ([#22](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/22))
+- **A bare `NaN`/`Infinity` token in any SWPC feed body is repaired to `null`** before the retry loop, instead of failing the parse and burning all four retry attempts on bytes that will never parse differently. ([#25](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/25))
+
+## Dependencies
+
+- `@cyanheads/mcp-ts-core` `^0.13.2` → `^0.13.3`
+- `zod` `^4.6.4` → `^4.6.5`

package/changelog/0.2.x/0.2.0.md

@@ -0,0 +1,21 @@
+---
+summary: "Forecast R/S probabilities replace a phantom scale 0, discrete flare history and F10.7 flux, solar wind series bounded to 200 records, and an optional SWPC forecast discussion."
+breaking: true
+security: false
+---
+
+# 0.2.0 — 2026-09-17
+
+## Added
+
+- **`get_solar_wind`:** `resolution` input (`reduced`/`full`, default `reduced`) bounds `plasma`/`mag` to 200 records each — one real measurement per bucket (fastest speed for plasma, most southward Bz for mag), newest record always last. A default 3-hour call is unaffected; a 24-hour call drops from ~541 KB to roughly the size of today's default call (~68 KB). Adds `bzMinInWindow` + `bzMinTimeTag`, computed from the full window before reduction. [#24](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/24)
+- **`get_solar_activity`:** `recentFlares[]` — discrete GOES flare events from `xray-flares-7-day.json`, filtered by the new `flare_hours` input (1–168, default 24), with peak class, R-scale level, and begin/max/end times and classes. [#31](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/31)
+- **`get_solar_activity`:** `f107` — the latest daily F10.7 cm solar radio flux (the Noon Penticton report, matching SWPC's own daily summary), with its 90-day mean when available. [#31](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/31)
+- **`get_solar_activity`:** `XraySchema` gains `flareClassFull` (class with magnitude, e.g. `"M5.2"`, truncated to match SWPC's own rounding) and `fluxWm2Value` (unformatted flux, for comparison without parsing `fluxWm2`). [#31](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/31)
+- **`get_conditions`:** `include_discussion` input + `discussion` output — SWPC's forecaster-written Forecast Discussion, parsed into per-topic sections (summary/forecast text). [#32](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/32)
+
+## Changed
+
+- **Breaking:** `get_conditions.forecast[].R`/`.S` no longer coerce SWPC's null forecast scale to `0`. Forecast days now carry a nullable `scale`/`text`/`label` plus probability fields — `minorProbPercent`/`majorProbPercent` for R, `probPercent` for S — since SWPC issues a probability, not a level, for future days. `today` and `forecast[].G` are unaffected. [#23](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/23)
+- **Breaking:** `get_conditions.observedAt` is now ISO 8601 UTC (`"2026-09-17T17:15:00Z"`) instead of the space-separated `"2026-09-17 17:15:00"`. [#23](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/23)
+- `get_solar_activity`'s X-ray flux feed swapped from `xrays-7-day.json` to `xrays-6-hour.json` — byte-identical records for the tool's past-hour slice, ~4.52 MB → ~162 KB per call. [#31](https://github.com/cyanheads/noaa-spaceweather-mcp-server/issues/31)

package/dist/mcp-server/tools/definitions/get-alerts.tool.d.ts

@@ -21,6 +21,7 @@ export declare const getAlerts: import("@cyanheads/mcp-ts-core").ToolDefinition<
         level: z.ZodNumber;
         noaaScale: z.ZodNullable<z.ZodString>;
         cancelled: z.ZodBoolean;
+        serialNumber: z.ZodNullable<z.ZodString>;
         phenomenon: z.ZodString;
         issueDatetime: z.ZodString;
         validFrom: z.ZodNullable<z.ZodString>;
@@ -28,14 +29,31 @@ export declare const getAlerts: import("@cyanheads/mcp-ts-core").ToolDefinition<
         message: z.ZodString;
     }, z.core.$strip>>;
     totalCount: z.ZodNumber;
+    activeOnly: z.ZodBoolean;
     fetchedAt: z.ZodString;
 }, z.core.$strip>, readonly [{
     readonly reason: "feed_unavailable";
     readonly code: JsonRpcErrorCode.ServiceUnavailable;
-    readonly when: "SWPC endpoint returns non-OK status or times out after retries.";
+    readonly when: "SWPC feed returns 5xx or 429, times out, or answers with a body that is not parseable JSON. Retried before failing.";
     readonly retryable: true;
     readonly recovery: "Retry in 30–60 seconds; SWPC feeds occasionally lag during high-activity events.";
+}, {
+    readonly reason: "feed_moved";
+    readonly code: JsonRpcErrorCode.ServiceUnavailable;
+    readonly when: "SWPC feed path returns a permanent 4xx (404, 410, 401, 403). Fails in one attempt.";
+    readonly retryable: false;
+    readonly recovery: "Retrying will not help — the SWPC feed path no longer resolves or no longer has the expected shape; the feed URL needs updating against SWPC current inventory.";
 }], {
     readonly notice: z.ZodOptional<z.ZodString>;
+    readonly appliedWindowHours: z.ZodOptional<z.ZodNumber>;
+    readonly appliedCutoff: z.ZodOptional<z.ZodString>;
+    readonly exclusions: z.ZodOptional<z.ZodObject<{
+        agedOut: z.ZodNumber;
+        productType: z.ZodNumber;
+        cancellationRecord: z.ZodNumber;
+        cancelledBySerial: z.ZodNumber;
+        superseded: z.ZodNumber;
+        validityElapsed: z.ZodNumber;
+    }, z.core.$strip>>;
 }>;
 //# sourceMappingURL=get-alerts.tool.d.ts.map

package/dist/mcp-server/tools/definitions/get-alerts.tool.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"get-alerts.tool.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/tools/definitions/get-alerts.tool.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAQ,CAAC,EAAE,MAAM,wBAAwB,CAAC;AACjD,OAAO,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AAwDjE,eAAO,MAAM,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA4IpB,CAAC"}
+{"version":3,"file":"get-alerts.tool.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/tools/definitions/get-alerts.tool.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAQ,CAAC,EAAE,MAAM,wBAAwB,CAAC;AACjD,OAAO,EAAE,gBAAgB,EAAE,MAAM,+BAA+B,CAAC;AA+NjE,eAAO,MAAM,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAqPpB,CAAC"}