# Weather MCP Server by Meteosource (remote · mcp.meteosource.com)

Forecasts, severe-weather alerts, air quality, 20-year weather history, solar and wind production.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.meteosource.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-meteosource-weather/mcp.md), [page](https://verifymcp.io/servers/com-meteosource-weather/mcp)

## Channel facts

- Endpoint: `https://mcp.meteosource.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 49/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3164 tokens (~452/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Weather MCP Server by Meteosource server?

Weather MCP Server by Meteosource is a hosted endpoint at https://mcp.meteosource.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-meteosource-weather": {
      "url": "https://mcp.meteosource.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "com-meteosource-weather": {
      "Transport": "http",
      "Url": "https://mcp.meteosource.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-meteosource-weather -t streamable-http -u 'https://mcp.meteosource.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-meteosource-weather": {
      "type": "http",
      "url": "https://mcp.meteosource.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-11-20 (score 69, +1)

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

### 2026-11-18 (score 68, +1)

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

### 2026-11-16 (score 67, +1)

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

### 2026-11-14 (score 66, +1)

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

### 2026-11-12 (score 65, +1)

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

### 2026-11-09 (score 64, +1)

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

### 2026-11-07 (score 63, +1)

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

### 2026-11-06 (score 62, 0)

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

## MCP tools (7)

### `search_places` (~156 tokens)

Find locations and their Meteosource place_id.

    Use this first to resolve city names, postal codes or coordinates into
    place_id values for the other weather tools. Provide either `query`
    (place name or postal code) to search, or `lat` + `lon` to find the
    nearest known place. Returns up to 10 matches ordered by relevance,
    each with place_id, administrative area, country, coordinates and
    timezone. Note: lat/lon are returned in degree-letter format
    (e.g. "50.08804N").

Input parameters:

- `language` (string)
- `lat` (number)
- `lon` (number)
- `query` (string)

### `get_forecast` (~320 tokens)

Weather forecast for up to 20 locations in one call.

    Sections (comma-separated): 'current' (now), 'hourly' (up to 168 h ahead,
    trimmed to `hours`), 'daily' (up to 30 days ahead, trimmed to `days`),
    'minutely' (precipitation minute-by-minute, higher tiers), 'alerts'
    (official weather warnings, startup tier and above), or 'all'.
    Use `variables` to keep only specific fields (e.g. ["temperature", "wind",
    "precipitation", "probability", "irradiance"]) and reduce output size —
    recommended when querying many locations. Timezone defaults to each
    location's local time; units default per-country ('metric' forces SI).
    Forecast horizon depends on the subscription tier (free: 7 days).

    Output: time series (hourly, daily, minutely) are tables — `columns`
    listed once and `rows` as arrays in column order; nested API groups are
    flattened with underscores (wind_speed, probability_storm,
    cloud_cover_total). `units` is given once at the top level when it is
    the same for every location.

Input parameters:

- `days` (integer)
- `hours` (integer)
- `language` (string)
- `locations` (array, required)
- `sections` (string)
- `timezone` (string)
- `units` (string)
- `variables` (array)

### `get_alerts` (~111 tokens)

Official weather warnings (severe weather alerts) for up to 20 locations.

    Returns only locations that currently have an active alert, with event
    type, severity, validity window and headline — an empty list means all
    clear. Cheap to call frequently; designed for monitoring/polling.
    Coverage: USA, EU countries and Canada. Requires the startup tier or
    higher (not available on the free tier).

Input parameters:

- `language` (string)
- `locations` (array, required)

### `get_weather_history` (~658 tokens)

Historical weather (archive) with server-side aggregation.

    The archive holds 20 years, but how much of it a key may read depends on
    its plan: startup includes the last 7 days, standard the last year,
    premium and flexi all 20 years; byvalue reaches 366 days back and no
    further. Older days need Meteosource's paid historical add-on (billed per
    location and day); without it the API refuses such a day with "not
    allowed to access historical data this old", reported per location, so
    start inside the plan's range. Dates are YYYY-MM-DD, inclusive.
    Granularity: 'hourly' (raw hours, max 14 days per call), 'daily'
    (per-day min/max/avg/sum statistics, max 366 days) or 'monthly'
    (folded from daily, max 366 days per call — call repeatedly for
    multi-year analyses; results are cached so repeats are cheap).
    Variables (default: temperature, precipitation, wind): cape, cloud_cover,
    dew_point, evaporation, feels_like, humidity, irradiance, ozone,
    precipitation, precipitation_type, pressure, soil_temperature,
    surface_temperature, temperature, weather, wind, wind_distribution.
    Aggregations per variable: temperature min/max/avg, precipitation sum,
    wind speed avg + gusts max, irradiance sum in Wh/m2 (useful for PV
    analysis), weather = most frequent code of the day, precipitation_types =
    kinds seen that day (e.g. "rain,snow"; "none" when dry) — use weather and
    precipitation_type to document what happened (snow, fog, thunderstorm).
    wind_distribution (daily/monthly; for wind-turbine siting) = hours per
    10 m wind-speed bin (wind_hours_0_2 … wind_hours_10_plus) and
    wind_power_density_w_m2 = 1/2 * 1.225 * mean(v^3) at 10 m — scale to hub
    height yourself (the API has no hub-height wind).
    `normals=true` (daily/monthly) adds long-term columns for each calendar
    day: temperature_normal_avg/min/max, temperature_record_min/max,
    wind_normal_speed, wind_record_gusts, precipitation_normal_sum and…

Input parameters:

- `date_from` (string, required)
- `date_to` (string, required)
- `granularity` (string)
- `locations` (array, required)
- `normals` (boolean)
- `timezone` (string)
- `units` (string)
- `variables` (array)

### `get_air_quality` (~170 tokens)

Hourly air-quality (smog) forecast for up to 20 locations, about 4 days ahead.

    Columns: `air_quality` (index, 1 = good, higher = worse) and pollutant
    surface concentrations — default pm10, pm25, no2_surface, so2_surface,
    ozone_surface; also available via `variables`: co_surface, no_surface,
    ozone_total, aerosol_550, dust_550nm, dust_mixing_ratio_05. Output is a
    table per location (`columns` once, `rows` as arrays), trimmed to `hours`.
    Not available on the free tier.

Input parameters:

- `hours` (integer)
- `locations` (array, required)
- `timezone` (string)
- `variables` (array)

### `get_solar_production` (~471 tokens)

Production of photovoltaic systems, past and forecast, for up to 20 sites.

    Each site is lat + lon plus the installation: module_kw (installed kWp;
    use 1 to get specific yield per kWp), inverter_kw (defaults to module_kw),
    tilt (degrees from horizontal, default 30) and orientation (azimuth the
    modules face, clockwise from north: 180 = south, the default). Dates are
    YYYY-MM-DD, inclusive, from up to 20 years back to 4 days ahead, so one
    call can cover last week's actual weather and the coming days. The
    renewables plan includes the last 3 years; older days need the paid
    historical add-on, otherwise the API refuses them ("historical data this
    old"), reported per site.
    Granularity: 'hourly' (power at each full hour, max 14 days per call),
    'daily' or 'monthly' (energy, max 366 days per call — call repeatedly for
    multi-year yield; past days are cached so repeats are cheap).
    Columns: production_kw = output of the system at that hour (an
    instantaneous value); production_kwh = energy of the day or month, summed
    from those hourly values; production_max_kw = its peak.
    `variables` adds the weather behind the production: irradiance (ghi, dni,
    dhi in W/m2 hourly; ghi/dni/dhi_sum_wh_m2 daily and monthly), temperature,
    cloud_cover, humidity, dew_point, pressure, snowfall (flag per hour;
    snowfall_hours daily and monthly).
    Each site+day costs one API request on first fetch; a single call is
    capped at 400 site-days — split longer ranges into multiple calls.
    Needs a key on the renewables tier.

    Output: `columns` once at the top level; each site has `rows` as arrays
    in column order.

Input parameters:

- `date_from` (string, required)
- `date_to` (string, required)
- `granularity` (string)
- `sites` (array, required)
- `timezone` (string)
- `units` (string)
- `variables` (array)

### `get_wind_production` (~942 tokens)

Production of wind farms, past and forecast, for up to 20 sites.

    Each site is lat + lon plus the farm: turbine_model (catalogue below),
    exactly one of turbine_count or total_capacity (MW), hub_height (metres,
    default 100) and roughness of the surrounding terrain (water, open,
    farmland — the default, suburban, urban). Dates are YYYY-MM-DD, inclusive,
    from up to 20 years back to 4 days ahead, so one call can cover last
    week's actual weather and the coming days. The renewables plan includes
    the last 3 years; older days need the paid historical add-on, otherwise
    the API refuses them ("historical data this old"), reported per site.
    Granularity: 'hourly' (power at each full hour, max 14 days per call),
    'daily' or 'monthly' (energy, max 366 days per call — call repeatedly for
    multi-year yield; past days are cached so repeats are cheap).
    Columns: production_mw = output of the whole farm at that hour (an
    instantaneous value); production_mwh = energy of the day or month, summed
    from those hourly values; production_max_mw = its peak.
    `variables` adds the weather behind the production: wind (10 m above
    ground, not hub height: wind_10m_speed, wind_10m_gusts and wind_10m_angle
    hourly; speed avg/max and gusts max daily and monthly), temperature,
    dew_point, pressure.
    Turbine catalogue (series + rotor diameter in m / rated power in kW):
    Adwen AD116/5000; Enercon E48/800, E-53/800, E-70/2000, E-70/2300,
    E-82/2000, E-82/2300, E-82/2350, E-82/3000, E-92/2350, E-101/3050,
    E-101/3500, E-115/3000, E-115/3200, E-126/4200, E-126/7500, E-126/7580,
    E-141/4200; Eno ENO100/2200, ENO114/3500, ENO126/3500; GE GE100/2500,
    GE103/2750, GE120/2500, GE120/2750, GE130/3200; Nordex N90/2500,
    N100/2500, N117/2400, N131/3000, N131/3300, N131/3600; Senvion MM92/2050,
    MM100/2000, S104/3400, S114/3200, S114/3400, S122/3000, S122/3200,
    S126/6150, S152/6330; aerodyn SCD168/8000; Siemens SWT113/2300,…

Input parameters:

- `date_from` (string, required)
- `date_to` (string, required)
- `granularity` (string)
- `sites` (array, required)
- `timezone` (string)
- `units` (string)
- `variables` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 64
- 2026-11-08: 63
- 2026-11-07: 63
- 2026-11-06: 62
- 2026-11-05: 62
- 2026-11-04: 61
- 2026-11-03: 61
- 2026-11-02: 60
- 2026-11-01: 60
- 2026-10-31: 59
- 2026-10-30: 59
- 2026-10-29: 58
- 2026-10-28: 58
- 2026-10-27: 57
- 2026-10-26: 57

## Common questions

### What is the Weather MCP Server by Meteosource server?

Weather MCP Server by Meteosource is listed in the public MCP registry as com.meteosource/weather. Forecasts, severe-weather alerts, air quality, 20-year weather history, solar and wind production. This page covers its hosted endpoint (https://mcp.meteosource.com/mcp).

### Is the Weather MCP Server by Meteosource server safe to use?

Weather MCP Server by Meteosource scores 69 out of 100 on VerifyMCP. 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 by Meteosource server expose?

Weather MCP Server by Meteosource exposes 7 tools: search_places, get_forecast, get_alerts, get_weather_history, get_air_quality, and 2 more. Their descriptions and schemas cost roughly 2,828 tokens of context every time the server is loaded.

### Does the Weather MCP Server by Meteosource server require authentication?

No. We connected to Weather MCP Server by Meteosource without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Weather MCP Server by Meteosource server still maintained?

Weather MCP Server by Meteosource is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Weather MCP Server by Meteosource server?

VerifyMCP ran 12 checks on Weather MCP Server by Meteosource, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Weather MCP Server by Meteosource: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.meteosource.com/mcp
- Authorisation metadata: https://mcp.meteosource.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/Meteosource/meteosource-weather-mcp
- Website: https://mcp.meteosource.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-meteosource-weather/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-meteosource-weather/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-meteosource-weather/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-meteosource-weather/mcp
