---
summary: "nws_search_alerts gains an optional limit input and validates point/zone locally before the upstream call; nws_get_observations classifies a nonexistent station as station_not_found instead of a raced no_observations"
breaking: false
security: false
---

# 0.7.0 — 2026-06-30

## Added

- **`limit` on `nws_search_alerts`** — optional `z.number().int().min(1).max(25).default(25)` input that slices the returned alerts client-side; `totalCount` still reports the full match count before the limit, so a small `limit` returns a digest of a broad or national search without dropping the total. Not sent to `/alerts/active` and excluded from the applied-filters echo. ([#21](https://github.com/cyanheads/nws-weather-mcp-server/issues/21))

## Fixed

- **`nws_search_alerts` point/zone validation** — `point` is matched against the strict NWS coordinate pattern `^(-?\d+(?:\.\d+)?),(-?\d+(?:\.\d+)?)$` locally, replacing a `.split(',').map(Number)` check where `Number("")` → 0 let `"47.6,"` and whitespace-padded segments reach a raw upstream 400; internal whitespace is stripped first so `"47.6, -122.3"` salvages to the accepted `"47.6,-122.3"`. `zone` is upper-cased (matching `area` and `nws_get_zone_forecast`) so `"waz315"` no longer trips the upstream zone-code regex. Malformed points fail locally as `invalid_point`. ([#20](https://github.com/cyanheads/nws-weather-mcp-server/issues/20))
- **`nws_get_observations` station classification** — the direct-station path runs `/stations/{id}` and `/stations/{id}/observations/latest` under `Promise.allSettled` instead of `Promise.all`, throwing the station-metadata rejection first. A nonexistent station returns `station_not_found` even when the observations leg also 404s, instead of the observations leg winning the race and masking it as `no_observations`. Fetches stay parallel. ([#19](https://github.com/cyanheads/nws-weather-mcp-server/issues/19))

## Dependencies

- `@biomejs/biome` `^2.5.0 → ^2.5.1`
- `@types/node` `^26.0.0 → ^26.0.1`
