NWS Surface Wind Observations MCP Server
PYPI · WINDS-MCP
NWS surface wind observations (ASOS/AWOS) via Weather.gov and Iowa Environmental Mesonet APIs
Available components
Last scanned (1 day ago)
Scores higher than 82% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to mansurjisan/ocean-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 98 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1341 tokens (~167/item across 8 items; 8 tools + 0 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −6
- Stability: pass → 0.60 functional
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed pypi/winds-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mansurjisan/ocean-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mansurjisan/ocean-mcp/.github/workflows/publish.yml@refs/tags/winds-mcp-v0.1.2 |
| Rekor log index | 2275847964 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:eb789f0b79fd98243fa0dc19ddd70dbd4be2d17739de5e950e3441b71c205d22 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
winds_compare_stations ~110
Compare latest wind observations across multiple stations. Args: station_ids: List of ICAO station IDs to compare (max 10, e.g., ['KJFK', 'KLGA', 'KEWR']). units: Unit system — 'metric' or 'english' (default: metric). response_format: Output format — 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| station_ids | array | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_find_nearest_stations ~154
Find NWS stations nearest to a geographic coordinate. Args: latitude: Latitude in decimal degrees (e.g., 40.7). longitude: Longitude in decimal degrees (e.g., -74.0). limit: Maximum number of stations to return (default 5). NWS returns all stations near the point untrimmed; this caps both the markdown list and the JSON response (which flags truncation if more were available). response_format: Output format — 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| limit | integer | – | – |
| longitude | number | yes | – |
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_get_daily_summary ~232
Get daily wind statistics summary from IEM ASOS archive. Computes daily max/mean wind speed, max gust, and prevailing direction. Args: station_id: Station identifier — ICAO (e.g., 'KJFK') or FAA (e.g., 'JFK'). start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. units: Unit system — 'metric' or 'english' (default: metric). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON days returned (default 2000; a 366-day request produces at most ~366 daily summaries, so this rarely triggers). Days are oldest-first, so the most recent max_records are kept and the JSON flags any truncation.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| max_records | integer | – | – |
| response_format | string | – | – |
| start_date | string | yes | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_get_history ~267
Get historical ASOS wind data from the Iowa Environmental Mesonet archive. Provides access to historical surface observations dating back to ~2000. Uses 3-char FAA codes internally; K-prefix (ICAO) is stripped automatically. Args: station_id: Station identifier — ICAO (e.g., 'KJFK') or FAA (e.g., 'JFK'). start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. units: Unit system — 'metric' or 'english' (default: metric). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON records returned (default 2000). The IEM archive returns rows oldest-first, so the most recent max_records are kept and the JSON flags any truncation. (A date range up to 366 days can be tens of thousands of 5-minute rows. Markdown is capped to the most recent 200 rows regardless.)
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| max_records | integer | – | – |
| response_format | string | – | – |
| start_date | string | yes | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_get_latest_observation ~133
Get the most recent surface observation at a station. Returns wind speed, direction, gust, temperature, pressure, and visibility. Args: station_id: ICAO station identifier (e.g., 'KJFK', 'KORD'). units: Unit system — 'metric' (m/s, °C, hPa) or 'english' (kt, °F, inHg). Default: metric. response_format: Output format — 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_get_observations ~189
Get recent surface observations over a time window. Args: station_id: ICAO station identifier (e.g., 'KJFK'). hours: Number of hours of observations to retrieve (default 24, max 168). units: Unit system — 'metric' or 'english' (default: metric). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on JSON records returned (default 2000). NWS returns observations newest-first, so the most recent max_records are kept and the JSON flags any truncation. (Markdown is capped to the most recent 200 rows regardless of this setting.)
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| max_records | integer | – | – |
| response_format | string | – | – |
| station_id | string | yes | – |
| units | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_get_station ~79
Get detailed metadata for a specific NWS station. Args: station_id: ICAO station identifier (e.g., 'KJFK', 'KORD', 'KLAX'). response_format: Output format — 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| station_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
winds_list_stations ~177
List NWS weather stations by US state. Returns ASOS, AWOS, and other NWS-affiliated surface observation stations. Station IDs are ICAO codes (e.g., KJFK, KORD, KLAX). Args: state: US state 2-letter code (e.g., 'NY', 'FL', 'CA'). limit: Maximum number of stations to return (default 50). Also caps the JSON response — the NWS API itself never returns more than this many, so JSON truncation only fires if `limit` is raised beyond what a single request should return. response_format: Output format — 'markdown' (default) or 'json'.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| response_format | string | – | – |
| state | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the NWS Surface Wind Observations MCP Server server?
NWS Surface Wind Observations MCP Server runs locally as a PyPI package, launched with uvx winds-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · winds-mcp
claude mcp add mansurjisan-winds-mcp -- uvx winds-mcp
What is the NWS Surface Wind Observations MCP Server server?
NWS Surface Wind Observations MCP Server is listed in the public MCP registry as io.github.mansurjisan/winds-mcp. NWS surface wind observations (ASOS/AWOS) via Weather.gov and Iowa Environmental Mesonet APIs. This page covers its PyPI package (winds-mcp).
Is the NWS Surface Wind Observations MCP Server server safe to use?
NWS Surface Wind Observations MCP Server scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 NWS Surface Wind Observations MCP Server server expose?
NWS Surface Wind Observations MCP Server exposes 8 tools: winds_get_latest_observation, winds_get_observations, winds_get_history, winds_get_daily_summary, winds_compare_stations, and 3 more. Their descriptions and schemas cost roughly 1,341 tokens of context every time the server is loaded.
Is the NWS Surface Wind Observations MCP Server server still maintained?
NWS Surface Wind Observations MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the NWS Surface Wind Observations MCP Server server under?
NWS Surface Wind Observations MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.