Meteomatics
https://mcp.meteomatics.com/mcp ↗
Description
The Meteomatics MCP (Model Context Protocol) server allows AI agents to securely access Meteomatics weather data tools. MCP is an open standard that lets AI applications connect to external tools and data sources. With the Meteomatics MCP, agents can request weather data directly from the Meteomatics API through a secure /mcp endpoint. The MCP server manages authentication using OAuth (client registration, authorization code + PKCE, and refresh tokens). Once connected, the AI agent can access data, models, parameters, time ranges that are available to your Meteomatics API account.
What our measurements say
Meteomatics is a remote MCP server published at mcp.meteomatics.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 348 ms, placing it among the faster endpoints. It offers a narrow, focused set of 9 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Some tool names (e.g., get_weather_for_polygon) clearly indicate spatial scope
- Descriptions include specific use cases for multi-location queries
Weaknesses
- Ambiguous tool names like 'get_opmet' require domain knowledge to understand
- Parameter requirements are inconsistently documented (e.g., station_id vs lat/lon)
- Tool overlap between single/multi-location weather functions creates ambiguity
- No explicit error handling or constraint documentation in any tool descriptions
get_opmet— Non-descriptive name requiring prior knowledge of aviation weather codesget_weather_for_location— Parameter requirements (lat/lon vs station_id) not clearly marked as mutually exclusiveget_weather_for_locations— Similar functionality to get_weather_for_location creates potential duplicationfind_station— No mention of filtering constraints or maximum results limit
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'unknown' to 'legacy' · indicates system recognition of legacy configuration
- 2026-09-11T05:44:28.819Z — complianceScore increased from null to 100 · confirms full regulatory compliance in legacy mode
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 119ms → warm 105ms (penalty 14ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-11-25
- Era changed: Unknown → Legacy
- Added to watch — era: Unknown
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/meteomatics-meteomatics)<a href="https://mcpmetrics.io/servers/meteomatics-meteomatics"><img src="https://mcpmetrics.io/badge/meteomatics/meteomatics/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see