Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Weather Data MCP Server

NPM · @DANGAHAGAN/WEATHER-MCP · SCANNED SEP 20

17 weather tools, no API keys: forecasts, alerts, air quality, marine, radar, lightning, wildfires

Available components

npm · @dangahagan/weather-mcp 86
−2 this week 86 Trust /100
Trust breakdown (7 categories)

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 Security98
  • 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
  • 57 of 162 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to weather-mcp/weather-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2243 tokens (~373/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 Management90
  • Stability observed for 27 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Install

How do I install the Weather Data MCP Server server?

Weather Data MCP Server runs locally as an npm package, launched with npx -y @dangahagan/weather-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @dangahagan/weather-mcp

# add to Claude Code
claude mcp add dgahagan-weather-mcp -- npx -y @dangahagan/weather-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dgahagan-weather-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dangahagan/weather-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dgahagan-weather-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dangahagan/weather-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dgahagan-weather-mcp -- npx -y @dangahagan/weather-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dgahagan-weather-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dangahagan/weather-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dgahagan-weather-mcp --command npx --arg -y --arg @dangahagan/weather-mcp
# ~/.hermes/config.yaml
mcp_servers:
  dgahagan-weather-mcp:
    command: "npx"
    args: ["-y", "@dangahagan/weather-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dgahagan-weather-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@dangahagan/weather-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dgahagan-weather-mcp -t stdio -c npx -a -y @dangahagan/weather-mcp
// mcp.json
{
  "mcpServers": {
    "dgahagan-weather-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dangahagan/weather-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +24
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: unverified → 0.84 ▲ functional
    • Stability: pass → 0.87 functional
    • Package version: 1.31.2 → 1.31.3 functional
  • 18 Sept 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.84 → unverified ▼ functional
    • Package version: 1.30.1 → 1.31.2 functional
    • Package version: 1.30.1 → 1.31.1 functional
    • Package version: 1.30.1 → 1.31.0 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.30.0 → 1.30.1 functional
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −2
    • Stability: pass → 0.90 functional
    • Package version: 1.13.0 → 1.30.0 functional
  • 13 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Sept 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.29.3 → 1.30.0 functional
  • 11 Sept 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.13.0 → 1.29.3 functional
    • Package version: 1.29.2 → 1.29.3 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/@dangahagan/weather-mcp@1.31.3

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 weather-mcp/weather-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/weather-mcp/weather-mcp/.github/workflows/publish.yml@refs/tags/v1.31.3
Rekor log index 2892317264
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:dfa17565ade9d21495195ddd8277bb01f9d7baa38fc119b7b9e85a59c779212d96e40bc95e39412fbc930544f48d6043008dccac3600741f2f750b558

Background: How many MCP packages publish verified provenance →

Dependencies 162 packages
Packages resolved 162
Stale 57
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~2,243 tokens

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 →

Tool Tokens
check_service_status ~56

Check whether the upstream weather APIs (NOAA, Open-Meteo) are reachable. Call this after any weather tool returns an error, or before a batch of requests. Returns per-service status and links to the official status pages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_alerts ~327

Get active weather alerts, watches, warnings, and advisories for a location. Coverage: the United States (NOAA), Canada (Environment and Climate Change Canada), European MeteoAlarm member countries, Japan (JMA), and the official national CAP feeds of India (NDMA SACHET), the Philippines (PAGASA) and Indonesia (BMKG). All of the above are keyless. With an optional `GOOGLE_WEATHER_API_KEY`, official alerts are also available for ~45+ more territories (Australia, Brazil, Mexico, and others) via the Google Weather API. Use this for safety-critical weather information when asked about "any alerts?", "weather warnings?", "is it safe?", "dangerous weather?", or "weather watches?". For forecast data, use get_forecast instead.

NameTypeReqDescription
active_onlyboolean–Whether to show only active alerts (default: true)
city_namestring–A place name to geocode, e.g. "Paris, France". Include state or country to disambiguate.
detailstring–Output verbosity: "summary" (shortest), "standard" (default, balanced), or "full" (everything the source provides).
latitudenumber–Latitude (-90 to 90). Not required if location_name or city_name is provided.
location_namestring–A saved location alias, e.g. "home". List them with list_saved_locations.
longitudenumber–Longitude (-180 to 180). Not required if location_name or city_name is provided.

No output schema declared.

No examples provided.

get_current_conditions ~540

Get the most recent weather observation for a location. Use this for current weather or when asking about "today's weather", "right now", or recent conditions without a specific historical date range. Returns NOAA station observations for US locations and Open-Meteo model data for international locations. Automatically includes frostbite-risk and heat-stress (WBGT) context when conditions are extreme. For specific past dates or date ranges, use get_historical_weather instead.

NameTypeReqDescription
city_namestring–A place name to geocode, e.g. "Paris, France". Include state or country to disambiguate.
distance_unitstring–Override the distance, visibility and elevation unit.
include_fire_weatherboolean–US locations get NOAA fire-weather indices (Haines, grassland, red-flag); elsewhere a computed Fosberg Fire Weather Index with dryness context. (default: false)
include_normalsboolean–Include climate normals (30-year averages) for comparison with current conditions, plus US daily records (default: false).
latitudenumber–Latitude (-90 to 90). Not required if location_name or city_name is provided.
location_namestring–A saved location alias, e.g. "home". List them with list_saved_locations.
longitudenumber–Longitude (-180 to 180). Not required if location_name or city_name is provided.
precipitation_unitstring–Override the precipitation unit.
pressure_unitstring–Override the pressure unit.
sourcestring–Data source: "auto" (default, selects NOAA for US or Open-Meteo for international), "noaa" (US only), "openmeteo" (global), or "metar" (global airport station observations). Choose "metar" when the u…
temperature_unitstring–Override the temperature unit.
time_formatstring–Clock format for times.
unitsstring–Unit system for output. Defaults to the server setting; individual *_unit overrides take precedence.
wind_speed_unitstring–Override the wind speed unit ("kn" is knots).

No output schema declared.

No examples provided.

get_forecast ~738

Get future weather forecast for a location. Use this for upcoming weather predictions (e.g., "tomorrow", "this week", "next 7 days", "hourly forecast"). Automatically selects the best data source: NOAA for US locations (more detailed), Open-Meteo for international locations. For current weather, use get_current_conditions. For past weather, use get_historical_weather.

NameTypeReqDescription
city_namestring–A place name to geocode, e.g. "Paris, France". Include state or country to disambiguate.
compare_modelsboolean–Compare 5 global weather models (GFS, ECMWF, ICON, GEM, UKMO) and summarize their agreement/divergence instead of a single forecast. Use when asked how confident or certain a forecast is, or whether…
daysnumber–Number of days to include in forecast (1-16 for global, 1-7 for US NOAA, default: 7)
detailstring–Output verbosity: "summary" (shortest), "standard" (default, balanced), or "full" (everything the source provides).
distance_unitstring–Override the distance, visibility and elevation unit.
ensemble_spreadboolean–Show one model's ensemble spread (ECMWF ENS, 50 members) instead of a single forecast — how confident the model itself is, day by day. Use when asked how certain/uncertain the forecast is. Daily only…
granularitystring–Forecast granularity: "daily" for day/night periods or "hourly" for hour-by-hour detail (default: "daily")
include_astronomyboolean–Include astronomy details for each forecast day (default: false, daily forecasts only). Use when asked about the moon phase, a full moon or new moon, moonrise/moonset, golden hour, twilight, or "when…
include_normalsboolean–Include climate normals (30-year averages) for comparison with forecasted temperatures, plus US daily records (default: false, daily forecasts only).
include_precipitation_probabilityboolean–Include precipitation probability in the forecast output (default: true)
include_severe_weatherboolean–Include severe weather probabilities such as thunderstorm chance, wind gust probabilities, and tropical storm/hurricane risks (default: false, US/NOAA only)
latitudenumber–Latitude (-90 to 90). Not required if location_name or city_name is provided.
location_namestring–A saved location alias, e.g. "home". List them with list_saved_locations.
longitudenumber–Longitude (-180 to 180). Not required if location_name or city_name is provided.
precipitation_unitstring–Override the precipitation unit.
pressure_unitstring–Override the pressure unit.
sourcestring–Data source: "auto" (default, selects NOAA for US or Open-Meteo for international), "noaa" (US only), or "openmeteo" (global)
temperature_unitstring–Override the temperature unit.
time_formatstring–Clock format for times.
unitsstring–Unit system for output. Defaults to the server setting; individual *_unit overrides take precedence.
wind_speed_unitstring–Override the wind speed unit ("kn" is knots).

No output schema declared.

No examples provided.

get_weather_summary ~435

Get a combined weather overview for a location in a SINGLE call — current conditions, forecast and alerts, optionally air quality and lightning. Best for broad questions like "What's the weather like in Seattle?", "Is it safe to hike today?", or "Give me a weather rundown". For a single specific data product (just the forecast, just alerts, etc.), call that specialized tool directly. Sections that are unavailable for a location (e.g. alerts in a country not yet covered) are noted rather than failing the whole summary.

NameTypeReqDescription
city_namestring–A place name to geocode, e.g. "Paris, France". Include state or country to disambiguate.
daysnumber–Number of forecast days to include when the forecast section is requested (1-16 for global, 1-7 for US NOAA, default: 7)
detailstring–Output verbosity: "summary" (shortest), "standard" (default, balanced), or "full" (everything the source provides).
distance_unitstring–Override the distance, visibility and elevation unit.
includearray–Which sections to include (default: ["current", "forecast", "alerts"]). Add "air_quality" and/or "lightning" for a fuller picture.
latitudenumber–Latitude (-90 to 90). Not required if location_name or city_name is provided.
location_namestring–A saved location alias, e.g. "home". List them with list_saved_locations.
longitudenumber–Longitude (-180 to 180). Not required if location_name or city_name is provided.
precipitation_unitstring–Override the precipitation unit.
pressure_unitstring–Override the pressure unit.
temperature_unitstring–Override the temperature unit.
time_formatstring–Clock format for times.
unitsstring–Unit system for output. Defaults to the server setting; individual *_unit overrides take precedence.
wind_speed_unitstring–Override the wind speed unit ("kn" is knots).

No output schema declared.

No examples provided.

search_location ~147

Search for locations by name and get their coordinates. Uses Nominatim (OpenStreetMap) for coverage of cities, towns, villages and hamlets worldwide. The weather tools geocode city_name themselves, so use this to disambiguate an ambiguous place name or to show the candidate matches (e.g., "Springfield", "San Francisco, CA", "Small Village, County") — not as a required first step before a weather call.

NameTypeReqDescription
limitnumber–Maximum number of results to return (1-50, default: 5)
querystringyesLocation name to search for (e.g., "Paris", "New York, NY", "Tokyo")

No output schema declared.

No examples provided.

Common questions

What is the Weather Data MCP Server server?

Weather Data MCP Server is listed in the public MCP registry as io.github.dgahagan/weather-mcp. 17 weather tools, no API keys: forecasts, alerts, air quality, marine, radar, lightning, wildfires. This page covers its npm package (@dangahagan/weather-mcp).

Is the Weather Data MCP Server server safe to use?

Weather Data MCP Server scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Data MCP Server server expose?

Weather Data MCP Server exposes 6 tools: get_weather_summary, get_forecast, get_current_conditions, get_alerts, search_location, check_service_status. Their descriptions and schemas cost roughly 2,243 tokens of context every time the server is loaded.

Is the Weather Data MCP Server server still maintained?

Weather Data MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Data MCP Server server under?

Weather Data 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.