Mcp Weather — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Mcp Weather (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Current weather and 7–10 day forecast for any location. Backed by Open-Meteo (https://open-meteo.com), a free aggregator of national meteorological agency data (NOAA in the US, DWD in Germany, etc.). Returns temperature, humidity, wind, precipitation, conditions. Free, no auth, no API key.
Part of Pipeworx — an MCP gateway connecting AI agents to 1857+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Weather is one of those things agents need to know about constantly — for travel planning, agricultural questions, energy demand context, event planning, real estate ("is this market in a flood zone with active flooding?"). Open-Meteo is the right backend: free, accurate, global coverage, no key gymnastics.
Common flows:
get_weather({location: "Tokyo"}) → temp, humidity, wind, conditions.get_forecast({location: "Denver"}) → daily highs/lows, precipitation chance.get_weather({latitude: 39.74, longitude: -104.99}) for places that don't geocode well by name.None. Open-Meteo is free and unauthenticated. Generous fair-use limits (~10,000 requests/day per IP). Pipeworx caches per-location for short windows so repeated calls don't burn your daily quota.
The location parameter accepts:
"Tokyo", "London", "Denver")"Paris, France" to disambiguate from Paris, TX)"94070" for US, "SW1A 1AA" for UK)latitude + longitude argumentFor ambiguous names, the tool returns a disambiguation hint. For weird locations or precision-sensitive queries (offshore, remote), pass coordinates directly.
| Data | Refresh |
|---|---|
| Current conditions | ~10 minutes |
| Hourly forecast (next 24h) | Every 1–3 hours |
| Daily forecast (1–10 days) | Every 6 hours |
Pipeworx caches with a 10-minute TTL so repeated calls within that window are cheap.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"weather": {
"url": "https://gateway.pipeworx.io/weather/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/weather/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1857+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/get_weather \
-H 'Content-Type: application/json' \
-d '{"latitude":40.7128,"longitude":-74.006}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_weather. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-weather is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/weather/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": {
"weather": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-weather"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Weather data" })The gateway picks the right tool and fills the arguments automatically.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.