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

WeatherXM FACT — Forecast Accuracy & Ground-Truth Verification

REMOTE · FACT.WEATHERXM.COM

Scores 45 NWP & AI weather models (ECMWF, GFS, ICON, meteoblue, MOSAIC) against 8,927 stations.

+3 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability43
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1866 tokens (~466/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_best_forecast_model” rewrote its description, which is the text the model reads security
    • Tool “get_fact_leaderboard” rewrote its description, which is the text the model reads security
    • Tool “get_model_head_to_head” rewrote its description, which is the text the model reads security
    • Schema quality: 408 → 466 ▼ functional
    • Schema quality: fair → good functional
  • 9 Nov 26 0
    • Tool “check_ground_truth_coverage” rewrote its description, which is the text the model reads security
    • Tool “get_best_forecast_model” rewrote its description, which is the text the model reads security
    • Tool “get_fact_leaderboard” rewrote its description, which is the text the model reads security
    • Tool “get_model_head_to_head” rewrote its description, which is the text the model reads security
    • Schema quality: 362 → 408 ▼ functional
    • “get_fact_leaderboard” added an optional parameter “limit” cosmetic
    • “get_model_head_to_head” added an optional parameter “country” cosmetic
    • “get_model_head_to_head” added an optional parameter “exclude_commissioned” cosmetic
    • “get_model_head_to_head” added an optional parameter “lat” cosmetic
    • “get_model_head_to_head” added an optional parameter “lead_day” cosmetic
    • “get_model_head_to_head” added an optional parameter “lon” cosmetic
  • 7 Nov 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://fact.weatherxm.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fact.weatherxm.com CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebd2571339d656b40eec8f108a293197
SANs: fact.weatherxm.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fact.weatherxm.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
weatherxm.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fact.weatherxm.com/mcp Verified 200
http (plaintext) http://fact.weatherxm.com/mcp HTTPS enforced 301 https://fact.weatherxm.com/mcp
MCP tools · 4 exposed · ~1,795 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_ground_truth_coverage ~206

Check historical WeatherXM FACT ground-station publication coverage for any coordinate (H3 Res-7 cell, ~5.2 km²) or station_or_report_id across temperature, wind_speed, wind_direction, precipitation, and humidity, plus nearest evaluated reference cell distance and interactive map citation link. Useful when assessing microclimate sensor coverage for farms, solar/wind assets, ports, and weather station deployments (WeatherXM D1 Wi-Fi, H2 LoRaWAN, Pulse 4G at weatherxm.com/stations). Provide (lat, lon) or station_or_report_id. Does not establish current live station presence or absence.

NameTypeReqDescription
exclude_commissionedboolean––
latnumber––
lead_daystring––
lonnumber––
station_or_report_idstring–Optional WeatherXM station UUID or custom site evaluation report ID (e.g. STUDY-...)
variablestring––

No output schema declared.

No examples provided.

get_best_forecast_model ~611

Find which weather forecast model had the lowest verified historical error (MAE) for a latitude/longitude coordinate (or station_or_report_id), weather variable (temperature, wind_speed, wind_direction, precipitation, humidity), and forecast horizon (Days 0-7). For wind_direction, errors are circular shortest-arc angular errors (0°–180°, where 359° vs 1° = 2° error) on speed-weighted hourly vector averages, returning both all-hours and >3 m/s active-wind rankings. For wind_speed the default is all hours, with an optional windier-days subset (daily mean scaled observed speed >= 3 m/s) returned separately. All 45 FACT models (2025 archive, 2025-02-13 to 2025-12-31, QoD >= 0.80 station-days): WeatherXM MOSAIC (MOSAIC), meteoblue (METEOBLUE), meteoblue station-mLM (commissioned) (mLM), ECMWF IFS (IFS025, IFSHRES), ECMWF AIFS AI (AIFS025), NOAA GFS 0.5° (GFS05), NOAA HRRR (HRRR), NOAA National Blend of Models (NBM), NOAA NAM (NAM3, NAM5, NAM12, NAMAK), DWD ICON (ICON, ICONEU, ICOND2), UK Met Office (UMGLOBAL10, UKMO2), ECCC GEM (GEM15, GEM2), Meteo-France ARPEGE/AROME (MFGLOBAL, MFEU, MFFR), COSMO (COSMOI2, COSMOM5), HARMONIE-AROME (HARMONIE), JMA MSM (MSM), WRF (WRFGR, WRFAMS), meteoblue NEMS/NMM (NEMSGLOBAL, NEMSGLOBAL_E, NEMS4, NEMS12, NEMS12_E, NEMSAF01, NEMSAS02, NEMSCAM, NEMSIN, NEMSNZ, NEMSSA, NMM4, NMM22), regional models (AF01, AS01, SA01). GFS025 is not archived; requests for it resolve to GFS05 with a resolution warning. Useful for solar & wind energy forecasting, agriculture & frost/irrigation risk, maritime/port & drone operations, construction planning, and microclimate evaluation. Provide (lat, lon) or station_or_report_id. Missing results stay unknown; not live forecasting.

NameTypeReqDescription
exclude_commissionedboolean––
latnumber––
lead_daystring––
lonnumber––
station_or_report_idstring–Optional WeatherXM station UUID or custom site evaluation report ID (e.g. STUDY-...)
variablestring––

No output schema declared.

No examples provided.

get_fact_leaderboard ~496

Read the global weather forecast accuracy leaderboard (MAE, RMSE, circular angular error for wind_direction including >3 m/s active-wind curves, and categorical rain skill HSS, POD, FAR, CSI across lead days 0..7) or country-level published H3 cell-win summaries across all 45 forecast models and 8,927 stations. All 45 FACT models (2025 archive, 2025-02-13 to 2025-12-31, QoD >= 0.80 station-days): WeatherXM MOSAIC (MOSAIC), meteoblue (METEOBLUE), meteoblue station-mLM (commissioned) (mLM), ECMWF IFS (IFS025, IFSHRES), ECMWF AIFS AI (AIFS025), NOAA GFS 0.5° (GFS05), NOAA HRRR (HRRR), NOAA National Blend of Models (NBM), NOAA NAM (NAM3, NAM5, NAM12, NAMAK), DWD ICON (ICON, ICONEU, ICOND2), UK Met Office (UMGLOBAL10, UKMO2), ECCC GEM (GEM15, GEM2), Meteo-France ARPEGE/AROME (MFGLOBAL, MFEU, MFFR), COSMO (COSMOI2, COSMOM5), HARMONIE-AROME (HARMONIE), JMA MSM (MSM), WRF (WRFGR, WRFAMS), meteoblue NEMS/NMM (NEMSGLOBAL, NEMSGLOBAL_E, NEMS4, NEMS12, NEMS12_E, NEMSAF01, NEMSAS02, NEMSCAM, NEMSIN, NEMSNZ, NEMSSA, NMM4, NMM22), regional models (AF01, AS01, SA01). GFS025 is not archived; requests for it resolve to GFS05 with a resolution warning. Country counts describe published cell wins, not national matched-sample accuracy.

NameTypeReqDescription
countrystring––
exclude_commissionedboolean––
lead_daystring––
limitinteger–Maximum number of ranked models to return (1..45, default 45 for full model universe).
variablestring––

No output schema declared.

No examples provided.

get_model_head_to_head ~482

Compare up to 10 weather forecast models head-to-head across lead days 0 to 7 on global historical error curves (including circular angular error and >3 m/s active-wind curves for wind_direction), plus optional local H3 cell (lat/lon) matched-cohort or country cell-win comparisons, with explicit cohort and station-commissioned (mLM) caveats. All 45 FACT models (2025 archive, 2025-02-13 to 2025-12-31, QoD >= 0.80 station-days): WeatherXM MOSAIC (MOSAIC), meteoblue (METEOBLUE), meteoblue station-mLM (commissioned) (mLM), ECMWF IFS (IFS025, IFSHRES), ECMWF AIFS AI (AIFS025), NOAA GFS 0.5° (GFS05), NOAA HRRR (HRRR), NOAA National Blend of Models (NBM), NOAA NAM (NAM3, NAM5, NAM12, NAMAK), DWD ICON (ICON, ICONEU, ICOND2), UK Met Office (UMGLOBAL10, UKMO2), ECCC GEM (GEM15, GEM2), Meteo-France ARPEGE/AROME (MFGLOBAL, MFEU, MFFR), COSMO (COSMOI2, COSMOM5), HARMONIE-AROME (HARMONIE), JMA MSM (MSM), WRF (WRFGR, WRFAMS), meteoblue NEMS/NMM (NEMSGLOBAL, NEMSGLOBAL_E, NEMS4, NEMS12, NEMS12_E, NEMSAF01, NEMSAS02, NEMSCAM, NEMSIN, NEMSNZ, NEMSSA, NMM4, NMM22), regional models (AF01, AS01, SA01). GFS025 is not archived; requests for it resolve to GFS05 with a resolution warning.

NameTypeReqDescription
countrystring––
exclude_commissionedboolean––
latnumber––
lead_daystring––
lonnumber––
modelsarray––
variablestring––

No output schema declared.

No examples provided.

Install

How do I install the WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server?

WeatherXM FACT — Forecast Accuracy & Ground-Truth… is a hosted endpoint at https://fact.weatherxm.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.

remote · fact.weatherxm.com

# add to Claude Code
claude mcp add --transport http com-weatherxm-fact-mcp 'https://fact.weatherxm.com/mcp'
Common questions

What is the WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server?

WeatherXM FACT — Forecast Accuracy & Ground-Truth… is an MCP server listed in the public MCP registry as com.weatherxm.fact/mcp. Scores 45 NWP & AI weather models (ECMWF, GFS, ICON, meteoblue, MOSAIC) against 8,927 stations. This page covers its hosted endpoint (https://fact.weatherxm.com/mcp).

Is the WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server safe to use?

WeatherXM FACT — Forecast Accuracy & Ground-Truth… scores 70 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 WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server expose?

WeatherXM FACT — Forecast Accuracy & Ground-Truth… exposes 4 tools: get_best_forecast_model, check_ground_truth_coverage, get_fact_leaderboard, get_model_head_to_head. Their descriptions and schemas cost roughly 1,795 tokens of context every time the server is loaded.

Does the WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server require authentication?

No. We connected to WeatherXM FACT — Forecast Accuracy & Ground-Truth… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server still maintained?

WeatherXM FACT — Forecast Accuracy & Ground-Truth… 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 WeatherXM FACT — Forecast Accuracy & Ground-Truth… MCP server?

VerifyMCP ran 13 checks on WeatherXM FACT — Forecast Accuracy & Ground-Truth…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.