weathersight MCP server
io.weathersight/weathersightweathersight.iostreamable-httpv1.0.0Scanned
Historical weather and climate: 100+ years of station data, normals, extremes, and trends.
19 tools: 3 change things and 16 only read.
- Reads private data · 0
- Reads text others write · 19
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- 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 weathersight MCP server can do
The weathersight MCP server is published by weathersight.io, a domain the MCP Registry verified. It has 19 tools. It can create or change data (3 tools: bestplace, besttime and seasonal), but cannot delete data. 16 tools only read.
19 tools bring in text other people can write (anom, anomalies, bestplace and 16 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.0.
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.
19 tools
Changes things 3Claude Code: ask
bestplaceGiven a single week, month, or day, ranks locations whose weather best matches a set of criteria (most optional criteria met first; all MUST criteria satisfied by every result).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Given a single week, month, or day, ranks locations whose weather best matches a set of criteria (most optional criteria met first; all MUST criteria satisfied by every result). Filter by lat/lon+radius or countries. <br><b>When to use:</b> Answer 'where has the best weather for week/month/day X?' <br><b>Date format:</b> scope=day + time=YYYYMMDD (forecast); scope=week + time=MMDD; scope=month + time=MM. Defaults: week of today+14, month today+1, day today+1. <br><b>Performance:</b> Filter by area/countries to keep fast. <br><b>Prerequisites:</b> None; supply lat/lon+radius_km or a country list. <br><b>Investigate:</b> Rank places for a given time window. scope=day uses forecasts. <br><b>Augment:</b> Find the best destinations for a target week/month. <br><b>Notes:</b> Every criterion metric name is literal and fully qualified: the 'avg:' prefix, then the metric base (observation metrics keep their 'obs.' segment), then the attribute — e.g. avg:max_t.p50, avg:obs.rain.sum, avg:obs.is_rain.count. Dropping 'avg:' or 'obs.' is an error; the criteria parameter below lists every valid name. scope=day queries forecasts; week/month query the 1996-2025 historical baseline. Returns: scope, time, baseline, results, locid, location, criteria_met, criteria_met_count, record.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
besttimeGiven a location, ranks the weeks or months whose historical climatology best matches a set of weather criteria (most optional criteria met first; all MUST criteria satisfied by ev…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Given a location, ranks the weeks or months whose historical climatology best matches a set of weather criteria (most optional criteria met first; all MUST criteria satisfied by every result). <br><b>When to use:</b> Answer 'when is the best time to visit X for weather like Y?' Choose when_type=week or month over the 1996-2025 baseline. <br><b>Date format:</b> when_type: week|month|day. Historical basis only for week/month. <br><b>Performance:</b> Sub-second per location. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Rank a location's calendar by weather suitability. For a specific upcoming day's forecast, use /api/anom with period_type=FUTURE_DAY. <br><b>Augment:</b> Find the typical best window for an activity at a place. <br><b>Notes:</b> Every criterion metric name is literal and fully qualified: the 'avg:' prefix, then the metric base (observation metrics keep their 'obs.' segment), then the attribute — e.g. avg:max_t.p50, avg:obs.rain.sum, avg:obs.is_rain.count. Dropping 'avg:' or 'obs.' is an error; the criteria parameter below lists every valid name. For daily forecasts use /api/anom (period_type=FUTURE_DAY). Weekly/monthly forecasts are planned. Returns: location, baseline, when_type, results, time, criteria_met, criteria_met_count, record.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
seasonalSeasonal (monthly) forecast anomalies for the next six months, with the local climatology they are measured against.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Seasonal (monthly) forecast anomalies for the next six months, with the local climatology they are measured against. Each result gives, per metric: the ERA5 baseline mean (means), its interannual standard deviation (std), the predicted anomaly (anom, in degrees C / mm / km/h) and how unusual that is, both as standard deviations (norm) and as a percentile rank among the last 30 years (perc). <br><b>When to use:</b> Answer 'will next month be hotter/wetter than normal here?' or 'where is the coming season predicted to be most unusual?' <br><b>Date format:</b> ym_start and ym_end are YYYYMM, inclusive. For a single month set both to the same value. Defaults to next month through next month + 5. <br><b>Performance:</b> Filter by locid, ctryid or latlon+radius_km to keep fast; a whole-world month slice is about 4000 rows and fits in one page. <br><b>Prerequisites:</b> None; supply locid, name, latlon+radius_km, ctryid, or nothing at all for a global query. <br><b>Investigate:</b> Rank places by how abnormal the coming months look. Use sort=perc:obs.rain.sum for rainfall and sort=norm:max_t.mean for heat. <br><b>Augment:</b> Back claims about the coming season with the predicted anomaly and how it compares with the local 30-year normal. <br><b>Notes:</b> Monthly resolution only — for daily forecasts use typicalweather. The forecast is ECMWF SEAS5; its anomalies are relative to SEAS5's own 1991-2020 model climatology, so means + anom approximates rather than equals the predicted absolute. Returns: ym_start, ym_end, baseline, metrics, count, truncated, note, error, next_cursor, results, locid, location, ym, run_ymd, basis_type, means, std, anom, norm, perc, criteria_met, criteria_met_count.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
Only reads 16Show 16 read-only tools
anomReturns observations with 1991–2020 baseline comparisons at daily, weekly, or monthly granularity for a location and period.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns observations with 1991–2020 baseline comparisons at daily, weekly, or monthly granularity for a location and period. <br><b>When to use:</b> Graph or tabulate recent anomalies at a location for a specific period — e.g. 'how did last month compare to normal?' <br><b>Date format:</b> YYYYMMDD for ymd; use groupby (day/week/month) to control granularity. For 'last week' use YYYYMMDD of 7 days ago. For 'last month' use YYYYMM of prior month. <br><b>Performance:</b> Computed on demand; moderate speed. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Use after /anomalies or /breaking. Identifies a city of interest; provides per-day/week detail for drill-down. Combine groupby=DAY/FULL_DAY with a recent date range for 'recent days with departure from normal' queries. <br><b>Augment:</b> Provides the per-period anomaly series for prose ('temperatures were above normal for 12 of the past 14 days'). Returns: loc, ts, vals, N, vals_ts, baseline.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
anomaliesReturns precomputed anomalous observations for locations in a given time period and scope.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns precomputed anomalous observations for locations in a given time period and scope. <br><b>When to use:</b> Survey anomalous weather at regional or global scale quickly without specifying individual cities. <br><b>Date format:</b> YYYY[MM[DD]]: YYYY for annual anomalies (scope=year), YYYYMM for monthly (scope=month), YYYYMMDD for weekly or daily (scope=week/day). <br><b>Performance:</b> Fast — retrieves precomputed data. <br><b>Prerequisites:</b> None; global or country-filtered. Use /countries for country IDs. <br><b>Investigate:</b> Good early call to identify which locations experienced anomalies before drilling into specifics with /anom or /dailycomp. <br><b>Augment:</b> Use for a first-pass global scan to identify story-worthy anomalies before fetching per-location detail. Returns: anomalies, anomaly.locid, anomaly.lat, anomaly.long, anomaly.obs_start, anomaly.obs_end, anomaly.obs_dur, anomaly.base_start, anomaly.base_end, anomaly.base_dur, anomaly.obs_period, anomaly.base_period, anomaly.outliers, outlier.obs_metric, outlier.percentile, outlier.obs_N, outlier.obs_X, outlier.base_N, outlier.base_X, outlier.obs_val, outlier.base_val, outlier.base_mean, outlier.base_stddev, outlier.min, outlier.max, outlier.max_key, outlier.min_key, outlier.obs_min_key, outlier.obs_max_key.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
breakingReturns anomalous weather conditions (breaking news) across the world or specified countries in the very recent past (observations) or immediate future (forecast).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns anomalous weather conditions (breaking news) across the world or specified countries in the very recent past (observations) or immediate future (forecast). <br><b>When to use:</b> First call when looking for current or upcoming notable weather events globally or by country. <br><b>Date format:</b> No date params — always returns the most recent ~3 days of observations (breaking_type=obs) or next 7 days of forecast (breaking_type=forecast). <br><b>Performance:</b> Fast — retrieves precomputed anomaly snapshots. <br><b>Prerequisites:</b> Use /countries to get country IDs for filtering. <br><b>Investigate:</b> Start here for any 'what's happening right now?' or 'what's forecast this week?' query; follow up with /anom or /dailycomp for per-location detail. <br><b>Augment:</b> Primary source for identifying breaking weather news stories globally; use ctryid to narrow scope by country. Returns: anomalies, anomaly.locid, anomaly.name, anomaly.city, anomaly.country, anomaly.lat, anomaly.lon, anomaly.geohash, anomaly.elevation, anomaly.obs_start, anomaly.obs_end, anomaly.obs_dur, anomaly.pt, anomaly.anomalies, outlier.obsm, outlier.comps, comp.obsm_f, comp.oq, comp.bq, comp.scope, comp.val, comp.bval, comp.min, comp.max, comp.med, comp.mean, comp.std, comp.min_dt, comp.max_dt, comp.intensity, comp.intensity_f, comp.rp, comp.summary, comp.period, comp.base_N, comp.N, comp.ut, comp.start, comp.end.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
climatecompsReturns monthly distributions of selected metrics for locations compared against a baseline period.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns monthly distributions of selected metrics for locations compared against a baseline period. <br><b>When to use:</b> Compute normalized and absolute deviations from a baseline, inter-annual and intra-annual variations within months and seasons. Check base_N and obs_N to assess data completeness. <br><b>Date format:</b> obs_years as YYYY or YYYY-YYYY range; months as MM or MM-MM (e.g. '06', '06-08', 'All' for annual). <br><b>Performance:</b> Bulk query — can be slow for global or large-area queries. Filter with locids, lat_lon/radius_km, or countries. <br><b>Prerequisites:</b> Use /location to obtain locids first for point queries. <br><b>Investigate:</b> Use to compare a recent season or year against the long-term baseline across many locations simultaneously. Combine with /climatetrends for trend context. <br><b>Augment:</b> Identifies which locations had the most anomalous season compared to their historical distribution. <br><b>Notes:</b> Metric format: 'max_t' = distribution of daily Maximum Temperature over the period; 'max_t.means' = distribution of annual means of max_t (1 value per year); 'rain_sum' (accumulations) and 'obs.is_thunderstorm' (counts) follow the same pattern. Returns: results, comp.locid, comp.geohash, comp.lat, comp.lon, comp.elev, comp.area, comp.country, comp.src_type, comp.metric, comp.obs_years, comp.base_years, comp.month, comp.obs_N, comp.base_N, comp.obs, comp.base, comp.obs.{q} / comp.base.{q}.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
climatetrendsReturns monthly timeseries of selected climate trend metrics for one or more locations, suitable for long-term trend analysis.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns monthly timeseries of selected climate trend metrics for one or more locations, suitable for long-term trend analysis. <br><b>When to use:</b> Retrieve long-term monthly timeseries for statistical trend analysis across any number of locations including globally. Use num_years and avg_N to filter sparse records. <br><b>Date format:</b> years as YYYY- range (e.g. '1975-' for 1975 to present); months as MM or MM-MM range (e.g. '06' for June, '06-08' for June–August, 'All' for annual). <br><b>Performance:</b> Bulk query — can be slow for global or many-location queries. Filter with locids, lat_lon/radius_km, or countries to improve speed. <br><b>Prerequisites:</b> Use /location to obtain locids first for point queries. <br><b>Investigate:</b> Use for global or regional trend analysis. Metric name format: 'agg_func:metric_id.attribute' (e.g. 'avg:max_t.p50'). Check num_years to confirm data completeness before citing a trend. <br><b>Augment:</b> Backs trend claims with long-term data across many locations (e.g. 'temperatures rising across Southeast Asia'). <br><b>Notes:</b> Example metrics: avg:max_t.p50, avg:obs.temp.mean, sum:obs.is_rain.count. See /api/metrics for full list. Returns: results, trend.locid, trend.geohash, trend.lat, trend.lon, trend.elev, trend.area, trend.country, trend.src_type, trend.metric, trend.years, trend.month, trend.num_years, trend.avg_N, trend.mvals, trend.mvals.xvals, trend.mvals.yvals_by_metric.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
compareCompares a location's observed weather period against the corresponding periods in a historical baseline distribution.Reads text others writeNo findings
Why it is in this group
- The name "compare" says "compare": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compares a location's observed weather period against the corresponding periods in a historical baseline distribution. <br><b>When to use:</b> Quantify how extreme a specific period was across all metrics at once — e.g. how anomalous was March 2025 at New York vs the 1991–2020 baseline. <br><b>Date format:</b> YYYY[MM[DD]]: YYYYMMDD for a specific day or short window (period_type DAY/WEEK), YYYYMM for a month (period_type MONTH), YYYY for an annual comparison (period_type YEAR). <br><b>Performance:</b> Computed on demand; fast for short periods. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Best for 'how unusual was [period] at [location]?' — returns percentile and z-score across all metrics simultaneously. Set baseline_offset=1 for the standard 1991–2020 baseline. <br><b>Augment:</b> Provides the precise statistical framing ('the hottest March in 30 years') before describing the anomaly in prose. Returns: comparisons, comparison.locid, comparison.lat, comparison.long, comparison.obs_start, comparison.obs_end, comparison.obs_dur, comparison.base_start, comparison.base_end, comparison.base_dur, comparison.obs_period, comparison.base_period, comparison.outliers, outlier.obs_metric, outlier.percentile, outlier.obs_N, outlier.obs_X, outlier.base_N, outlier.base_X, outlier.obs_val, outlier.base_val, outlier.base_mean, outlier.base_stddev, outlier.min, outlier.max, outlier.max_key, outlier.min_key, outlier.obs_min_key, outlier.obs_max_key.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
countriesReturns countries with their canonical country IDs used in all other API calls.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns countries with their canonical country IDs used in all other API calls. <br><b>When to use:</b> Resolve country names to canonical IDs, or obtain the full list of supported countries. This list rarely changes. <br><b>Performance:</b> Fast — static data; safe to cache across calls. <br><b>Prerequisites:</b> None. <br><b>Investigate:</b> Call once if country-level filtering is needed; cache the result for the session. <br><b>Augment:</b> Fetch country IDs before making country-filtered calls to /anomalies or /breaking. Returns: countries, country.ctryid, country.name, country.regions.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
dailycompReturns per-day observed values with percentiles and z-scores vs a sliding N-day window over a historical baseline.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns per-day observed values with percentiles and z-scores vs a sliding N-day window over a historical baseline. <br><b>When to use:</b> Graph heatwaves, cold spells, and other streaks by showing daily departures from normal. Also compare two separate periods or locations using z-scores or percentiles for normalized severity. <br><b>Date format:</b> YYYYMMDD for ymd_start and ymd_end. Keep ranges ≤30 days for fast response; up to 90 days is feasible. <br><b>Performance:</b> Computed on demand; slower for long date ranges. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Best for detailed day-by-day anomaly investigation once approximate dates and location are known. Use separate calls for two periods to compare heatwave severity via z-score. Do NOT use for ranking top-N events across years — call /events with criteria for that and post-process the response. <br><b>Augment:</b> Provides the daily series needed to describe the arc of a heatwave or cold snap in a news narrative. Returns: locid, lat, lon, dates, num_years, avg_coverage, metrics, metrics.{key}.values, metrics.{key}.pcts, metrics.{key}.sigmas, metrics.{key}.p1 … p99, metrics.{key}.bmin / bmax, metrics.{key}.mean, metrics.{key}.stddev, metrics.{key}.coverage.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
degreedaysReturns cumulative degree-day indicators (heating/cooling/growing) for a location and period using ERA5 reanalysis data.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns cumulative degree-day indicators (heating/cooling/growing) for a location and period using ERA5 reanalysis data. <br><b>When to use:</b> Estimate energy demand anomalies or agricultural stress in a recent or upcoming period. <br><b>Date format:</b> YYYYMMDD for ymd_start and ymd_end. Maximum interval is 14 days per call. <br><b>Performance:</b> Computed on demand using ERA5; moderate speed. Keep intervals to ≤14 days. <br><b>Prerequisites:</b> Requires lat/lon directly — no locid needed. <br><b>Investigate:</b> Use when the query involves power grid strain or energy demand. For forecast context, use future ymd dates. <br><b>Augment:</b> Adds quantitative energy-demand context to heatwave or cold snap stories. Returns: meta, indicators.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
eventsFinds days matching one or more compound weather conditions (e.g.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Finds days matching one or more compound weather conditions (e.g. hot + humid, rainy + windy) for a location. Returns up to 5000 most-recent matching events plus the total count. <br><b>When to use:</b> Count occurrences of compound weather events across years, study extreme or unusual day combinations, or identify streaks of such events. <br><b>Date format:</b> year_start/year_end as YYYY; month_day_start/month_day_end as MMDD for seasonal filtering within each year. <br><b>Performance:</b> Computed on demand; returns up to 5000 most-recent matches. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Use when the query involves compound conditions — 'how many days had both extreme heat and thunderstorms?' Combine numeric and condition metrics with AND/OR logic. <br><b>Augment:</b> Provides event frequency counts for framing rarity in a story ('only 3 such days in the past 20 years'). <br><b>Notes:</b> Numeric metrics, with unit and valid absolute range: dewp (-30 to 35 °C), gust (0 to 300 km/hr), max_t (-90 to 55 °C), max_wind (0 to 250 km/hr), min_t (-90 to 40 °C), rain (0 to 600 mm), snow (0 to 100 mm), temp (-90 to 50 °C), wind (0 to 200 km/hr). Condition metrics: is_fog, is_hail, is_rain, is_snow, is_thunderstorm. No other metrics are supported. Do not specify lower or upper bound when dealing with absolutes unless it is required. Unspecified bounds default to the metric's full range, and absolute bounds outside that range make the request invalid. Returns: locid, name, error, total_events, events, datestamp, max_t, max_t_complete, min_t, min_t_complete, rain, rain_complete, snow, temp, dewp, wind, max_wind, gust, conditions, criteria_met.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
extremesReturns extreme value analysis (return periods) for a specified location and metric.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns extreme value analysis (return periods) for a specified location and metric. <br><b>When to use:</b> Quantify the statistical rarity of a record or near-record value. Typically called after other APIs establish that an observation is anomalous. <br><b>Performance:</b> Computed on demand; moderate speed. <br><b>Prerequisites:</b> Use /location to obtain a locid first. Prefer level='area' over 'city' for better recall and longer period of record. <br><b>Investigate:</b> Use after /recentextremes or /anom establishes a high value; provides the return-period framing ('a once-in-50-year event'). <br><b>Augment:</b> Provides the statistical rarity framing needed for record-event stories. Try both src_types 'Obs' and 'ERA5' for non-US locations to account for discontinuous station records. Returns: locid, period, months_covered, window_size, N, coverage_pct, results, result.metric, result.value, result.return_period.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
locationReturns meta information for a location given a name, locid, or lat/lon.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns meta information for a location given a name, locid, or lat/lon. <br><b>When to use:</b> Obtain the canonical locid needed by all location-specific API calls. Typically the first call in any workflow. <br><b>Performance:</b> Fast — precomputed lookup. <br><b>Prerequisites:</b> None — this is the entry point. <br><b>Investigate:</b> Call first whenever the user names a city or region; cache the locid for all subsequent calls in the session. Use 'City, State Country' format (e.g. 'Austin TX USA'). <br><b>Augment:</b> Resolve city names from the article to locids early; reuse them throughout augmentation to avoid repeated name lookups. Returns: name, locid, friendly, lat, long, country, icao, elevation, timezone, wmo.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
metricsReturns the catalogue of all supported weather metric identifiers with units and categories.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns the catalogue of all supported weather metric identifiers with units and categories. <br><b>When to use:</b> Resolve metric IDs to human-friendly names, units, and categories. Call once and cache per session. <br><b>Performance:</b> Fast — static data; safe to cache for the lifetime of a session. <br><b>Prerequisites:</b> None. <br><b>Investigate:</b> Call once at session start; use metric.id as a lookup key throughout the conversation. <br><b>Augment:</b> Translate metric IDs into readable labels for article text and chart axes. Returns: metrics, metric.id, metric.name, metric.cat, metric.type, metric.dist.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
recentextremesReturns recent weather records (all-time or period-of-record extremes) for the world or specified countries.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns recent weather records (all-time or period-of-record extremes) for the world or specified countries. <br><b>When to use:</b> Find which locations have broken or nearly broken records in a recent date window. Set history_years ≥ 15 to ensure a meaningful period of record. <br><b>Date format:</b> YYYYMMDD for ymd_start and ymd_end. Keep windows ≤ 3 months per call for reasonable performance. <br><b>Performance:</b> Computed on demand; slower for large date ranges. Start with scope='monthly' or 'yearly'; fall back to 'weekly' for near-records. <br><b>Prerequisites:</b> Use /countries for country IDs; use /location for locids. <br><b>Investigate:</b> Use after /breaking identifies a record-breaking event to get precise extreme-value context. For US locations use period_type='DAY'; for non-US use 'FULL_DAY'. Hourly-derived metrics (wet bulb, wind gusts) for non-US require period_type='DAY'. <br><b>Augment:</b> Provides the 'record' framing for a story — 'hottest day ever recorded at this station.' Note: FULL_DAY and DAY expose different metric sets. Returns: results, extreme.locid, extreme.name, extreme.country_code, extreme.lat, extreme.lon, extreme.elev, extreme.period_type, extreme.metric, extreme.ymd, extreme.anomaly_type, extreme.scope, extreme.value, extreme.history_years.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
timeseriesReturns aggregated metric values as a yearly or monthly timeseries for a location.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns aggregated metric values as a yearly or monthly timeseries for a location. <br><b>When to use:</b> Detect long-term trends and compute statistical significance (r-squared, p-value). Best suited for multi-decade spans. <br><b>Date format:</b> mm_dd_start/mm_dd_end as MMDD (day-of-year window, not a calendar year); year_start/year_end as YYYY. Note: Use mm_dd_start/mm_dd_end as MM when months are specified and MMDD when week-level granularity is needed. When day-level info is needed use /events or /dailycomp. <br><b>Performance:</b> Computed on demand; slower for large date ranges or many metrics. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Use for trend analysis ('Is max temperature at location X increasing over decades?'). Combine with r-squared post-processing for significance. <br><b>Augment:</b> Provides decadal trend context alongside current anomalies ('temperatures have risen 1.5°C over 40 years'). Returns: locid, lat, lon, xvals, yvals.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
typicalweatherReturns statistical distributions of weather attributes (temperature, precipitation, wind, etc.) for a location and time period.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Returns statistical distributions of weather attributes (temperature, precipitation, wind, etc.) for a location and time period. <br><b>When to use:</b> Establish the climatological baseline — what is 'normal' for this location and period. Use before discussing anomalies. <br><b>Date format:</b> YYYY[MM[DD]]: YYYYMMDD for a specific week, YYYYMM for a month, YYYY for a seasonal or annual overview. Note: YYYYMMDD does not give info about daily obs. If a date is specified it corresponds to the week. Use /events for daily history. <br><b>Performance:</b> Computed on demand; moderate speed. Avoid date spans wider than one year. <br><b>Prerequisites:</b> Use /location to obtain a locid first. <br><b>Investigate:</b> Good for grounding anomaly claims — e.g. 'Is 35°C in July unusual for Madrid?' Check distributions before asserting extremeness. <br><b>Augment:</b> Use to provide climatological context before describing observed anomalies in an article. Returns: duration, observations, conditions, probs, pcps, means, >>.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: 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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write19
- 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:14 UTC, unchanged since Nov 13, 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
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://weathersight.io/.well-known/oauth-protected-resource
- Authorization servers
- https:/weathersight.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://weathersight.io/api/mcp: tools/list returned 19 tools to an anonymous client, including bestplace (write), besttime (write), seasonal (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 9 to 3
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 removed, 1 changed.−7 removed~1 changedView diff
- Removed:climatetwins
- Removed:dailycountbyloc
- Removed:dailycountbyyear
- Removed:dailyfcasteval
- Removed:dailyweather
- Removed:fcastevalbygroup
- Removed:fcastevalbylocation
- Changed:eventsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 3.View diff
- Tools that change things, listed without credentials: 9 to 3
Tools5 added.+5 addedView diff
- Added:climatetwinsOnly reads
- Added:dailycountbylocChanges things
- Added:dailycountbyyearChanges things
- Added:dailyfcastevalChanges things
- Added:dailyweatherChanges things
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http weathersight https://weathersight.io/api/mcpclaude mcp add --transport http weathersight https://weathersight.io/api/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__weathersight__anom",
"mcp__weathersight__anomalies",
"mcp__weathersight__breaking",
"mcp__weathersight__climatecomps",
"mcp__weathersight__climatetrends",
"mcp__weathersight__compare",
"mcp__weathersight__countries",
"mcp__weathersight__dailycomp",
"mcp__weathersight__degreedays",
"mcp__weathersight__events",
"mcp__weathersight__extremes",
"mcp__weathersight__location",
"mcp__weathersight__metrics",
"mcp__weathersight__recentextremes",
"mcp__weathersight__timeseries",
"mcp__weathersight__typicalweather"
],
"ask": [
"mcp__weathersight__bestplace",
"mcp__weathersight__besttime",
"mcp__weathersight__seasonal"
],
"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 weathersight. Review it before you use it.
Capability tags behind 19 rules
- mcp__weathersight__anom untrusted-input
- mcp__weathersight__anomalies untrusted-input
- mcp__weathersight__bestplace untrusted-input
- mcp__weathersight__besttime untrusted-input
- mcp__weathersight__breaking untrusted-input
- mcp__weathersight__climatecomps untrusted-input
- mcp__weathersight__climatetrends untrusted-input
- mcp__weathersight__compare untrusted-input
- mcp__weathersight__countries untrusted-input
- mcp__weathersight__dailycomp untrusted-input
- mcp__weathersight__degreedays untrusted-input
- mcp__weathersight__events untrusted-input
- mcp__weathersight__extremes untrusted-input
- mcp__weathersight__location untrusted-input
- mcp__weathersight__metrics untrusted-input
- mcp__weathersight__recentextremes untrusted-input
- mcp__weathersight__seasonal untrusted-input
- mcp__weathersight__timeseries untrusted-input
- mcp__weathersight__typicalweather untrusted-input
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.weathersight/weathersight/verify?hash=0c19dfe252e78349fb6f0f70b8512dc1357262c4baf5ddeff9924c5ea8333c8f" | jq -e '.changed == false'Pinned hash 0c19dfe252e7, from Nov 17, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.weathersight/weathersight/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.weathersight/weathersight)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.
weathersight MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the weathersight MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 3 of which can change, send or delete something, and 0 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 weathersight MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the weathersight 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 weathersight MCP server have?
- 19 tools: 3 write, 16 read. bestplace, besttime, seasonal, anom, anomalies, breaking, climatecomps, climatetrends and 11 more.
Does the weathersight MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the weathersight MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the weathersight MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.