io.github.cyanheads/nws-weather-mcp-server
REMOTE · NWS.CASEYJHAND.COM · 2 COMPONENTS
Get US weather forecasts, active alerts, and current observations.
Available components
Last scanned (3 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Maps and Location
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3470 tokens (~289/item across 12 items; 10 tools + 2 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 28 Oct 26 0
- New resource “nws-weather-guide” functional
- Server version: 0.11.2 → 0.12.0 functional
- 24 Oct 26 0
- Server version: 0.11.1 → 0.11.2 functional
- “nws_get_forecast” added an optional parameter “include_amounts” cosmetic
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nws_get_office_discussion” rewrote its description, which is the text the model reads security
- Tool “nws_get_zone_forecast” rewrote its description, which is the text the model reads security
- Server version: 0.11.0 → 0.11.1 functional
- “nws_search_alerts” reworded the description of “cursor” cosmetic
- “nws_get_office_discussion” reworded the description of “product_type” cosmetic
- “nws_get_office_discussion” reworded the description of “sections” cosmetic
- “nws_get_forecast” reworded the description of “cursor” cosmetic
- “nws_get_forecast” reworded the description of “hourly” cosmetic
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nws_get_zone_forecast” rewrote its description, which is the text the model reads security
- Tool “nws_get_office_discussion” rewrote its description, which is the text the model reads security
- Schema quality: 237 → 278 ▼ functional
- Server version: 0.10.0 → 0.11.0 functional
- New tool “nws_get_alert” functional
- “nws_get_office_discussion” added an optional parameter “sections” cosmetic
- “nws_search_alerts” reworded the description of “limit” cosmetic
- “nws_get_zone_forecast” reworded the description of “zone_id” cosmetic
- “nws_get_office_discussion” reworded the description of “office” cosmetic
- “nws_get_observation_history” reworded the description of “limit” cosmetic
- “nws_get_observation_history” reworded the description of “cursor” cosmetic
- “nws_find_stations” reworded the description of “limit” cosmetic
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1835 → 2375 ▼ functional
- Server version: 0.9.5 → 0.10.0 functional
- New tool “nws_get_observation_history” functional
- New tool “nws_get_alert_counts” functional
- 28 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
- 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
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 6 Nov 2026 · Probed https://nws.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 | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 995a30681ab772540e934241ca1d576c |
| 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 nws.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| caseyjhand.com. | DS published | 2371 | 13 | Verified |
| nws.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://nws.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://nws.caseyjhand.com/mcp | HTTPS enforced | 301 | https://nws.caseyjhand.com/mcp |
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 →
nws_find_stations Nws Find Stations ~204
Find weather observation stations near a location. Returns stations sorted by proximity with distance and bearing. Use to discover station IDs for nws_get_observations.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque continuation token from a previous response's nextCursor. Omit for the first page. The token carries its own page size, so limit applies to the first page only. Every call re-fetches the stati… |
| latitude | number | yes | Center latitude for proximity search. |
| limit | integer | – | Max stations per page. A page holds at most 50; a larger limit (up to 10000) is served as 50 and reported through requestedLimit and effectiveLimit. totalCount still reports every station near the po… |
| longitude | number | yes | Center longitude for proximity search. |
| Name | Type | Req | Description |
|---|---|---|---|
| effectiveLimit | number | – | The page size applied instead of requestedLimit; continued pages keep it. Absent when the limit was within the cap. |
| error | object | – | Present when the call failed. Absent on success. |
| nextCursor | string | – | Opaque token for the next page of stations — pass it back as `cursor`. Omitted when this is the last page. |
| notice | string | – | Guidance when the requested limit exceeded the page cap, when no stations were found near the requested coordinates, when stations remain beyond this page, or when the supplied cursor points past the… |
| requestedLimit | number | – | The limit asked for, when it exceeded the 50-station page cap; absent otherwise. |
| shown | number | – | Number of stations returned in this page |
| stations | array | – | Nearby stations sorted by distance |
| totalCount | number | – | Total observation stations available near this location before the page limit was applied — NOT the number returned in this page, which is shown. Same value on every page of one query; compare it aga… |
No examples provided.
nws_get_alert Nws Get Alert ~237
Fetch one NWS alert message by ID — a current alert, or an earlier message that an update or cancellation has since superseded and that an active-alert search no longer returns. Takes an id from nws_search_alerts or a references[].identifier from any alert, and returns the same alert fields nws_search_alerts does. The message carries its own references, newest first, so a revision chain is walked one call per message. Every reference sharing the newest sent time is an immediate predecessor (an update can merge several earlier segments), so references[0] is one of them, not always the only one. NWS serves messages for about 7 days after they are sent.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | NWS alert message ID, e.g. "urn:oid:2.49.0.1.840.0.654087301e4bfcbe71d24494c26a965e54d3a1ad.001.1": the id of an alert from nws_search_alerts, or the identifier of one of its references. Pass it exac… |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | Single alert message with event, severity, area, and timing |
| error | object | – | Present when the call failed. Absent on success. |
No examples provided.
nws_get_alert_counts Nws Get Alert Counts ~149
Count active weather alerts nationwide, per state/territory or marine area, and per marine region, in one small response — the answer to "how many alerts are active, and where" without fetching the alerts themselves. Counts cover every message status, Test and Exercise included, so totalAlerts can run above the totalCount a national nws_search_alerts search reports under its default status of Actual. An alert counts once in each area its zones fall in, so the area counts can sum past totalAlerts; landAlerts plus marineAlerts equals totalAlerts. Takes no filters. For counts per zone or under a filter, call nws_search_alerts with that zone or filter and read its totalCount.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | object | – | Active alert counts keyed by state/territory code (e.g., "WA", "PR") or marine area code (e.g., "PZ", "GM"). Only areas with an active alert appear. An alert counts once in each area its zones fall i… |
| error | object | – | Present when the call failed. Absent on success. |
| landAlerts | number | – | Active alerts affecting land zones. |
| marineAlerts | number | – | Active alerts affecting marine zones. landAlerts + marineAlerts = totalAlerts. |
| regions | object | – | Active marine alert counts keyed by marine region: "AL" (Alaska waters), "AT" (Atlantic Ocean), "GL" (Great Lakes), "GM" (Gulf of Mexico), "PA" (Eastern Pacific and US West Coast), "PI" (Central and… |
| totalAlerts | number | – | Active alerts nationwide across every message status (Actual, Exercise, System, Test, Draft). Can exceed the totalCount of a national nws_search_alerts search, which counts status Actual by default. |
No examples provided.
nws_get_forecast Nws Get Forecast ~307
Get the weather forecast for a US location. Returns either named 12-hour periods (default) or hourly breakdowns.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque continuation token from a previous response's nextCursor, to retrieve the next 48 periods. Omit for the first page. The token carries the mode it was issued in (hourly or 7-day), so the next p… |
| hourly | boolean | – | If true, returns hourly forecast (48 one-hour periods per page, ~156 available) instead of 12-hour named periods (14 periods). Hourly includes dewpoint and relative humidity. Sets the mode of the fir… |
| include_amounts | boolean | – | Include every native quantitativePrecipitation, snowfallAmount, and iceAccumulation interval from the NWS grid. Applies to this call only, including cursor pages; units and interval strings remain as… |
| latitude | number | yes | Latitude in decimal degrees (e.g., 47.6062). |
| longitude | number | yes | Longitude in decimal degrees (e.g., -122.3321). |
| Name | Type | Req | Description |
|---|---|---|---|
| amountsUpdateTime | string|null | – | Native grid updateTime, distinct from forecast updateTime; null when omitted upstream and absent when amounts were not fetched |
| error | object | – | Present when the call failed. Absent on success. |
| generatedAt | string | – | When NWS generated this response (ISO 8601). It advances whenever NWS regenerates the response, even when the underlying data is unchanged; see updateTime for the data age. |
| location | object | – | Resolved location metadata |
| mode | string | – | Forecast mode: "hourly" or "7-day" |
| nextCursor | string | – | Opaque token for the next page of periods — pass it back as `cursor`; it carries this forecast mode (hourly or 7-day). Omitted when this is the last page. |
| notice | string | – | Guidance when forecast data was last updated more than 24 hours ago, periods remain or the cursor points past the end, or requested amount data or layers are unavailable. |
| periods | array | – | Forecast periods |
| precipitationAmounts | array | – | Present grid amount layers when requested and fetched successfully; missing layers are named in notice |
| shown | number | – | Number of forecast periods in this page (at most 48). |
| totalCount | number | – | Total forecast periods available upstream before the page window was applied — NOT the number in this page, which is shown. Compare it against shown to tell whether periods were withheld. |
| updateTime | string|null | – | When the data this forecast was generated from was last updated (ISO 8601, as NWS sends it). A grid that stops updating keeps this time while generatedAt keeps advancing. Null when NWS omits it. |
No examples provided.
nws_get_observation_history Nws Get Observation History ~408
Get a station's recent observation history, newest first — the trend behind the single latest reading nws_get_observations returns (is pressure falling, is the wind picking up). NWS keeps about the last 7 days per station, and a busy airport station reports as often as every 5 minutes, so a day can run past 100 observations: narrow with start (inclusive) and end (exclusive), and page back to older observations with nextCursor. Takes a station ID; use nws_find_stations to find one near a coordinate.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque continuation token from a previous response's nextCursor. Omit for the first page. It carries that query's start, end, and applied limit, so those inputs apply to the first page only. Each pag… |
| end | string | – | Time to stop before (exclusive), in the same format as start. Omit to start from the most recent observation. |
| limit | integer | – | Observations per page, newest first. A page holds at most 100; a larger limit (up to 10000) is served as 100 and reported through requestedLimit and effectiveLimit. When older observations remain in… |
| start | string | – | Earliest observation time to include (inclusive), as an ISO 8601 date-time with seconds and an offset (e.g., "2026-09-30T00:00:00Z" or "2026-09-29T17:00:00-07:00"). Omit to reach back as far as NWS k… |
| station_id | string | yes | Observation station ID (e.g., "KSEA"), case-insensitive. Use nws_find_stations to discover station IDs near a coordinate. |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | The page limit this page holds, when truncated is true |
| effectiveLimit | number | – | The page size applied instead of requestedLimit; continued pages keep it. Absent when the limit was within the cap. |
| error | object | – | Present when the call failed. Absent on success. |
| nextCursor | string | – | Opaque token for the next, older page — pass it back as cursor. Present only when older observations remain in the window; omitted on the last page. |
| notice | string | – | Guidance when the requested limit exceeded the page cap, when the window held no observations (NWS keeps about the last 7 days), or when older observations remain beyond this page. |
| observations | array | – | Observations in the window, newest first |
| requestedLimit | number | – | The limit asked for, when it exceeded the 100-observation page cap; absent otherwise. |
| shown | number | – | Number of observations returned in this page |
| stationId | string | – | Observation station ID, uppercased |
| stationName | string | – | Station name |
| timeZone | string|null | – | Station time zone when known |
| truncated | boolean | – | True when older observations remain in the window past this page; continue with nextCursor. |
No examples provided.
nws_get_observations Nws Get Observations ~123
Get current weather observations (actual measured conditions). Accepts coordinates (resolves nearest station automatically) or a station ID directly (e.g., "KSEA").
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | – | Latitude for automatic station resolution. Use with longitude. Ignored if station_id is provided. |
| longitude | number | – | Longitude for automatic station resolution. Use with latitude. Ignored if station_id is provided. |
| station_id | string | – | Station identifier directly (e.g., "KSEA", "KORD"). Use nws_find_stations to discover station IDs. |
| Name | Type | Req | Description |
|---|---|---|---|
| barometricPressurePa | number|null | – | Barometric pressure in Pascals |
| cloudLayers | array | – | Cloud layer information |
| dewpointC | number|null | – | Dewpoint in Celsius, to one decimal |
| error | object | – | Present when the call failed. Absent on success. |
| heatIndexC | number|null | – | Heat index in Celsius, to one decimal |
| notice | string | – | Guidance when the latest observation is more than 2 hours old or most measurements are unavailable from this station. |
| observedAt | string | – | Observation timestamp (ISO 8601) |
| precipitationLast3HoursMm | number|null | – | Precipitation in the past 3 hours in mm, to 0.1 mm, carried by the hourly reports nearest 03, 09, 15, and 21 UTC. 0 is a trace (under 0.01 in); null means no amount was reported. |
| precipitationLast6HoursMm | number|null | – | Precipitation in the past 6 hours in mm, to 0.1 mm, carried by the hourly reports nearest 00, 06, 12, and 18 UTC. 0 is a trace (under 0.01 in); null means no amount was reported. |
| precipitationLastHourMm | number|null | – | Precipitation in the past hour in mm, to 0.1 mm. 0 is a trace (under 0.01 in), not a dry hour; null means no amount was reported, the usual value for a dry hour and on 5-minute reports. |
| relativeHumidityPct | number|null | – | Relative humidity in percent (0-100) |
| station | string | – | Station ID that served the observation (e.g., "KSEA") |
| stationId | string | – | Observation station ID |
| stationName | string | – | Station name |
| temperatureC | number|null | – | Temperature in Celsius, to one decimal (e.g., 8.3) |
| textDescription | string | – | Conditions summary (e.g., "Mostly Cloudy") |
| timeZone | string|null | – | Station time zone when known |
| timestamp | string | – | Observation time (ISO 8601) |
| visibilityM | number|null | – | Visibility in meters |
| windChillC | number|null | – | Wind chill in Celsius, to one decimal |
| windDirectionDeg | number|null | – | Wind direction in degrees (0-360) |
| windGustKmh | number|null | – | Wind gust in km/h |
| windSpeedKmh | number|null | – | Wind speed in km/h |
No examples provided.
nws_get_office_discussion Nws Get Office Discussion ~650
Get the latest narrative forecast product from a Weather Forecast Office (WFO). The default product is AFD (Area Forecast Discussion), which explains the meteorological reasoning behind the forecast — synoptic setup, model guidance, and forecaster confidence. Other types: HWO (Hazardous Weather Outlook, 1-7 day severe/flood/winter outlook), ZFP (Zone Forecast Product, zone-by-zone text), SPS (Special Weather Statement, short-fuse advisory), FWF (Fire Weather Planning Forecast, one segment per fire weather zone). The office code is the 3-letter WFO identifier returned as the "office" field by nws_get_forecast. A product over 24,000 bytes (most ZFPs and FWFs) comes back as an outline of its sections — AFD section names, or ZFP/HWO/SPS/FWF zone segments with their area names — with each section's size, instead of the text; re-call with sections to get the ones you need. sections also works on a product of any size, to read one AFD section or one zone's forecast. For an alert zone typed "fire" (Red Flag Warning, Fire Weather Watch), pass the alert's "office" field as office, product_type "FWF", and the zone code in sections.
| Name | Type | Req | Description |
|---|---|---|---|
| office | string | yes | Product location code of 2–3 letters or digits, case-insensitive — usually the 3-letter Weather Forecast Office (WFO) code (e.g., "SEW" for Seattle, "LOX" for Los Angeles), returned as the "office" f… |
| product_type | string | – | Product type code. AFD (Area Forecast Discussion) — meteorological reasoning, model analysis, forecaster confidence. HWO (Hazardous Weather Outlook) — 1-7 day outlook for severe weather, flooding, wi… |
| sections | array | – | Sections to return instead of the whole product: AFD section names, case-insensitive (e.g., "DISCUSSION", "AVIATION"), or zone codes for ZFP/HWO/SPS/FWF (e.g., "WAZ315"; a code inside a listed range… |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| issuanceTime | string | – | When the product was issued (ISO 8601), e.g., "2026-05-30T10:33:00+00:00". |
| issuingOffice | string | – | Issuing office call sign (e.g., "KSEW"). Includes the K/P prefix, unlike the input office code. |
| notice | string | – | Set when the product is outlined (with a worked sections re-call) or when sections selected part of it (how many of how many sections came back). |
| outline | array | – | Sections of a product too large to inline, largest first. Present only in place of productText. |
| productCode | string | – | Product type code (e.g., "AFD"). |
| productName | string | – | Full product name (e.g., "Area Forecast Discussion"). |
| productText | string | – | Narrative product text as issued by the forecaster: the whole product, or the product header followed by each selected section when sections was given. Absent when outline is returned. |
| wmoCollectiveId | string | – | WMO collective identifier (e.g., "FXUS66"). Identifies the product family in international message routing. |
No examples provided.
nws_get_zone_forecast Nws Get Zone Forecast ~380
Get the text forecast for an NWS forecast zone. Returns named forecast periods (e.g., "Today", "Tonight", "Monday") with detailed narrative text — the human-readable, zone-level forecast written by local forecasters. Completes the alert-to-forecast chain: nws_search_alerts returns each affected zone in "affectedZones" as a code plus a type, and nws_find_stations returns codes in the "forecastZone" column. Only affectedZones entries with type "forecast" work here; entries typed "county" have no text forecast upstream and will not resolve. An entry typed "fire" has its forecast in a segment of the office's Fire Weather Planning Forecast: call nws_get_office_discussion with office set to the alert's "office" field, product_type "FWF", and sections set to the zone code; a fire zone code that is also a public zone code (e.g., "NDZ040") returns that public zone's forecast here, not the fire weather forecast. Marine forecast zones vary: many coastal zones serve a text forecast of wind and seas (e.g., "PZZ251"), while offshore zones (e.g., "GMZ056") and some coastal ones have none. Zone codes follow the pattern XXZ### (e.g., "WAZ315" for the City of Seattle).
| Name | Type | Req | Description |
|---|---|---|---|
| zone_id | string | yes | NWS forecast zone code (e.g., "WAZ315" for the City of Seattle, or a marine zone such as "PZZ251"). Returned as "forecastZone" by nws_get_forecast and nws_find_stations, or as the "code" of an "affec… |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| periodCount | number | – | Number of forecast periods returned. |
| periods | array | – | Forecast periods in chronological order, typically covering 7 days. |
| updated | string | – | When the zone forecast was last updated (ISO 8601 with timezone offset). |
| zoneId | string | – | Zone ID, uppercased (e.g., "WAZ315" for input "waz315"). |
No examples provided.
nws_list_alert_types Nws List Alert Types ~45
List all valid NWS alert event type names. Use to discover valid values for the event filter in nws_search_alerts, or to browse alert categories. No parameters required.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of event types |
| error | object | – | Present when the call failed. Absent on success. |
| eventTypes | array | – | Alert event type names sorted alphabetically |
No examples provided.
nws_search_alerts Nws Search Alerts ~633
Search active weather alerts (watches, warnings, advisories) across the US. Filter by state, coordinates, zone, land/marine region, event type, severity, urgency, or certainty. area, point, zone, region_type, and region are mutually exclusive — provide at most one. Omit all filters for a national search.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | US state/territory code (e.g., "WA", "OK", "PR") or marine area code (e.g., "GM"). Mutually exclusive with point and zone. |
| certainty | array | – | Filter by certainty level. |
| cursor | string | – | Opaque continuation token from a previous response's nextCursor; send it on its own. Omit for the first page. It carries that query's filters and page size, so the filter inputs and limit apply to th… |
| event | array | – | Filter to specific event types (e.g., ["Tornado Warning"]). Matches are case-insensitive and partial, so "tornado" matches both "Tornado Warning" and "Tornado Watch". Use nws_list_alert_types to disc… |
| limit | integer | – | Maximum number of alerts to include in this page (default 25). A page holds at most 25; a larger limit (up to 10000) is served as 25 and reported through requestedLimit and effectiveLimit. totalCount… |
| point | string | – | Coordinates as "lat,lon" (e.g., "47.6,-122.3"). Returns alerts whose geometry contains this point. Mutually exclusive with area and zone. |
| region | array | – | Restrict to NWS marine region groups: "AL" (Alaska waters), "AT" (Atlantic Ocean), "GL" (Great Lakes), "GM" (Gulf of Mexico), "PA" (Eastern Pacific and US West Coast), "PI" (Central and Western Pacif… |
| region_type | string | – | Restrict to land-based or marine alerts. Mutually exclusive with area, point, zone, and region. |
| severity | array | – | Filter by severity level. |
| status | string | – | Alert status filter. Default "Actual". Use a different value only when you specifically need non-live alerts. |
| urgency | array | – | Filter by urgency level. |
| zone | string | – | NWS forecast zone (e.g., "WAZ558") or county zone (e.g., "WAC033"). Mutually exclusive with area and point. |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | – | Matching alerts for this page (at most the applied limit, which never exceeds 25) |
| appliedFilters | string | – | Summary of applied search filters |
| effectiveLimit | number | – | The page size applied instead of requestedLimit; continued pages keep it. Absent when the limit was within the cap. |
| error | object | – | Present when the call failed. Absent on success. |
| nextCursor | string | – | Opaque token for the next page of matches — pass it back as `cursor` on its own; it carries this query's filters and page size. Omitted when this is the last page. |
| notice | string | – | Guidance when the requested limit exceeded the page cap, when no alerts matched (echoes applied filters and suggests how to broaden), when matches remain beyond this page, or when the supplied cursor… |
| requestedLimit | number | – | The limit asked for, when it exceeded the 25-alert page cap; absent otherwise. |
| shown | number | – | Number of alerts included in this response |
| totalCount | number | – | Total distinct alerts matching the filters in this fetch, before the page window is applied. NWS repeats some alerts verbatim within one response; the copies are collapsed on id, so this counts each… |
No examples provided.
How do I install the io.github.cyanheads/nws-weather-mcp-server server?
io.github.cyanheads/nws-weather-mcp-server is a hosted endpoint at https://nws.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 · nws.caseyjhand.com
claude mcp add --transport http cyanheads-nws-weather-mcp-server 'https://nws.caseyjhand.com/mcp'
What is the io.github.cyanheads/nws-weather-mcp-server server?
io.github.cyanheads/nws-weather-mcp-server is listed in the public MCP registry as io.github.cyanheads/nws-weather-mcp-server. Get US weather forecasts, active alerts, and current observations. This page covers its hosted endpoint (https://nws.caseyjhand.com/mcp).
Is the io.github.cyanheads/nws-weather-mcp-server server safe to use?
io.github.cyanheads/nws-weather-mcp-server scores 89 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/nws-weather-mcp-server server expose?
io.github.cyanheads/nws-weather-mcp-server exposes 10 tools: nws_get_forecast, nws_search_alerts, nws_get_alert, nws_get_alert_counts, nws_get_observations, and 5 more. Their descriptions and schemas cost roughly 3,136 tokens of context every time the server is loaded.
Does the io.github.cyanheads/nws-weather-mcp-server server require authentication?
No. We connected to io.github.cyanheads/nws-weather-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/nws-weather-mcp-server server still maintained?
io.github.cyanheads/nws-weather-mcp-server is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.cyanheads/nws-weather-mcp-server server?
VerifyMCP ran 13 checks on io.github.cyanheads/nws-weather-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.