io.github.cyanheads/nws-weather-mcp-server

REMOTE · NWS.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

Get US weather forecasts, active alerts, and current observations.

Available components

remote · nws.caseyjhand.com 72 npm · @cyanheads/nws-weather-mcp-server 35

+4 this week 72 72 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability82

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 1357 tokens (~169/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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · nws.caseyjhand.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http cyanheads-nws-weather-mcp-server https://nws.caseyjhand.com/mcp

# ~/.codex/config.toml

[mcp_servers.cyanheads-nws-weather-mcp-server]
url = "https://nws.caseyjhand.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-nws-weather-mcp-server": {
      "type": "remote",
      "url": "https://nws.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add cyanheads-nws-weather-mcp-server --url https://nws.caseyjhand.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  cyanheads-nws-weather-mcp-server:
    url: "https://nws.caseyjhand.com/mcp"

// mcp.json

{
  "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.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 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
30 Jul 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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 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
26 Jul 26 67

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	7 Jul 2026	5 Oct 2026	ECDSA 256	ECDSA-SHA256	5aad900eb2055a0b0ea55912ec19680c
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

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

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

MCP tools — 7 exposed · ~1,198 tokens

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.

Tool Tokens

nws_find_stations Nws Find Stations ~79

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.

Input Output Examples

Name	Type	Req	Description
latitude	number	yes	Center latitude for proximity search.
limit	integer	—	Max stations to return (1-50).
longitude	number	yes	Center longitude for proximity search.

Name	Type	Req	Description
notice	string	—	Guidance when no stations were found near the requested coordinates.
stations	array	yes	Nearby stations sorted by distance
totalCount	number	yes	Number of stations returned (respects the limit parameter)
totalFound	number	yes	Total observation stations available near this location before the limit was applied

No examples provided.

nws_get_forecast Nws Get Forecast ~114

Get the weather forecast for a US location. Returns either named 12-hour periods (default) or hourly breakdowns.

Input Output Examples

Name	Type	Req	Description
hourly	boolean	—	If true, returns hourly forecast (next 48 one-hour periods) 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
generatedAt	string	yes	When the forecast was generated (ISO 8601)
location	object	yes	Resolved location metadata
mode	string	yes	Forecast mode: "hourly" or "7-day"
notice	string	—	Set when upstream returned more periods than the cap — states how many periods were omitted.
periodCount	number	yes	Number of forecast periods returned (capped at 48).
periods	array	yes	Forecast periods
totalPeriodCount	number	yes	Total forecast periods available upstream before the cap was applied.

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").

Input Output Examples

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	—	yes	Barometric pressure in Pascals
cloudLayers	array	yes	Cloud layer information
dewpointC	—	yes	Dewpoint in Celsius
heatIndexC	—	yes	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	yes	Observation timestamp (ISO 8601)
relativeHumidityPct	—	yes	Relative humidity in percent (0-100)
station	string	yes	Station ID that served the observation (e.g., "KSEA")
stationId	string	yes	Observation station ID
stationName	string	yes	Station name
temperatureC	—	yes	Temperature in Celsius
textDescription	string	yes	Conditions summary (e.g., "Mostly Cloudy")
timeZone	—	yes	Station time zone when known
timestamp	string	yes	Observation time (ISO 8601)
visibilityM	—	yes	Visibility in meters
windChillC	—	yes	Wind chill in Celsius
windDirectionDeg	—	yes	Wind direction in degrees (0-360)
windGustKmh	—	yes	Wind gust in km/h
windSpeedKmh	—	yes	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.

Input Output Examples

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
issuanceTime	string	yes	When the product was issued (ISO 8601), e.g., "2026-05-30T10:33:00+00:00".
issuingOffice	string	yes	Issuing office call sign (e.g., "KSEW"). Includes the K/P prefix, unlike the input office code.
productCode	string	yes	Product type code (e.g., "AFD").
productName	string	yes	Full product name (e.g., "Area Forecast Discussion").
productText	string	yes	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	yes	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 ~214

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 zone codes in "affectedZones", and nws_find_stations returns them in the "forecastZone" column; use those codes here. Zone codes follow the pattern XXZ### (e.g., "WAZ315" for Western Washington lowlands). County zone codes (XXC###) are not supported — use the forecast zone code.

Input Output Examples

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 in "affectedZones" by nw…

Name	Type	Req	Description
periodCount	number	yes	Number of forecast periods returned.
periods	array	yes	Forecast periods in chronological order, typically covering 7 days.
updated	string	yes	When the zone forecast was last updated (ISO 8601 with timezone offset).
zoneId	string	yes	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 Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
count	number	yes	Number of event types
eventTypes	array	yes	Alert event type names sorted alphabetically

No examples provided.

nws_search_alerts Nws Search Alerts ~356

Search active weather alerts (watches, warnings, advisories) across the US. Filter by state, coordinates, zone, event type, severity, urgency, or certainty. area, point, and zone are mutually exclusive. Omit all filters for a national search.

Input Output Examples

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.
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 the response (1-25, default 25). totalCount still reports the full number of matches, so a small limit returns a digest of broad or national searches without dr…
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.
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	yes	Matching alerts (capped at the requested limit, max 25)
appliedFilters	string	yes	Summary of applied search filters
notice	string	—	Guidance when no alerts matched — echoes applied filters and suggests how to broaden the search.
shownCount	number	yes	Number of alerts included in this response
totalCount	number	yes	Total number of matching alerts before the limit/cap is applied

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	67
27 Jul	68
28 Jul	68
29 Jul	69
30 Jul	70
31 Jul	70
1 Aug	71
2 Aug	71
3 Aug	72