open-meteo-mcp-server
io.github.cyanheads/open-meteo-mcp-servercyanheadsstreamable-httpv0.6.1Scanned
Global weather via Open-Meteo: forecast, historical, marine, air quality, geocoding, elevation.
11 tools: 1 change things and 10 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the open-meteo-mcp-server can do
The open-meteo-mcp-server is published by the GitHub account cyanheads. It has 11 tools. It can create or change data (1 tool: openmeteo_dataframe_query), but cannot delete data. 10 tools only read.
2 tools read private data (openmeteo_dataframe_query and openmeteo_dataframe_describe).
The fixed checks matched 4 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 0.6.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 1Claude Code: ask
openmeteo_dataframe_queryRun a read-only SQL SELECT against tables staged on a DataCanvas by openmeteo_get_forecast, openmeteo_get_historical, openmeteo_get_marine, openmeteo_get_air_quality, openmeteo_get…Reads private data1 finding
Why it is in this group
- The name "openmeteo_dataframe_query" says "query": a word for reading.
- The description's first verb is "run": a word for a change.
- The input takes a statement or command to run (input.sql), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "sql": it reads databases.
- private-dataThe name says "query" and the input takes a statement (input.sql): it reads databases.
Findings
- Warn
The server marks "openmeteo_dataframe_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "openmeteo_dataframe_query" says "query": a word for reading.
Description, as the server wrote it Run a read-only SQL SELECT against tables staged on a DataCanvas by openmeteo_get_forecast, openmeteo_get_historical, openmeteo_get_marine, openmeteo_get_air_quality, openmeteo_get_ensemble, openmeteo_get_flood, or openmeteo_get_climate. Pass the canvas_id returned when any of those tools spills (truncated: true), and reference the exact table_name those tools return alongside it. Call openmeteo_dataframe_describe to list staged tables and their columns when you need to discover names. Returns the first limit rows (default 25, or the per-call row cap when that is lower), each whole, plus row_count — exact, or a lower bound flagged by count_error when counting fails or runs past 5 seconds; page the rest with LIMIT / OFFSET. A page's size rests on limit and the columns selected, so from a member-suffixed ensemble table select the columns the question needs rather than SELECT *. One response carries at most 8,000,000 characters of row data (its rows written as JSON, a character that needs escaping counted at its escaped length), and a page over that fails as result_too_large rather than being cut. An error message relayed from the query engine is cut to 2,000 characters.
Annotations the server declares
- readOnlyHint: true
Only reads 10Show 10 read-only tools
openmeteo_dataframe_describeList the tables and their columns on a DataCanvas staged by openmeteo_get_forecast, openmeteo_get_historical, openmeteo_get_marine, openmeteo_get_air_quality, openmeteo_get_ensembl…Reads private dataNo findings
Why it is in this group
- The name "openmeteo_dataframe_describe" says "describe": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "table": it reads databases.
Description, as the server wrote it List the tables and their columns on a DataCanvas staged by openmeteo_get_forecast, openmeteo_get_historical, openmeteo_get_marine, openmeteo_get_air_quality, openmeteo_get_ensemble, openmeteo_get_flood, or openmeteo_get_climate. Call this first to discover table names before querying with openmeteo_dataframe_query.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_air_qualityModeled CAMS (Copernicus Atmosphere Monitoring Service) air quality: PM2.5, PM10, nitrogen dioxide, sulphur dioxide, ozone, carbon monoxide, dust, pollen, and European/US AQI indic…No findings
Why it is in this group
- The name "openmeteo_get_air_quality" says "get": a word for reading.
Description, as the server wrote it Modeled CAMS (Copernicus Atmosphere Monitoring Service) air quality: PM2.5, PM10, nitrogen dioxide, sulphur dioxide, ozone, carbon monoxide, dust, pollen, and European/US AQI indices. This is modeled grid data, not measured station readings — for measured data, use openaq-mcp-server. Forecast horizon up to 7 days, with optional past_days (up to 92) for recent history — or start_date and end_date together for an archive range; the CAMS global archive begins in August 2022, and earlier dates return rows of nulls. One window per call: a date range is mutually exclusive with forecast_days and past_days, and needs both ends — a lone start_date or end_date is rejected. Common variables: pm2_5, pm10, carbon_monoxide, nitrogen_dioxide, sulphur_dioxide, ozone, dust, european_aqi, us_aqi, alder_pollen, birch_pollen, grass_pollen, mugwort_pollen, olive_pollen, ragweed_pollen. Pollen is modeled for Europe only, and only in pollen season — elsewhere the pollen values come back null, and the notice names them. Set current_variables for pollutant and AQI values at this instant — returned as a current object plus a current_units map, and enough on its own without hourly_variables; the block’s interval field is its aggregation interval in seconds (3600 on this endpoint). A wide window — a large past_days or date range plus many variables — produces thousands of records; these spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_climateLong-range climate projections from bias-corrected daily CMIP6 models, covering 1950-01-01 to 2050-12-31 at any coordinate.No findings
Why it is in this group
- The name "openmeteo_get_climate" says "get": a word for reading.
Description, as the server wrote it Long-range climate projections from bias-corrected daily CMIP6 models, covering 1950-01-01 to 2050-12-31 at any coordinate. Answers "what will conditions look like through 2050?" — the future-projection counterpart to openmeteo_get_historical (the observed archive, what happened). Daily resolution only. Available models: CMCC_CM2_VHR4, FGOALS_f3_H, HiRAM_SIT_HR, MRI_AGCM3_2_S, EC_Earth3P_HR, MPI_ESM1_2_XR, NICAM16_8S. A model name outside that list is sent upstream rather than rejected here, so a model Open-Meteo adds later still works; if upstream rejects the request, the error names the offending model on its own rather than the whole requested list. With 2+ models each variable appears once per model with the model name as suffix (e.g. temperature_2m_max_CMCC_CM2_VHR4); a single or omitted model returns plain variable names. Not all models carry all variables — missing combinations return null. Multi-decade daily pulls across several models produce thousands of records and spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_elevationTerrain elevation from the Copernicus Digital Elevation Model (~90m resolution) for one or more coordinate pairs.No findings
Why it is in this group
- The name "openmeteo_get_elevation" says "get": a word for reading.
Description, as the server wrote it Terrain elevation from the Copernicus Digital Elevation Model (~90m resolution) for one or more coordinate pairs. Accepts up to 1,000 pairs and samples the first 100 in one upstream request; when more were submitted, unprocessed_count says how many remain and next_offset is where to resume — resubmit latitudes.slice(next_offset) and longitudes.slice(next_offset) of the arrays just sent, until next_offset is null. Open-Meteo counts each sampled pair as one call against its per-IP limit of 600 a minute, so a seventh full slice inside one minute comes back rate_limited — space later slices about a minute apart. Useful for geographic context, elevation-adjusted weather interpretation, or route planning. A point the DEM has no value for (latitude 90) returns elevation_m null; the other points in the call are unaffected.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_ensembleProbabilistic ensemble weather forecast — up to 64 ensemble members, up to 35 days ahead with optional past_days (0–92).1 finding
Why it is in this group
- The name "openmeteo_get_ensemble" says "get": a word for reading.
Findings
- Info
The description is 2,459 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...preview instead. At least one of hourly_variables or daily_variables is required."
Description, as the server wrote it Probabilistic ensemble weather forecast — up to 64 ensemble members, up to 35 days ahead with optional past_days (0–92). Most models end within 16 days; a model's columns are null past its horizon, and the response notice names where its data ends. Each member's values appear as separate columns named with a member suffix (e.g. temperature_2m_member01, temperature_2m_member02). Use the spread across members to compute exceedance probabilities, quantify forecast uncertainty, and build decision thresholds. Available models: ecmwf_ifs025_ensemble (51 members, global 0.25°), ecmwf_aifs025_ensemble (51, global 0.25°), ecmwf_ifs_europe_ensemble (51, Europe 9 km), ecmwf_aifs_europe_ensemble (51, Europe 31 km), google_weathernext2_ensemble (64, global 0.25°), ncep_gefs_seamless (31, global blend), ncep_gefs025 (31, global 0.25°), ncep_gefs05 (31, global 50 km, 35 days), ncep_aigefs025 (31, global 0.25°), icon_seamless_eps (20–40, global/Europe blend), icon_global_eps (40, global 26 km), icon_eu_eps (40, Europe 13 km), icon_d2_eps (20, Central Europe 2 km), gem_global_ensemble (21, global 0.25°), bom_access_global_ensemble (18, global 40 km), ukmo_global_ensemble_20km (18, global 20 km), ukmo_uk_ensemble_2km (3, UK 2 km), meteoswiss_icon_ch1_ensemble (11, Central Europe 1 km), meteoswiss_icon_ch2_ensemble (21, Central Europe 2 km). Omit models to use ecmwf_ifs025_ensemble. Name several models, comma-separated, to compare them in one call: every column then also ends in its model's name (temperature_2m_member01_ncep_gefs025), and the notice gives each model's member count. A regional model returns no data outside the area it covers. Requested alone, that comes back as an input error naming the coverage gap, not a transient failure, so pick a global model or move the coordinate inside the region rather than retrying; requested beside a model that covers the coordinate, it is left out of the response and the notice says so. A model name this list does not carry is still sent upstream, so a newly added one keeps working. Large multi-member, multi-day pulls produce thousands of records and spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead. At least one of hourly_variables or daily_variables is required.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_floodGloFAS (Global Flood Awareness System) daily river discharge (m³/s) from the GloFAS 0.05° grid cell nearest the given coordinates — no river ID needed.1 finding
Why it is in this group
- The name "openmeteo_get_flood" says "get": a word for reading.
Findings
- Info
The description is 2,872 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...meteo_dataframe_query. With canvas disabled it returns a bounded preview instead."
Description, as the server wrote it GloFAS (Global Flood Awareness System) daily river discharge (m³/s) from the GloFAS 0.05° grid cell nearest the given coordinates — no river ID needed. The response's latitude and longitude name that cell. It is not reliably on the river intended: a point near a confluence, a pair of parallel channels, or a bank can resolve to a cell with little flow. When the value is far below what the named river carries, step the coordinate 0.05° across the channel and compare the values. One mode per call: forecast_days for the outlook, or start_date and end_date together for a date range. A date range accepts dates from 1984-01-01, but GloFAS discharge begins 1997-01-01 — every model returns null before it. The two modes are mutually exclusive, and a date range needs both ends — a lone start_date or end_date is rejected. forecast_days accepts up to 210, but the current GloFAS run sets how far the data reaches (about six months ahead); later days come back null and the notice names where the data ends. What a date range holds depends on the model. Omitting models reads seamless_v4: consolidated_v4 reanalysis before 2023-08-05, then forecast-run discharge from 2023-08-05 on, so a range crossing that date changes source mid-series. Set models to pin a source: seamless_v4 (default — consolidated_v4 reanalysis before 2023-08-05, forecast_v4 runs from 2023-08-05 into the live forecast), consolidated_v4 (reanalysis from 1997-01-01 through 2025-05-31; null outside that span and on every forecast_days call), forecast_v4 (forecast runs from 2023-06-01 into the live forecast; null before). consolidated_v4 is the only way to read reanalysis for 2023-08-05 through 2025-05-31. With 2+ models every daily column is suffixed with the model name (river_discharge_consolidated_v4). Available daily variables: "river_discharge" (the daily discharge value; the mean across ensemble members is "river_discharge_mean"), and the ensemble statistics "river_discharge_mean", "river_discharge_median", "river_discharge_min", "river_discharge_max", "river_discharge_p25" (25th percentile), and "river_discharge_p75" (75th percentile). The statistics carry spread across ensemble members on forecast-run days — the forecast_days outlook, and date-range days from 2023-08-05 under seamless_v4 or forecast_v4. On reanalysis days (seamless_v4 before 2023-08-05, consolidated_v4 through 2025-05-31) they repeat river_discharge and are not uncertainty estimates. Returns null for coordinates far from any river or in areas without GloFAS coverage. A wide date range produces thousands of daily records and spills to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled it returns a bounded preview instead.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_forecastWeather forecast for coordinates: hourly and/or daily variables for up to 16 days ahead, with optional past_days (up to 92) for recent history.No findings
Why it is in this group
- The name "openmeteo_get_forecast" says "get": a word for reading.
Description, as the server wrote it Weather forecast for coordinates: hourly and/or daily variables for up to 16 days ahead, with optional past_days (up to 92) for recent history. Use past_days instead of openmeteo_get_historical for dates within the last week, since the archive’s ERA5 components lag by about a week. Returns per-timestamp records — each hourly entry contains a "time" field (ISO 8601) plus one key per requested variable; each daily entry contains a "time" field (YYYY-MM-DD) plus requested variables. Common hourly variables: temperature_2m, precipitation, wind_speed_10m, relative_humidity_2m, cloud_cover, uv_index, apparent_temperature, precipitation_probability, weather_code, surface_pressure, visibility, wind_direction_10m, wind_gusts_10m, dew_point_2m. Common daily variables: temperature_2m_max, temperature_2m_min, precipitation_sum, wind_speed_10m_max, sunrise, sunset, uv_index_max, precipitation_hours, weather_code. Set current_variables for conditions at this instant — Open-Meteo serves those from 15-minute model data, which is more precise than picking the nearest hourly row, and the response carries a current object plus a current_units map. Set models to compare deterministic models side by side (e.g., ["ncep_gfs_seamless", "ecmwf_ifs025", "dwd_icon_seamless"]) — where they disagree, the forecast is uncertain. With 2+ models every hourly and daily key carries the model name as a suffix (temperature_2m_ecmwf_ifs025); with models omitted the data is Open-Meteo’s best_match blend. A wide window — a large past_days plus many hourly variables — produces thousands of records; these spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead. At least one of current_variables, hourly_variables, or daily_variables is required.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_historicalHistorical weather from the Open-Meteo reanalysis archive (1940–present).No findings
Why it is in this group
- The name "openmeteo_get_historical" says "get": a word for reading.
Description, as the server wrote it Historical weather from the Open-Meteo reanalysis archive (1940–present). Requires start_date and end_date (ISO 8601 date, e.g., "2024-07-01"). With models omitted the archive answers from Best Match, which blends IFS HRES, ERA5, and ERA5-Land seamlessly — so the source varies by date and no single update lag describes the response. Set models to pin a consistent source for a multi-decade series: the ERA5 family updates daily with about a week of delay, while IFS HRES has none, so for the last week either request models: ["ecmwf_ifs"] or use openmeteo_get_forecast with past_days. Available models: best_match (default, blends IFS HRES + ERA5 + ERA5-Land), ecmwf_ifs (global 9 km, updated every 6 hours, no delay), ecmwf_ifs_analysis_long_window (global 9 km, daily, 2 days delay), era5_seamless (ERA5 and ERA5-Land combined), era5 (global 0.25° (~25 km), daily, about a week delay), era5_land (global 0.1° (~11 km), daily, about a week delay), era5_ensemble (global 0.5° (~55 km), daily, about a week delay), cerra (Europe only, 5 km, no real-time updates). Uses the same variable names as the forecast API for direct comparison. Large date ranges (multi-year hourly) produce thousands of records — these spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true; inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead. At least one of hourly_variables or daily_variables is required.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_get_marineMarine wave and ocean conditions for a coastal or ocean coordinate: wave height, wave period, wave direction, wind-wave height, swell height, sea-surface temperature.1 finding
Why it is in this group
- The name "openmeteo_get_marine" says "get": a word for reading.
Findings
- Info
The description is 2,590 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...least one of current_variables, hourly_variables, or daily_variables is required."
Description, as the server wrote it Marine wave and ocean conditions for a coastal or ocean coordinate: wave height, wave period, wave direction, wind-wave height, swell height, sea-surface temperature. Forecast horizon up to 16 days, with optional past_days (up to 92) for recent history — or start_date and end_date together for an archive range, which returns real wave values back to at least 2022. One window per call: a date range is mutually exclusive with forecast_days and past_days, and needs both ends — a lone start_date or end_date is rejected. With models omitted the data is Open-Meteo's best_match blend, whose wave data runs about 9 days — later days come back null and the notice says where the data ends. Set models to reach further (ncep_gfswave025 runs 16 days, ecmwf_wam about 15) or to compare wave models side by side; with 2+ models every hourly and daily key carries the model name as a suffix (wave_height_ecmwf_wam). Returns per-timestamp records — each entry contains a "time" field plus one key per requested variable. Best for open-ocean and coastal exposed points — sheltered water such as a sound or bay returns near-zero wave values, and a land point well inland returns null values, which the notice reports. A land point near the coast is answered from a nearby sea cell with real values and no notice, so check the response latitude and longitude is the water you meant. Common hourly variables: wave_height, wave_direction, wave_period, wind_wave_height, wind_wave_direction, wind_wave_period, swell_wave_height, swell_wave_direction, swell_wave_period. Common daily: wave_height_max, wave_direction_dominant, wave_period_max. Note: ocean_current_velocity is null for non-open-ocean coordinates. Set current_variables for conditions at this instant — Open-Meteo serves those from 15-minute model data, and the response carries a current object plus a current_units map, alongside either window. length_unit "imperial" returns heights in ft, wind_speed_unit sets the ocean_current_velocity unit, and temperature_unit the sea_surface_temperature unit — converted upstream, with every unit read from the *_units maps. A wide window — a large past_days or date range plus many variables — produces thousands of records; these spill to a DataCanvas when canvas is enabled, returning canvas_id and table_name with truncated: true — inspect the staged columns with openmeteo_dataframe_describe, then query the full set with openmeteo_dataframe_query. With canvas disabled they return a bounded preview instead. At least one of current_variables, hourly_variables, or daily_variables is required.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
openmeteo_search_locationsResolve a place name to ranked coordinate matches with country, region, elevation, timezone, and population.No findings
Why it is in this group
- The name "openmeteo_search_locations" says "search": a word for reading.
Description, as the server wrote it Resolve a place name to ranked coordinate matches with country, region, elevation, timezone, and population. Required prerequisite for name-based queries — all weather tools take latitude/longitude, not place names. Search by a bare place name (city, region, or landmark); never fold a qualifier into it — pass "Baoding", not "Baoding Hebei", and "Paris", not "Paris, France". To disambiguate places that share a name, set the country input (ISO 3166-1 alpha-2, e.g. "US") and/or read the admin1 and country fields on each ranked result — admin1 is a result field for choosing among matches, not a search input. Returns up to count matches (default 5, at most 100), ranked by population and relevance.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://open-meteo.caseyjhand.com/mcp: tools/list returned 11 tools to an anonymous client, including openmeteo_dataframe_query (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "openmeteo_dataframe_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "openmeteo_dataframe_query" says "query": a word for reading.
The description is 2,590 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...least one of current_variables, hourly_variables, or daily_variables is required."
The description is 2,459 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...preview instead. At least one of hourly_variables or daily_variables is required."
The description is 2,872 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...meteo_dataframe_query. With canvas disabled it returns a bounded preview instead."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:openmeteo_dataframe_queryChanges thingsinputSchema
- Changed:openmeteo_get_climateOnly readsinputSchema
- Changed:openmeteo_get_ensembleOnly readsdescriptioninputSchema
- Changed:openmeteo_get_forecastOnly readsinputSchema
- Changed:openmeteo_get_historicalOnly readsinputSchema
- Changed:openmeteo_get_marineOnly readsdescriptioninputSchema
- Changed:openmeteo_search_locationsOnly readsdescriptioninputSchema
Tools6 changed.~6 changedView diff
- Changed:openmeteo_dataframe_queryChanges thingsdescriptioninputSchema
- Changed:openmeteo_get_climateOnly readsinputSchema
- Changed:openmeteo_get_ensembleOnly readsinputSchema
- Changed:openmeteo_get_floodOnly readsdescriptioninputSchema
- Changed:openmeteo_get_forecastOnly readsinputSchema
- Changed:openmeteo_get_historicalOnly readsinputSchema
Tools4 changed.~4 changedView diff
- Changed:openmeteo_get_floodOnly readsdescriptioninputSchema
- Changed:openmeteo_get_forecastOnly readsdescriptioninputSchema
- Changed:openmeteo_get_historicalOnly readsdescriptioninputSchema
- Changed:openmeteo_get_marineOnly readsdescriptioninputSchema
Tools6 changed.~6 changedView diff
- Changed:openmeteo_dataframe_queryChanges thingsinputSchema
- Changed:openmeteo_get_elevationOnly readsdescriptioninputSchema
- Changed:openmeteo_get_floodOnly readsdescriptioninputSchema
- Changed:openmeteo_get_forecastOnly readsdescriptioninputSchema
- Changed:openmeteo_get_historicalOnly readsinputSchema
- Changed:openmeteo_get_marineOnly readsdescriptioninputSchema
Install
Pinned to version 0.6.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http open-meteo https://open-meteo.caseyjhand.com/mcpclaude mcp add --transport http open-meteo https://open-meteo.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__open-meteo__openmeteo_search_locations",
"mcp__open-meteo__openmeteo_get_elevation",
"mcp__open-meteo__openmeteo_get_forecast",
"mcp__open-meteo__openmeteo_get_historical",
"mcp__open-meteo__openmeteo_get_marine",
"mcp__open-meteo__openmeteo_get_air_quality",
"mcp__open-meteo__openmeteo_get_ensemble",
"mcp__open-meteo__openmeteo_get_flood",
"mcp__open-meteo__openmeteo_get_climate",
"mcp__open-meteo__openmeteo_dataframe_describe"
],
"ask": [
"mcp__open-meteo__openmeteo_dataframe_query"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as open-meteo. Review it before you use it.
Capability tags behind 2 rules
- mcp__open-meteo__openmeteo_dataframe_query private-data
- mcp__open-meteo__openmeteo_dataframe_describe private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/open-meteo-mcp-server/verify?hash=34142266413fc056f35462490f1e71d7e3e20dd7125d3c3e7b13f0c5ab39321d" | jq -e '.changed == false'Pinned hash 34142266413f, from Nov 18, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/open-meteo-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/open-meteo-mcp-server)Source: MCP Registry · repository. Synced Nov 18, 2026, 08:17 UTC.
open-meteo-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the open-meteo-mcp-server safe?
- No scan can promise that. What its definitions show: 11 tools, 1 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the open-meteo-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the open-meteo-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the open-meteo-mcp-server have?
- 11 tools: 1 write, 10 read. openmeteo_dataframe_query, openmeteo_search_locations, openmeteo_get_elevation, openmeteo_get_forecast, openmeteo_get_historical, openmeteo_get_marine, openmeteo_get_air_quality, openmeteo_get_ensemble and 3 more.
Does the open-meteo-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the open-meteo-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the open-meteo-mcp-server changed its tools?
- Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.