# Smarter Weather (remote · mcp.smarterweather.com)

Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.

- Trust score: 73/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.smarterweather.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/smarterweather-weather/mcp.md), [page](https://verifymcp.io/servers/smarterweather-weather/mcp)
- npm · `@smarterweather/mcp-weather`: 45/100, [markdown](https://verifymcp.io/servers/smarterweather-weather/smarterweather-mcp-weather.md), [page](https://verifymcp.io/servers/smarterweather-weather/smarterweather-mcp-weather)

## Channel facts

- Endpoint: `https://mcp.smarterweather.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 9445 tokens (~277/item across 34 items; 31 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
  - Structured output schemas are declared (87% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http smarterweather-weather https://mcp.smarterweather.com/mcp
```

### Codex

```toml
[mcp_servers.smarterweather-weather]
url = "https://mcp.smarterweather.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smarterweather-weather": {
      "type": "remote",
      "url": "https://mcp.smarterweather.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add smarterweather-weather --url https://mcp.smarterweather.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  smarterweather-weather:
    url: "https://mcp.smarterweather.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "smarterweather-weather": {
      "type": "http",
      "url": "https://mcp.smarterweather.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 73, +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.

### 2026-07-31 (score 72, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 69, 0)

- [security] Tool “get_forecast_discussion” rewrote its description, which is the text the model reads
- [security] Tool “get_outlooks” rewrote its description, which is the text the model reads
- [security] Tool “get_lightning_activity” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [functional] Server version: 0.0.0.94 → 0.0.0.98
- [functional] New tool “get_climate_normals”
- [cosmetic] “get_forecast_discussion” added an optional parameter “day”
- [cosmetic] “get_forecast_discussion” reworded the description of “type”
- [cosmetic] “get_outlooks” reworded the description of “include_narrative”
- [cosmetic] “get_outlooks” reworded the description of “hazard”
- [cosmetic] “get_outlooks” reworded the description of “day”

### 2026-07-28 (score 69, +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.

### 2026-07-27 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 68)

First indexed and scored.

## MCP tools (31)

### `get_forecast` (~441 tokens)

Get forecast

Complete weather overview for a location: current conditions, daily forecast (day/night periods, SPC threats, severity, CAPE, UV), active alerts, and convective outlooks in one call. Data is pre-aggregated across NBM, HRRR, GFS, RTMA, and SPC and unit-converted server-side. This is the primary weather tool; reach for lower-level tools only when you need raw observations or a specific dataset. Accepts a place name directly. Examples: {"location": "Denver"} or {"location": "Portland, OR", "days": 5} or {"lat": 41.4, "lon": -92.9}.

Input parameters:

- `days` (integer): Number of forecast days (1-14). Default 10.
- `detail_level` (string): standard: compact response (~5-10KB); daily includes day_precip_probability / night_precip_probability when available (precip_probability is max of day/night). detailed: also preserves CAPE, UV, full…
- `include` (string): Comma-separated sections: current, daily, hourly, alerts, outlooks. Default "current,daily,alerts,outlooks". Use get_hourly_forecast for hourly detail.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `units` (string): Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.

Output parameters:

- `data_status` (object): Present only when the platform reports degraded/outage data sources: overall state, a caveat note, and the affected sources. Absent means no advisory was available -- not a freshness guarantee. See g…
- `forecast` (object)
- `location` (object)
- `units` (string)
- `widget` (object): sw-ui-spec widget block rendered by the MCP Apps weather widget (ui://weather-widget/v1/index.html). Additive; safe to ignore.

### `get_hourly_forecast` (~323 tokens)

Get hourly forecast

Blended hourly forecast: temperature, feels-like, humidity, wind, precipitation probability/amount, conditions, and icon per hour. Snapped to the current hour so hourly[0] is "now". Timestamps are UTC ISO 8601; convert to the local timezone before presenting. Accepts a place name directly. Example: {"location": "Chicago", "days": 2}.

Input parameters:

- `days` (integer): Days of hourly data (1-7). Default 2 (48 hours).
- `detail_level` (string): standard: compact hourly data (sampled past 24h). detailed: preserves CAPE, ceiling, UV, gust, thunderstorm probability for the first 48h.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `units` (string): Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.

Output parameters:

- `data_status` (object): Present only when the platform reports degraded/outage data sources: overall state, a caveat note, and the affected sources. Absent means no advisory was available -- not a freshness guarantee. See g…
- `forecast` (object)
- `location` (object)
- `units` (string)
- `widget` (object): sw-ui-spec widget block rendered by the MCP Apps weather widget (ui://weather-widget/v1/index.html). Additive; safe to ignore.

### `search_locations` (~191 tokens)

Search locations

Resolve a place query to candidate locations with coordinates. Accepts city names ("Denver"), city+state ("Portland, OR" via query), ZIP codes ("50219"), or partial input with fuzzy=true for autosuggest-style matching ("bost" -> Boston). Returns ranked candidates with lat/lon. Most weather tools accept a `location` string directly and geocode internally -- use this tool only to disambiguate ("which Springfield?") or to present location choices to the user. Example: {"query": "Springfield"} returns all major Springfields ranked by population.

Input parameters:

- `fuzzy` (boolean): Autosuggest mode for partial/misspelled input. Default false (exact search).
- `limit` (integer): Maximum candidates to return (1-10). Default 5.
- `query` (string, required): Place query: city, "city, state", ZIP, or partial text with fuzzy=true.

Output parameters:

- `candidates` (array)
- `query` (string)

### `reverse_geocode` (~132 tokens)

Reverse geocode

Resolve coordinates to a human-readable place (city, state, county, timezone). Use when you have lat/lon but need a display name or the local timezone. Example: {"lat": 39.74, "lon": -104.99} -> Denver, Colorado, America/Denver.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `lon` (number, required): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `lat` (number)
- `lon` (number)
- `place` (object)

### `get_alerts` (~245 tokens)

Get NWS alerts

Active NWS watches, warnings, and advisories. Location mode returns all alerts in effect at a point (severity, urgency, certainty, timing, headline, description, instructions); an empty result means no active alerts -- not a failure. alert_id mode returns full detail (including geometry) for one alert previously returned by this tool. Examples: {"location": "Miami"} or {"alert_id": "urn:oid:2.49.0.1.840..."}.

Input parameters:

- `alert_id` (string): Alert identifier for detail mode. When set, location is ignored.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `alert` (object)
- `alert_id` (string)
- `alerts`
- `location` (object)
- `widget` (object): sw-ui-spec widget block rendered by the MCP Apps weather widget (ui://weather-widget/v1/index.html). Additive; safe to ignore.

### `get_time_context` (~235 tokens)

Get time context

Complete temporal context for a location: local time, timezone, 14-day calendar with day names and Today/Tomorrow offsets, sunrise/sunset/solar times (from the weather pipeline's astro product), and moon phase. Use whenever you need to reason about dates, times, or daylight for a location -- including "what time is sunset?", "is it dark there now?", or "what day of the week is the 4th-day forecast?". Accepts a place name directly. Example: {"location": "Seattle"}.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `calendar` (array)
- `current_time` (object)
- `daylight` (object)
- `location` (object)
- `moon` (object)

### `get_period_totals` (~435 tokens)

Get period totals

Aggregate a weather variable over one or more time periods. Returns server-computed totals, maxima, minima, or averages per period. Period start/end times should use the user's local timezone boundaries (not UTC midnight). Response includes the converted value and unit per period. Ideal for questions like "total rainfall today and tomorrow" or "peak wind speed this weekend". Accepts a place name directly. Example: {"location": "Portland, OR", "variable": "precipitation", "aggregation": "sum", "periods": [{"start": "2026-07-08T07:00:00Z", "end": "2026-07-09T07:00:00Z", "label": "Today"}]}.

Input parameters:

- `aggregation` (string): Aggregation function. Default sum. Use sum for precipitation/snowfall, max for temperature/wind, min for low temperatures, avg for humidity/cloud cover.
- `dataset_id` (string): Dataset override. Default: auto-resolved NBM for the location.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `periods` (array, required): Time periods to aggregate over (1-14).
- `units` (string): Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.
- `variable` (string, required): Standard variable name (e.g. precipitation, snowfall, temperature_2m, wind_speed_10m, cape).

Output parameters:

- `aggregation` (string)
- `location` (object)
- `message` (string)
- `periods` (array)
- `variable` (string)

### `compare_locations` (~168 tokens)

Compare locations

Compare forecast variables across multiple locations side-by-side in one batched call. Returns a distilled per-location series matrix for direct comparison -- prefer this over N sequential forecast calls. Locations accept place names directly. Example: {"locations": [{"location": "Denver"}, {"location": "Boulder, CO"}], "variables": ["temperature_2m", "precipitation_probability"], "hours": 48}.

Input parameters:

- `dataset_id` (string): Dataset override. Default: auto-resolved NBM per location.
- `hours` (integer): Forecast hours. Default 24.
- `locations` (array, required): Locations to compare (2-10). Each takes location OR lat/lon, optional label.
- `variables` (array, required): Standard variable names (e.g. temperature_2m, precipitation).

Output parameters:

- `comparisons` (array)
- `hours` (number)
- `variables` (array)

### `find_best_window` (~348 tokens)

Find best weather window

Find the optimal time window for an activity based on weather criteria. Scans the forecast and returns daylight-aware periods matching all conditions. Criteria are expressed in the selected `units` system (default imperial: °F, mph, miles, feet). Example: {"location": "Boulder, CO", "criteria": {"min_temperature": 55, "max_wind_speed": 15, "max_precipitation_probability": 20}, "hours": 72, "activity_duration_hours": 3}.

Input parameters:

- `activity_duration_hours` (integer): Minimum consecutive hours meeting criteria. Default 2.
- `criteria` (object, required): Weather criteria defining acceptable conditions (all optional).
- `daylight_only` (boolean): Only consider daylight hours (sunrise to sunset). Default true.
- `hours` (integer): Hours to search. Default 72.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `units` (string): Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.

Output parameters:

- `activity_duration_hours` (number)
- `criteria_applied` (object)
- `daylight_only` (boolean)
- `location` (object)
- `message` (string)
- `sun_times` (array)
- `units` (string)
- `windows` (array)

### `get_outlooks` (~403 tokens)

Get hazard outlooks

Hazard outlooks affecting a location. hazard=severe returns SPC convective outlooks (Day 1-8 categorical risk + tornado/wind/hail probabilities); hazard=fire returns SPC fire weather outlooks; hazard=rain returns WPC Excessive Rainfall Outlook polygons (days 1-3); hazard=heat returns the NWS HeatRisk index at the point (0 none .. 4 extreme, days 1-3). include_narrative=true adds the forecaster discussion for severe (SWO), fire (FWD), or rain (QPF/QPFERD; one PIL for all days). An empty result means no outlook covers the point -- not a failure. Examples: {"location": "Moore, OK", "hazard": "severe", "include_narrative": true} or {"location": "Phoenix", "hazard": "heat"}.

Input parameters:

- `day` (integer): Outlook day for the narrative filter (1-8). Default 1.
- `hazard` (string): Hazard family: severe = SPC convective, fire = SPC fire weather, rain = WPC excessive rainfall, heat = NWS HeatRisk index. (Winter/WSSI is a planned expansion.)
- `include_narrative` (boolean): Include the forecaster narrative for the requested day (severe, fire, and rain).
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `day` (number)
- `hazard` (string)
- `heat_risk` (array)
- `location` (object)
- `narrative`
- `outlooks` (array)

### `get_forecast_discussion` (~470 tokens)

Get forecast discussion

Expert forecaster text products. type=afd: Area Forecast Discussion (WFO forecasters explain reasoning, uncertainty, model disagreements). type=hwo: Hazardous Weather Outlook (7-day hazard summary). type=mcd: SPC Mesoscale Discussions (real-time severe weather analysis). type=swo: SPC convective outlook discussion (why the risk areas are drawn where they are). type=fwd: SPC fire weather discussion. type=ero: WPC excessive rainfall / flash flood discussion. The last three are national products -- they need no location, and `day` selects the outlook day for swo and fwd. summary_only=true returns the pipeline LLM summary without the full body (much smaller). Examples: {"location": "Des Moines", "type": "afd"} or {"type": "swo", "day": 2, "summary_only": true}.

Input parameters:

- `day` (integer): Outlook day for type=swo or type=fwd (1-8). Ignored for the other types; WPC files ERO days 1-3 under one product.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `limit` (integer): Number of recent products (1-10). Default 1 (latest).
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `summary_only` (boolean): Return only the LLM summary + sections, omitting the full body text.
- `type` (string, required): Product type: afd (WFO discussion), hwo (hazard outlook), mcd (SPC mesoscale), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall).
- `wfo` (string): WFO identifier override (e.g. BOU). Default: resolved from the location.

Output parameters:

- `location` (object)
- `products` (array)
- `type` (string)

### `get_storm_reports` (~243 tokens)

Get storm reports

Recent NWS Local Storm Reports (LSRs) -- verified reports of tornadoes, hail, damaging winds, flooding near a location. Use to confirm severe weather occurrence or assess reported damage. Example: {"location": "Wichita", "hours": 12, "type": "H"}.

Input parameters:

- `hours` (integer): Lookback window in hours (1-24). Default 6.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `type` (string): Report type filter: T=tornado, H=hail, W=wind, F=flood, D=damage, S=snow.

Output parameters:

- `hours` (number)
- `location` (object)
- `reports` (object)

### `get_lightning_activity` (~225 tokens)

Get lightning activity

Real-time lightning near a location: GLM satellite flash count (30km/10min) and MRMS ground-truth lightning density + 30-minute probability. The summary field is ready-to-use. A zero flash count means no lightning inside that window -- report it as a quiet observation scoped to the window in `scope`, never as a data gap. Only call when storms may be active or the user asks about lightning. Example: {"location": "Tampa"}.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `lightning` (object)
- `location` (object)
- `scope` (string): Area and time window searched, so a zero count is unambiguous to report.

### `get_sounding` (~286 tokens)

Get radiosonde sounding

Nearest RAOB (radiosonde) vertical soundings to a point. Each sounding carries: profile (pressure-indexed thermodynamics: pressure_hpa, height_m, temperature_c, dewpoint_c, wind arrays), wind_profile (height-indexed winds for hodographs/shear), and derived indices (sbcape/mucape/mlcape + cin, lifted_index, k_index, total_totals, pwat_mm, freezing_level_m, lcl/lfc/el, bulk_shear_0_6km_kt). Soundings launch at 00Z/12Z so data can be hours old. Example: {"location": "Norman, OK"}.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `n` (integer): Number of nearest soundings (1-5). Default 1.

Output parameters:

- `location` (object)
- `soundings` (object)

### `get_forecast_distribution` (~345 tokens)

Get forecast distribution

Probabilistic forecast guidance from NBM for one aspect of the weather: percentile ranges (p10-p90), exceedance probabilities, and ensemble spread. Aspects: precip (PoP, QPF + percentiles), snow (accumulation percentiles, >1/2/4in probabilities, snow level), ice (freezing rain, accretion), temperature (temp/dewpoint + stddev), wind (speed/gust percentiles), severe (hail/tornado/damaging-wind probabilities), aviation (LIFR/IFR/MVFR visibility + ceiling probabilities), confidence (ensemble stddev; low spread = settled forecast). Examples: {"location": "Denver", "aspect": "snow", "hours": 72} or {"lat": 32.9, "lon": -97.0, "aspect": "severe"}.

Input parameters:

- `aspect` (string, required): Which distribution family to return (see tool description).
- `hours` (integer): Forecast hours (1-264). Default varies by aspect (48-72).
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `aspect` (string)
- `hours` (number)
- `location` (object)
- `series` (array)

### `get_current_conditions` (~214 tokens)

Get current conditions

Current weather right now at a location from two independent sources in one call: the RTMA gridded analysis (exact-point values, updated sub-hourly) and the nearest METAR station observation (ground truth with raw METAR, flight category). Use the analysis for point-accurate values and the station for verification. For a forecast, use get_forecast. Example: {"location": "Pella, IA"}.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `analysis`
- `location` (object)
- `nearest_station`

### `get_observations` (~274 tokens)

Get station observations

METAR surface observations from weather stations: temperature, wind, visibility, ceiling, flight category, raw METAR. Nearest mode (default) returns the closest N stations to a location; station mode returns history for a specific ICAO identifier. Examples: {"location": "Denver", "n": 3} or {"station": "KJFK", "hours": 6}.

Input parameters:

- `hours` (integer): Hours of history in station mode (1-24).
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `n` (integer): Number of nearest stations (1-10). Default 1. Ignored in station mode.
- `station` (string): ICAO station identifier (e.g. KJFK). Switches to station-history mode.

Output parameters:

- `location` (object)
- `observations` (object)
- `station` (string)

### `list_datasets` (~228 tokens)

List datasets

Discover the datasets (model grids, analyses, observations) available at a location, with per-dataset freshness (data age, latest model run). Datasets vary by domain (CONUS/Alaska/Hawaii). Use this to find dataset_id values for query_dataset and describe_dataset, or to assess whether data is current before making decisions. Example: {"location": "Anchorage"}.

Input parameters:

- `include_freshness` (boolean): Include per-dataset data age and run times. Default true.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `datasets` (object)
- `freshness` (object)
- `location` (object)

### `describe_dataset` (~96 tokens)

Describe dataset

Variables available in a dataset, with standard names, units, descriptions, and the time range of available data. Use before query_dataset to discover valid variable names. Example: {"dataset_id": "nbm_conus"}.

Input parameters:

- `dataset_id` (string, required): Pipeline dataset identifier (e.g. "nbm_conus", "mrms_reflectivity_conus"). Discover valid values with list_datasets; inspect variables with describe_dataset.

Output parameters:

- `dataset_id` (string)
- `detail` (object)

### `query_dataset` (~521 tokens)

Query dataset

Raw time series from a specific dataset for specific variables at a point. Power-user access to any gridded product (NBM, HRRR, GFS, RTMA, MRMS, air quality, ...). Time modes: hours (next N hours, default 24), time_start+time_end (explicit ISO-8601 window), or latest=true (single most-recent value). reference_time pins a specific model run, and each returned series reports the run that served it (reference_time, or reference_times when a series mixes runs) — check it before comparing two runs, since a run older than about 48 hours may no longer be available. For blended forecasts use get_forecast instead. Examples: {"location": "Denver", "dataset_id": "hrrr_surface", "variables": ["temperature_2m"], "hours": 18} or {"lat": 41.4, "lon": -92.9, "dataset_id": "rtma_conus", "variables": ["temperature_2m"], "latest": true}.

Input parameters:

- `dataset_id` (string): Dataset to query. Default: the NBM dataset for the location domain (nbm_conus/nbm_alaska/nbm_hawaii). Discover options with list_datasets.
- `hours` (integer): Forecast/lookahead hours from now (1-264). Default 24 when no other time mode set.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `latest` (boolean): Return only the most recent value (analysis datasets like RTMA/MRMS).
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `reference_time` (string): Pin a specific model run (ISO 8601). Default: latest run.
- `time_end` (string): ISO 8601 window end (with time_start).
- `time_start` (string): ISO 8601 window start (with time_end).
- `variables` (array, required): Standard variable names (e.g. temperature_2m, precipitation). Discover with describe_dataset.

Output parameters:

- `location` (object)
- `series` (array)

### `get_growing_degree_days` (~481 tokens)

Get growing degree days

Growing Degree Units (GDU / GDD) for a US location (CONUS, Alaska, Hawaii), computed from daily max/min temperatures. Pass a crop id (e.g. "corn", "soybean", "wheat") to use calibrated base/upper thresholds, or crop="custom" with base_temp_c (and optional upper_temp_c / method). Without season_start you get per-day GDU across the forecast horizon; WITH season_start (YYYY-MM-DD) you get the cumulative season-to-date total (observed history + today + forecast) plus a per-day cumulative series -- the number a grower tracks against crop milestones. Answers "how many growing degree days has my corn accumulated since May 1?" and "what's the GDU forecast this week?".

Input parameters:

- `base_temp_c` (number): Custom base threshold in °C. Required when crop="custom".
- `crop` (string, required): Crop id from the catalog (e.g. "corn", "soybean", "wheat") or "custom" to supply your own thresholds via base_temp_c.
- `day_definition` (string): Daily boundary: "nws" (default; NBM MaxT/MinT period extremes) or "local_calendar" (midnight-to-midnight local day).
- `days` (integer): Forecast horizon in days (default 10).
- `include_milestones` (boolean): Include the crop's growth-stage GDU milestones in the response.
- `lat` (number, required): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `lon` (number, required): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `method` (string): GDU method for custom crops. Defaults from whether upper_temp_c is set.
- `season_start` (string): Season/planting start as YYYY-MM-DD (local date). Presence switches the response to a cumulative season-to-date GDU total. Must be within the ~180-day observed window.
- `unit` (string): Unit system for GDU + temps. Default imperial (°F-days).
- `upper_temp_c` (number): Custom upper cutoff in °C (enables the modified method). Optional.

### `get_climate_normals` (~311 tokens)

Get climate normals

Day-of-year climate normals (NCEI 1991-2020 30-year averages) for a US location, from the nearest station with a record. Returns normal high, normal low, and normal mean for each date in the window, plus the station and how far away it is. Use this whenever a question needs a baseline rather than a forecast: "is this warm for October?", "what is a typical high here in January?", "how does this week compare to normal?". Pair it with get_forecast to say how far above or below normal the coming days run. Covers dates by day of year, so it answers for any date, past or future -- these are long-period averages, not a forecast and not observed history for a specific year.

Input parameters:

- `days` (integer): Range length in days when start/end are omitted; the window opens today (default 14).
- `end` (string): Inclusive range end as YYYY-MM-DD. Must be supplied with start.
- `lat` (number, required): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `lon` (number, required): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `start` (string): Inclusive range start as YYYY-MM-DD. Must be supplied with end.
- `unit` (string): Unit system for the normals. Default imperial (°F).

### `get_forecast_skill` (~663 tokens)

Get forecast skill

How accurate our forecasts have actually been near a location, measured against observed analysis truth. Returns bias (positive = the model runs high), mean absolute error, RMSE, and a skill score against local climatology, per model, weather variable, and forecast lead time; for probability forecasts, the Brier score and a reliability breakdown. Use this to qualify a forecast rather than assert it -- "NBM has been running 1.8F warm at 3-day leads near you, so treat that 72 as around 70" -- and to answer "how much should I trust this forecast", "is the model biased here", or "how accurate were you last month". Evidence is reported at three scopes side by side: the exact point (strongest, slowest to accumulate), the ~50km neighborhood, and the ~300km region. Prefer the most specific scope that has samples. Metrics below minimumSamples observations are withheld and listed under insufficientHistory with their count -- say that history is still accumulating rather than treating thin numbers as evidence. Coverage is a rolling recent window over verified US variables, not all of history. Entries are per model and their samples are not matched, so never conclude that one model beats another by comparing their numbers here. Each entry states the truth field it was measured against -- one designated analysis per variable -- so never compare numbers carrying different truth values either.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `lead_hours` (integer): Narrow to the lead time being asked about, in hours; the containing lead bucket is selected for you (60 gives the 48-72h bucket). Use the lead of the forecast you are qualifying: ~24 for tomorrow, ~7…
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `model` (string): Narrow to one model, e.g. nbm.
- `truth` (string): Measure against a named truth source instead of the default one for each variable, e.g. urma. Only pass this if the user asked which analysis was used or named one; the default is already the designa…
- `unit` (string): Units for the error magnitudes. Default imperial (bias/MAE/RMSE in °F, mph, in).
- `variable` (string): Narrow to one variable, e.g. temperature_2m, dew_point_2m, wind_speed_10m, wind_gusts_10m, cloud_cover, precipitation, precipitation_probability. Omit for everything measured at the location.

Output parameters:

- `cells` (object)
- `insufficientHistory` (array)
- `location` (object)
- `minimumSamples` (number)
- `skill` (array)
- `tracked` (boolean): Whether this exact coordinate is one the verification pipeline tracks.
- `units` (string)

### `get_tropical` (~130 tokens)

Get tropical activity

Active NHC (National Hurricane Center) tropical systems: forecast cones, track lines, forecast points, coastal watches/warnings, and 7-day Tropical Weather Outlook formation areas -- Atlantic + East Pacific. Each feature carries a kind (cone | track | points | watch_warning | outlook_area) plus storm name, intensity, and timing properties. include_geometry=true adds full GeoJSON geometries (large). An empty result means no active tropical activity. Example: {} or {"include_geometry": true}.

Input parameters:

- `include_geometry` (boolean): Include full GeoJSON geometries (cone/track polygons). Default false.

Output parameters:

- `active` (boolean)
- `feature_count` (number)
- `features` (array)

### `get_population_exposure` (~183 tokens)

Get population exposure

National population-exposure headline for a risk-zone outlook product: how many people are inside risk bands at or above min_level. Powers headlines like "~57M people under major heat risk tomorrow". hazard=heat covers NWS HeatRisk days 1-3 (levels: 1 minor, 2 moderate, 3 major, 4 extreme). Pass product_id directly for other risk-zone products. Example: {"hazard": "heat", "min_level": 3}.

Input parameters:

- `hazard` (string): Hazard family (expands the day-1..3 product set). Currently: heat (HeatRisk).
- `min_level` (integer): Minimum risk level to count (>=). Default 1 (any elevated risk).
- `product_id` (string): Explicit risk-zone product ID (overrides hazard), e.g. heatrisk_day1_conus.

Output parameters:

- `min_level` (number)
- `summaries` (array)

### `get_climate_records` (~274 tokens)

Get climate reports and records

NWS daily climate data: type=reports returns CLI daily climate reports (observed high/low/precip vs normals per station); type=records returns RER record event reports (record highs/lows/rainfall actually set). Filter by wfo (3-letter office, e.g. DMX), station, date (YYYY-MM-DD), start/end range, or hours lookback. Examples: {"type": "records", "hours": 48} or {"type": "reports", "wfo": "DMX", "date": "2026-07-04"}.

Input parameters:

- `date` (string): Single date, YYYY-MM-DD.
- `end` (string): Range end date, YYYY-MM-DD.
- `hours` (integer): Lookback window in hours (1-168) when no date/range is given.
- `record_type` (string): Record type filter (records only), e.g. HIGH, LOW, RAIN.
- `start` (string): Range start date, YYYY-MM-DD.
- `station` (string): Station identifier filter (reports only).
- `type` (string, required): reports = CLI daily climate reports; records = RER record events.
- `wfo` (string): WFO office filter (e.g. DMX, OUN).

Output parameters:

- `results` (object)
- `type` (string)

### `get_storm_cells` (~249 tokens)

Get storm cells

Radar-identified storm cells near a location, merging NEXRAD Level III algorithm output from the nearest radar site: storm tracks (cell position, movement, forecast positions), hail index (probability of hail/severe hail + max expected size), mesocyclone detections (rotation), and TVS (tornado vortex signatures). Use during active convection to see what the radar algorithms flag. An empty result means no detected cells -- common outside active storms. Example: {"location": "Norman, OK"}.

Input parameters:

- `include` (array): Which detection families to include. Default: all.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).

Output parameters:

- `detections` (object)
- `location` (object)
- `summary` (string): Ready-to-use one-liner. States explicitly when nothing was detected.
- `tracks` (object)

### `get_air_quality` (~316 tokens)

Get air quality

AirNow air quality at a location (CONUS): current overall AQI plus per-pollutant detail (PM2.5, ozone, PM10 concentrations) and the AirNow AQI forecast. AQI scale: 0-50 good, 51-100 moderate, 101-150 unhealthy for sensitive groups, 151-200 unhealthy, 201-300 very unhealthy, 301+ hazardous. pollutants=["aqi"] (default) is the cheap headline call; add pollutant keys or include_forecast=true when the user digs in. Example: {"location": "Boise", "pollutants": ["aqi", "pm25"], "include_forecast": true}.

Input parameters:

- `include_forecast` (boolean): Also return the AirNow next-day AQI forecast.
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `pollutants` (array): Which measurements to return. aqi = combined AQI index. Default: ["aqi"].

Output parameters:

- `current` (array)
- `forecast` (array)
- `location` (object)
- `widget` (object): sw-ui-spec widget block rendered by the MCP Apps weather widget (ui://weather-widget/v1/index.html). Additive; safe to ignore.

### `get_map_snapshot` (~522 tokens)

Get map snapshot

Render a weather map image for visual analysis. Simple form: pass `product` (a viz-catalog product_id like "mrms_qpe_01h_pass2_conus", "goes_truecolor_conus", "spc_day1_categorical", or "nexrad_l3:{SITE}:{PRODUCT}" for single-site radar, e.g. "nexrad_l3:TLX:N0B") plus a location and zoom (5=regional, 8=metro, 10=city). Composed form: pass `scene` -- a declarative scene document layering basemap + multiple weather products + active alerts + storm features + inline GeoJSON in one image (layers draw bottom-to-top, under basemap labels). Example scene: {"scene":"1.0","view":{"center":{"lat":43.8,"lon":-91.2},"zoom":8},"layers":[{"type":"weather","product":"goes_truecolor_conus"},{"type":"weather","product":"nexrad_l3:ARX:N0B"},{"type":"alerts","filter":{"events":["Tornado Warning"]},"onError":"skip"}]}. Alert filters (all optional, AND-combined): `ids` (specific alerts), `events`, `severities`, `minSeverity` (Extreme>Severe>Moderate>Minor>Unknown). Returns the rendered image plus per-layer resolved valid times.

Input parameters:

- `height` (integer)
- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `opacity` (number): Weather layer opacity
- `product` (string): viz-catalog product_id or nexrad_l3:{SITE}:{KEY} (simple form)
- `scene` (object): Full scene document (composed form). When set, product/location/zoom are ignored.
- `time` (integer): Unix seconds; frame closest to this time (default: latest)
- `width` (integer)
- `zoom` (number): Map zoom (simple form)

### `get_sounding_chart` (~265 tokens)

Get sounding chart

Render the nearest RAOB (radiosonde) sounding as a Skew-T log-P + hodograph chart image for visual analysis: temperature/dewpoint traces, wind barbs, height-banded hodograph, and a derived-indices table (CAPE/CIN, lifted index, PWAT, shear, LCL). Soundings launch at 00Z/12Z so data can be hours old. Use get_sounding for the raw profile numbers. Example: {"location": "Norman, OK"}.

Input parameters:

- `lat` (number): Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
- `location` (string): Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
- `lon` (number): Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
- `scale` (number): Raster scale factor (2 = retina; higher = larger image payload)
- `unit` (string): Temperature axis display unit

### `get_platform_status` (~150 tokens)

Get platform status

Current data-freshness status of the weather platform: overall state, per-source states (ok / degraded / outage / no_signal), open incidents with cause attribution (provider outage vs internal processing delay), and active provider advisories. Use this when a user asks whether data is current, when other tools return surprisingly stale data, or before presenting time-critical weather. If a source is degraded or in outage, tell the user their data may be stale rather than presenting it as live. No inputs. Refreshed about every 5 minutes.

Input parameters:

- `include_ok` (boolean): true: list every monitored source including healthy ones. false (default): only sources that are not ok, keeping the response compact.

Output parameters:

- `advisories` (array)
- `generated_at` (string): When the status document was generated (UTC).
- `note` (string)
- `overall` (string): Worst state across customer-facing data sources; "unknown" when status is unavailable.
- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/smarterweather-weather/mcp#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 69
- 2026-07-28: 69
- 2026-07-27: 68
- 2026-07-26: 68

## Links

- Remote endpoint: https://mcp.smarterweather.com/mcp
- Repository: https://github.com/smarterweather/developer
- Website: https://smarterweather.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/smarterweather-weather/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/smarterweather-weather/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/smarterweather-weather/mcp