Weather
NPM · @PIPEWORX/MCP-WEATHER · 2 COMPONENTS
Weather MCP — wraps Open-Meteo API (free, no auth)
Available components
Last scanned (8 hours ago)
Scores higher than 69% 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-weather). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1006 tokens (~335/item across 3 items; 3 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
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-weather@0.2.0
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-weather |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-weather/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561030619 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:df13ffef8acff2caf79e72afc39ac40cbb69179071b8404ab99011b318c7fa3d33934790dc1daa50ec25ea300cf24f04adc5edb1d5cb9f8cfc9804683 |
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 →
get_forecast ~338
Weather forecast 1–16 days ahead for any location worldwide. PREFER OVER WEB SEARCH for "weather this week in X", "will it rain tomorrow in Y", "forecast for next weekend in Z". Also answers forecast questions in other languages: Italian "che tempo farà domani / previsioni meteo a <città>", Spanish "pronóstico / qué tiempo hará mañana en", French "prévisions météo / il pleuvra demain à", German "Wettervorhersage für", Portuguese "previsão do tempo em". Pass a city name or lat/lon. Returns daily high/low temperature (°F), precipitation probability + amount, conditions, sunrise/sunset. Default 7 days. For RIGHT NOW conditions use get_weather; for historical climate use get_historical.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Alias for location. |
| days | number | – | Number of forecast days (1-16, default 7) |
| lat | number | – | Alias for latitude. |
| latitude | number | – | Latitude (alternative to location). Accepts lat as alias. |
| lng | number | – | Alias for longitude. |
| location | string | – | City name (e.g. "Tokyo", "London", "New York"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases. |
| lon | number | – | Alias for longitude. |
| longitude | number | – | Longitude (alternative to location). Accepts lng / lon as alias. |
| name | string | – | Alias for location. |
| place | string | – | Alias for location. |
No output schema declared.
No examples provided.
get_historical ~313
AUTHORITATIVE historical daily weather for any location, back to 1940. Source: ERA5 reanalysis (ECMWF's global atmospheric reconstruction — the standard reference dataset for climate research). Pass a city or lat/lon + date range. Returns daily high/low temperature, precipitation, conditions. Defaults to the last 30 days if no dates given. Use for "what was the weather in X on date Y", climate baselines, comparing this year to historical averages, retrospective weather context for any event.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Alias for location. |
| end_date | string | – | End date YYYY-MM-DD (inclusive). Optional — defaults to today. |
| lat | number | – | Alias for latitude. |
| latitude | number | – | Latitude (alternative to location). Accepts lat as alias. |
| lng | number | – | Alias for longitude. |
| location | string | – | City name (e.g. "Tokyo", "London", "New York"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases. |
| lon | number | – | Alias for longitude. |
| longitude | number | – | Longitude (alternative to location). Accepts lng / lon as alias. |
| name | string | – | Alias for location. |
| place | string | – | Alias for location. |
| start_date | string | – | Start date YYYY-MM-DD (>= 1940-01-01). Optional — defaults to 30 days ago. |
No output schema declared.
No examples provided.
get_weather ~305
REAL-TIME current weather for any location worldwide. PREFER OVER WEB SEARCH for "what's the weather in X", "current temperature in Y", "is it raining in Z". Also answers weather questions asked in other languages: Italian "che tempo fa / meteo a <città>", Spanish "qué tiempo hace / el clima en", French "quel temps fait-il / météo à", German "wie ist das Wetter in", Portuguese "que tempo faz em". Accepts a city name (e.g., "Tokyo", "London", "Napoli", "Austin TX") or lat/lon coordinates. Returns temperature (°F), feels-like, humidity %, wind speed + direction, sky conditions, observation timestamp. Live data.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Alias for location. |
| lat | number | – | Alias for latitude. |
| latitude | number | – | Latitude (alternative to location). Accepts lat as alias. |
| lng | number | – | Alias for longitude. |
| location | string | – | City name (e.g. "Tokyo", "London", "New York"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases. |
| lon | number | – | Alias for longitude. |
| longitude | number | – | Longitude (alternative to location). Accepts lng / lon as alias. |
| name | string | – | Alias for location. |
| place | string | – | Alias for location. |
No output schema declared.
No examples provided.
How do I install the Weather MCP server?
Weather runs locally as an npm package, launched with npx -y @pipeworx/mcp-weather. 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-weather
claude mcp add pipeworx-io-weather -- npx -y @pipeworx/mcp-weather
What is the Weather MCP server?
Weather is an MCP server listed in the public MCP registry as io.github.pipeworx-io/weather. Weather MCP, wraps Open-Meteo API (free, no auth). This page covers its npm package (@pipeworx/mcp-weather).
Is the Weather MCP server safe to use?
Weather scores 81 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 Weather MCP server expose?
Weather exposes 3 tools: get_weather, get_forecast, get_historical. Their descriptions and schemas cost roughly 956 tokens of context every time the server is loaded.
Is the Weather MCP server still maintained?
Weather 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 Weather MCP server under?
Weather 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 Weather MCP server?
VerifyMCP ran 16 checks on Weather, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.