---
summary: "nws_get_forecast, nws_find_stations, and nws_search_alerts take a cursor input and return nextCursor, reaching results past each tool's page cap instead of dropping them"
breaking: false
security: false
---

# 0.7.4 — 2026-08-12

All three re-fetch their full collection on every call and cache nothing but `/points` grid resolution, so pages are contiguous within one response but not guaranteed across separate calls — most consequential for `nws_search_alerts`, whose active-alert set changes continuously.

## Fixed

- **`nws_get_forecast` hourly periods past the 48-cap** — a `cursor` input and `nextCursor` enrichment field, built on `paginateArray`, reach the periods beyond the first page instead of leaving them unretrievable. ([#27](https://github.com/cyanheads/nws-weather-mcp-server/issues/27))
- **`nws_find_stations` results past the 50-cap** — same mechanism; `NwsService.findStations` dropped its `limit` parameter and now returns the complete distance-sorted set so the tool can window it. ([#28](https://github.com/cyanheads/nws-weather-mcp-server/issues/28))
- **`nws_search_alerts` matches past the 25-cap** — same mechanism, windowing the full filtered set fetched from `/alerts/active` (which accepts no upstream `limit` or cursor). ([#29](https://github.com/cyanheads/nws-weather-mcp-server/issues/29))
