accueil / serveurs / Géo & Temps / io.github.cyanheads/nws-weather-mcp-server
io.github.cyanheads/nws-weather-mcp-server
serveur MCP (Model Context Protocol) · nws-weather-mcp-server 0.11.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.cyanheads/nws-weather-mcp-server est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/nws-weather-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 10 outils
- nws_find_stations≈ 1218 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
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 point, so pass the returned nextCursor as cursor to reach the rest.cursor· string · optionnel
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 station list, so pages are contiguous within one response; the registry changes rarely, but a later call can window an updated list.latitude· number · requis
Center latitude for proximity search.longitude· number · requis
Center longitude for proximity search.
Exemple d'appel{"name": "nws_find_stations", "arguments": {"latitude": 1, "longitude": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "shown": 1, "notice": "texte", "stations": [], "nextCursor": "texte", "totalCount": 1, "effectiveLimit": 1, "requestedLimit": 1}} - nws_get_alert≈ 1788 tokens
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.
Paramètres, retour & exemple (1)
Paramètresalert_id· string · requis
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 exactly as returned; IDs are case-sensitive.
Exemple d'appel{"name": "nws_get_alert", "arguments": {"alert_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"alert": {}, "error": {}}} - nws_get_alert_counts≈ 858 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "nws_get_alert_counts", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"areas": {}, "error": {}, "regions": {}, "landAlerts": 1, "totalAlerts": 1, "marineAlerts": 1}} - nws_get_forecast≈ 1495 tokens
Get the weather forecast for a US location. Returns either named 12-hour periods (default) or hourly breakdowns.
Paramètres, retour & exemple (4)
Paramètrescursor· string · optionnel
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 within one response; NWS reissues forecasts through the day, so a later call can window a regenerated period array.hourly· boolean · optionnel
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 · requis
Latitude in decimal degrees (e.g., 47.6062).longitude· number · requis
Longitude in decimal degrees (e.g., -122.3321).
Exemple d'appel{"name": "nws_get_forecast", "arguments": {"latitude": 1, "longitude": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"mode": "texte", "error": {}, "shown": 1, "notice": "texte", "periods": [], "location": {}, "nextCursor": "texte", "totalCount": 1, "generatedAt": "texte"}} - nws_get_observation_history≈ 1816 tokens
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.
Paramètres, retour & exemple (5)
Paramètresend· string · optionnel
Time to stop before (exclusive), in the same format as start. Omit to start from the most recent observation.limit· integer · optionnel
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 the window, the response carries nextCursor; pass it back as cursor for them.start· string · optionnel
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 keeps, about 7 days.cursor· string · optionnel
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 page continues from just before the oldest observation of the one before it, so pages neither repeat nor skip an observation.station_id· string · requis
Observation station ID (e.g., "KSEA"), case-insensitive. Use nws_find_stations to discover station IDs near a coordinate.
Exemple d'appel{"name": "nws_get_observation_history", "arguments": {"station_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "notice": "texte", "timeZone": "texte", "stationId": "texte", "truncated": true, "nextCursor": "texte", "stationName": "texte", "observations": [], "effectiveLimit": 1, "requestedLimit": 1}} - nws_get_observations≈ 1250 tokens
Get current weather observations (actual measured conditions). Accepts coordinates (resolves nearest station automatically) or a station ID directly (e.g., "KSEA").
Paramètres, retour & exemple (3)
Paramètreslatitude· number · optionnel
Latitude for automatic station resolution. Use with longitude. Ignored if station_id is provided.longitude· number · optionnel
Longitude for automatic station resolution. Use with latitude. Ignored if station_id is provided.station_id· string · optionnel
Station identifier directly (e.g., "KSEA", "KORD"). Use nws_find_stations to discover station IDs.
Exemple d'appel{"name": "nws_get_observations", "arguments": {"latitude": 1, "longitude": 1, "station_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "notice": "texte", "station": "texte", "timeZone": "texte", "dewpointC": 1, "stationId": "texte", "timestamp": "texte", "heatIndexC": 1, "observedAt": "texte", "windChillC": 1, "cloudLayers": [], "stationName": "texte"}} - nws_get_office_discussion≈ 1546 tokens
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. A product over 24,000 bytes (most ZFPs) comes back as an outline of its sections — AFD section names, or ZFP/HWO/SPS 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.
Paramètres, retour & exemple (3)
Paramètresoffice· string · requis
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" field in nws_get_forecast output. Some offices file a product under other codes: Anchorage files its ZFP under "AER" (Anchorage East) and "ALU" (Anchorage West), not "AFC"; San Juan files its ZFP under "PR", and Guam its SPS under "PQ1".sections· array · optionnel
Sections to return instead of the whole product: AFD section names, case-insensitive (e.g., "DISCUSSION", "AVIATION"), or zone codes for ZFP/HWO/SPS (e.g., "WAZ315"; a code inside a listed range such as FLZ076>078 selects that segment). Take names from the outline. Returns the product header plus every matching section verbatim, in product order, followed by the product's closing lines (forecaster credits, links). Omit for the whole product, or its outline when it is too large.product_type· string · optionnel · AFD | HWO | ZFP | SPS
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, winter weather. ZFP (Zone Forecast Product) — detailed zone-by-zone text forecast. SPS (Special Weather Statement) — short-fuse advisory for notable non-warning weather.
Exemple d'appel{"name": "nws_get_office_discussion", "arguments": {"office": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "notice": "texte", "outline": [], "productCode": "texte", "productName": "texte", "productText": "texte", "issuanceTime": "texte", "issuingOffice": "texte", "wmoCollectiveId": "texte"}} - nws_get_zone_forecast≈ 1046 tokens
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" or "fire" have no text forecast upstream and will not resolve. 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).
Paramètres, retour & exemple (1)
Paramètreszone_id· string · requis
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 "affectedZones" entry with type "forecast" in nws_search_alerts. Format: two-letter state or marine area code + "Z" + three-digit number.
Exemple d'appel{"name": "nws_get_zone_forecast", "arguments": {"zone_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "zoneId": "texte", "periods": [], "updated": "texte", "periodCount": 1}} - nws_list_alert_types≈ 426 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "nws_list_alert_types", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "error": {}, "eventTypes": []}} - nws_search_alerts≈ 2896 tokens
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.
Paramètres, retour & exemple (12)
Paramètresarea· string · optionnel
US state/territory code (e.g., "WA", "OK", "PR") or marine area code (e.g., "GM"). Mutually exclusive with point and zone.zone· string · optionnel
NWS forecast zone (e.g., "WAZ558") or county zone (e.g., "WAC033"). Mutually exclusive with area and point.event· array · optionnel
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 discover valid names.limit· integer · optionnel
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 still reports the full number of distinct matches, so a small limit returns a digest of broad or national searches without dropping the total; pass the returned nextCursor as cursor to reach the rest.point· string · optionnel
Coordinates as "lat,lon" (e.g., "47.6,-122.3"). Returns alerts whose geometry contains this point. Mutually exclusive with area and zone.cursor· string · optionnel
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 active-alert feed, so alerts are contiguous within one response but not across calls — the active set changes continuously as alerts are issued and expire, so a continued page covers the collection as it stands at that moment.region· array · optionnel
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 Pacific). Marine alerts only — a land alert never matches. Mutually exclusive with area, point, zone, and region_type.status· string · optionnel · Actual | Exercise | System | Test | Draft
Alert status filter. Default "Actual". Use a different value only when you specifically need non-live alerts.urgency· array · optionnel
Filter by urgency level.severity· array · optionnel
Filter by severity level.certainty· array · optionnel
Filter by certainty level.region_type· string · optionnel · Land | Marine
Restrict to land-based or marine alerts. Mutually exclusive with area, point, zone, and region.
Exemple d'appel{"name": "nws_search_alerts", "arguments": {"area": "texte", "zone": "texte", "event": [], "limit": 1, "point": "texte", "cursor": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "shown": 1, "alerts": [], "notice": "texte", "nextCursor": "texte", "totalCount": 1, "appliedFilters": "texte", "effectiveLimit": 1, "requestedLimit": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».