Open Meteo
NPM · @PIPEWORX/MCP-OPEN-METEO · 2 COMPONENTS
Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs
Available components
Last scanned (10 hours ago)
Scores higher than 65% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-open-meteo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1059 tokens (~176/item across 6 items; 6 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 77
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-open-meteo@0.2.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-open-meteo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-open-meteo/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679795750 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9801c525de780b3a1a6bd51256b6703bb3ec1cb844c057988d935741f07dfc266460ed021c985d288870241189a152472e0eb7575e1e7b91c734df7e6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
air_quality ~194
"Air quality / AQI in [city]" / "is the air safe to breathe in [location]" / "pollution levels for [place]" / "smoke / smog / wildfire-smoke forecast" / "pollen forecast" — global air quality and pollen forecast at any lat/lng. Returns PM2.5, PM10, ozone (O3), NO2, SO2, CO, dust, and pollen (alder/birch/grass/mugwort/olive/ragweed) up to 5 days ahead, plus European AQI / US AQI. Free, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| forecast_days | number | – | 1-5 (default 5) |
| hourly | string | – | Comma-separated variables. Default pm2_5,pm10,o3,no2,european_aqi |
| latitude | number | yes | – |
| longitude | number | yes | – |
No output schema declared.
No examples provided.
flood ~118
"Flood risk for [river]" / "river discharge forecast" / "will [river] flood" / "water levels at [location]" — daily river discharge forecast from the GloFAS global flood model. Returns predicted m³/s discharge up to 30 days ahead for any river-bearing lat/lng worldwide. Use for flood risk assessment, agriculture planning, hydrology research.
| Name | Type | Req | Description |
|---|---|---|---|
| daily | string | – | Default river_discharge |
| forecast_days | number | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
No output schema declared.
No examples provided.
forecast ~263
"What's the weather in [city]" / "weather forecast for [location]" / "will it rain tomorrow", "rain chance / probability this week" / "temperature in [place] this week" / "wind / precipitation / humidity forecast" — global weather forecast up to 16 days ahead, hourly or daily, at any lat/lng. Returns temperature, precipitation, wind, humidity, cloud cover, weather codes by default; pass hourly/daily arg for custom variables. Free, keyless, no signup (Open-Meteo / ECMWF + national weather services). Pair with geocode to convert "Paris" → lat/lng first.
| Name | Type | Req | Description |
|---|---|---|---|
| daily | string | – | Comma-separated daily variables. Default sensible set. |
| forecast_days | number | – | 1-16 (default 7) |
| hourly | string | – | Comma-separated hourly variables. Default sensible set. |
| latitude | number | yes | – |
| longitude | number | yes | – |
| past_days | number | – | 0-92 (default 0) |
| temperature_unit | string | – | celsius (default) | fahrenheit |
| timezone | string | – | IANA timezone or "auto" |
| wind_speed_unit | string | – | kmh | ms | mph | kn |
No output schema declared.
No examples provided.
geocode ~145
"What are the coordinates of [city]" / "lat lng for [place]" / "find [town] location" — resolve a place name (city, village, region) to lat/lng so the other Open-Meteo tools can use them. Free, keyless, multilingual; returns up to 100 matches ranked by population. Use before forecast / historical / air_quality / marine / flood when you only have a place name.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Max results, 1-100 (default 10) |
| language | string | – | ISO-639 lang for returned names (default en) |
| name | string | yes | Place name (any language) |
No output schema declared.
No examples provided.
historical ~154
"What was the weather on [date]" / "historical weather for [location]" / "temperature in [city] last summer" / "rainfall during [period]" / "past weather data" — ERA5 reanalysis covering 1940-present at any global lat/lng. Returns hourly or daily temperature, precipitation, wind, humidity etc. for any date range. Use for climate analysis, retrospective event weather, or training data.
| Name | Type | Req | Description |
|---|---|---|---|
| daily | string | – | – |
| end_date | string | yes | YYYY-MM-DD |
| hourly | string | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| start_date | string | yes | YYYY-MM-DD |
| timezone | string | – | – |
No output schema declared.
No examples provided.
marine ~129
"Wave / swell / surf forecast for [beach]" / "sea conditions in [bay]" / "wave height at [coordinates]" / "is it safe to sail" — global marine weather forecast (wave height, wave period, wave direction, wind waves, swell waves) at any ocean lat/lng. Free, keyless. Use for surf reports, sailing prep, fishing conditions, coastal planning.
| Name | Type | Req | Description |
|---|---|---|---|
| forecast_days | number | – | – |
| hourly | string | – | Default wave_height,wave_period,wind_wave_height |
| latitude | number | yes | – |
| longitude | number | yes | – |
No output schema declared.
No examples provided.
How do I install the Open Meteo MCP server?
Open Meteo runs locally as an npm package, launched with npx -y @pipeworx/mcp-open-meteo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-open-meteo
claude mcp add pipeworx-io-open-meteo -- npx -y @pipeworx/mcp-open-meteo
What is the Open Meteo MCP server?
Open Meteo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/open-meteo. Open-Meteo MCP, weather forecast + historical reanalysis + sister APIs. This page covers its npm package (@pipeworx/mcp-open-meteo).
Is the Open Meteo MCP server safe to use?
Open Meteo scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Open Meteo MCP server expose?
Open Meteo exposes 6 tools: forecast, historical, geocode, air_quality, marine, flood. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.
Is the Open Meteo MCP server still maintained?
Open Meteo is still listed as active in the MCP registry. We last reached this channel on 5 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 Open Meteo MCP server under?
Open Meteo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Open Meteo MCP server?
VerifyMCP ran 15 checks on Open Meteo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Open Meteo: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.