io.github.cyanheads/nws-weather-mcp-server
REMOTE · NWS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21
Get US weather forecasts, active alerts, and current observations.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability79
- 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 1793 tokens (~224/item across 8 items; 7 tools + 1 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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'
{
"mcpServers": {
"cyanheads-nws-weather-mcp-server": {
"url": "https://nws.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-nws-weather-mcp-server": {
"type": "http",
"url": "https://nws.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-nws-weather-mcp-server] url = "https://nws.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-nws-weather-mcp-server": {
"type": "remote",
"url": "https://nws.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-nws-weather-mcp-server --url 'https://nws.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-nws-weather-mcp-server:
url: "https://nws.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-nws-weather-mcp-server": {
"Transport": "http",
"Url": "https://nws.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-nws-weather-mcp-server -t streamable-http -u 'https://nws.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-nws-weather-mcp-server": {
"type": "http",
"url": "https://nws.caseyjhand.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 0
- Server version: 0.9.3 → 0.9.4 functional
- 13 Sept 26 0
- Server version: 0.9.2 → 0.9.3 functional
- “nws_search_alerts” reworded the description of “cursor” cosmetic
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 −1
- Stability: pass → 0.93 functional
- 4 Sept 26 0
- Server version: 0.9.1 → 0.9.2 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.9.0 → 0.9.1 functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 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 | 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 nws.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 |
| 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 ~176
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 (1-50). totalCount still reports every station near the point, so pass the returned nextCursor as cursor to reach the rest. |
| longitude | number | yes | Center longitude for proximity search. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 no stations were found near the requested coordinates, when stations remain beyond this page, or when the supplied cursor points past the end of the list. |
| 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_forecast Nws Get Forecast ~188
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. Every call re-fetches the forecast, so consecutive periods are contiguous wi… |
| 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. |
| 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 |
|---|---|---|---|
| error | object | – | Present when the call failed. Absent on success. |
| generatedAt | string | – | When the forecast was generated (ISO 8601) |
| 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`. Omitted when this is the last page. |
| notice | string | – | Set when periods remain beyond this page, or when the supplied cursor points past the end of the period array. |
| periods | array | – | Forecast periods |
| 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. |
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 |
| error | object | – | Present when the call failed. Absent on success. |
| heatIndexC | number|null | – | Heat index in Celsius |
| notice | string | – | Guidance when the latest observation is more than 2 hours old — data may not reflect current conditions. |
| observedAt | string | – | Observation timestamp (ISO 8601) |
| 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 |
| 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 |
| 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 ~267
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). The office code is the 3-letter WFO identifier returned as the "office" field by nws_get_forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| office | string | yes | Three-letter Weather Forecast Office (WFO) code (e.g., "SEW" for Seattle, "LOX" for Los Angeles). Returned as the "office" field in nws_get_forecast output. |
| 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… |
| 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. |
| productCode | string | – | Product type code (e.g., "AFD"). |
| productName | string | – | Full product name (e.g., "Area Forecast Discussion"). |
| productText | string | – | Full narrative product text as issued by the forecaster. AFDs are typically 1,000-3,000 words covering synoptic setup, model guidance, and period-by-period reasoning. |
| 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 ~242
Get the text forecast for a public 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" or "fire" have no text forecast upstream and will not resolve. Zone codes follow the pattern XXZ### (e.g., "WAZ315" for Western Washington lowlands).
| Name | Type | Req | Description |
|---|---|---|---|
| zone_id | string | yes | NWS public forecast zone code (e.g., "WAZ315" for the Western Washington lowlands including Seattle). Returned as "forecastZone" by nws_get_forecast and nws_find_stations, or as the "code" of an "aff… |
| 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 as provided (e.g., "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 ~593
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. 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 activ… |
| 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 (1-25, default 25). totalCount still reports the full number of distinct matches, so a small limit returns a digest of broad or national searches with… |
| 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 requested limit, max 25) |
| appliedFilters | string | – | Summary of applied search filters |
| 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`. Omitted when this is the last page. |
| notice | string | – | Guidance when no alerts matched (echoes applied filters and suggests how to broaden), when matches remain beyond this page, or when the supplied cursor points past the end of the match set. |
| 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.
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 83 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 7 tools: nws_get_forecast, nws_search_alerts, nws_get_observations, nws_find_stations, nws_list_alert_types, and 2 more. Their descriptions and schemas cost roughly 1,634 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.