Bragproof

← Reports

@cyanheads/nws-weather-mcp-server

Starts with no setup0.12.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 3 of 4 tools tried
Contacts while installing and starting: nothing

10tools listed
0hosts contacted
0files written
0.4 sto start
36dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @cyanheads/nws-weather-mcp-server@0.12.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

4 tools that take no input and look read-only were called once with nothing. 3 returned a result.

nws_search_alertsReturned a result 0.4 s · 44,449 characters
nws_get_alert_countsReturned a result 0.2 s · 898 characters
nws_get_observationsNo usable answer tool reported an error: Error: Neither station_id nor a (latitude, longitude) pair was provided Recovery: Provide either station_id or both latitude and longit
nws_list_alert_typesReturned a result under 0.1 s · 2,356 characters

During the calls (not necessarily because of them) it first contacted: api.weather.gov.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

nws_get_forecast include_amounts, latitude, longitude, hourly, cursor
Get the weather forecast for a US location. Returns either named 12-hour periods (default) or hourly breakdowns.
nws_search_alerts area, point, zone, region_type, region, event, severity, urgency, certainty, message_type, status, start, end, limit, cursor
Search weather alerts (watches, warnings, advisories) across the US: the alerts active now, or — with start and/or end — every alert message issued in that window within the last 7 days, updates and cancellations included, to answer whether a place was under a warning at a past time. Filter by state, coordinates, zone, land/marine region, event type, severity, urgency, certainty, or message type. area, point, zone, region_type, and region are mutually exclusive — provide at most one. Omit all filters for a national search.
nws_get_alert alert_id
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.
nws_get_alert_counts
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.
nws_get_observations latitude, longitude, station_id
Get current weather observations (actual measured conditions). Accepts coordinates (resolves nearest station automatically) or a station ID directly (e.g., "KSEA").
5 more tools
nws_get_observation_history station_id, start, end, limit, cursor
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.
nws_find_stations latitude, longitude, limit, cursor
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.
nws_list_alert_types
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.
nws_get_office_discussion office, product_type, sections
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. The newest product on file can be past its expiry time, and a notice then names it: an SPS usually is, so for statements in effect now use nws_search_alerts with event ["Special Weather Statement"].
nws_get_zone_forecast zone_id
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 zones vary by family: coastal zones on an ocean coast, bay, or sound (codes starting AMZ, ANZ, GMZ, PHZ, or PZZ, e.g., "PZZ251") usually serve a text forecast of wind and seas, while Great Lakes, most Alaska, Guam, American Samoa, and offshore zones (e.g., "GMZ056") have none. Zone codes follow the pattern XXZ### (e.g., "WAZ315" for the City of Seattle).

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=24.0.0
Sourcegithub.com/cyanheads/nws-weather-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Bc28rdLFQWXAY8zZACPUlSMOPqvudoHNI2XKmpK9PZh5K7IHiUFC7u7hc+SnKoqmNdk0Q7WWGFuzu+J6mumcQQ==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@cyanheads/nws-weather-mcp-server.svg)](https://bragproof.smaverk.com/r/%40cyanheads/nws-weather-mcp-server)

New version out? Ask for a fresh report.