meteoblue Weather API vs Meteosource Weather MCP

meteoblue Weather API 75

Graded as a hosted service. Status page at status.meteoblue.com, a Pingdom public report with 15 monitors, one-minute checks and monthly history, served over http only, per the 8 October check, not re-read on 2 November 2026 because the host didn't resolve from our network (20). In the 90-day window from 4 August, the monitors read on 8 October show the History API down for 1 hour 26 minutes on 1 September, the Forecast API for 2 minutes on 15 September, and the Warnings, Dataset, Image and Location Search monitors for 1 to 17 minutes. Each touched one API, so each is partial. 9 October to 2 November is unread because the host didn't resolve, so "minor only" can't be confirmed for the whole window. The line holds at the 8 October award, as mailtrap's and merge-accounting's were held when their status hosts stopped answering, until the history can be read (15). 500 calls a minute and daily credit limits per account and key are documented (15). 429 is in every spec, and the availability page advises a 30-second timeout, a 30-second wait and at most 10 retries. No Retry-After header is documented. Every call is a GET (12 of 15). Custom SLAs are listed for enterprise plans with no published figure or credits. The availability page publishes yearly availability, 99.95 per cent for 2025, as a record and not a commitment (3 of 10). The Forecast API is generally available as version 2.0.0 (10). 20 + 15 + 15 + 12 + 3 + 10 = 75.

Meteosource Weather MCP 35

status.meteosource.com wasn't reachable (0). No history (5). Daily call quotas per plan, and the README's plans-and-limits section (15). Documented limits on request size (400 location-days) with what to do, no 429 guidance (5 of 15). No SLA found (0). Version 0.1.2, not labelled beta (10). 0 + 5 + 15 + 5 + 0 + 10 = 35.

meteoblue Weather API 37

The latest dated changelog entry is 22 August 2026 (ICON-CH1 and ICON-CH2 added), 72 days before this check (20 of 30). It is the only changelog entry in the 90-day window from 4 August, since the two 29 July entries have left it. The only official SDK has no release since 10 January 2025, no official MCP server is listed, and docs page stamps (overview 30 July, Model-Run Archive 2 October) aren't releases or changelog entries (0). A public changelog, a community forum and email support for self-serve users, none of which we tested (9 of 15). The only official SDK, meteoblue-dataset-sdk 1.3.5, was last released on 10 January 2025 and covers one API (4 of 15). Its repository has test and publish workflows and a last commit on 19 February 2025 (4 of 10). 20 + 0 + 9 + 4 + 4 = 37.

Meteosource Weather MCP 70

Repository commit and tag v0.1.2 on 26 October 2026 (30). Three tags in 90 days (20). Repository issues not read (0). Official registry entry com.meteosource/weather (15). Small repository with server.json; server source not public (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

meteoblue Weather API 62

Closed service under general terms last revised on 24 May 2018. They grant a non-commercial licence for open and registered access and leave commercial terms to a written agreement, while the Free Weather API table marks commercial use as allowed. The Python SDK is MIT (12 of 30). The privacy policy, last revised 15 May 2024, covers the API by name. It gives no retention period beyond as long as necessary, and no DPA was found (12 of 30). No deprecation policy was found. The terms let meteoblue change or revoke them at any time, and the changelog records removals after the fact, such as two COSMO models on 11 August 2025 (4 of 20). The policy names Google and Microsoft Clarity for the website and lists other contractors by category. The docs name Datatrans for payments, and the API answers through Cloudflare. No subprocessor list or stated data location for API logs was found (7 of 20).

Meteosource Weather MCP 32

The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25.

meteoblue Weather API 66

This is an API with no MCP server from the vendor. A caller sizes the response by choosing packages and a resolution and by setting forecastDays and historyDays. There is no field selection, and basic-1h returns 15 fields for each of 168 hours (16 of 25). The History API takes a time range, resolution and one of 14 aggregations, the Accounting API pages with page and per, and forecasts need no pagination (14 of 20). Errors are JSON with error and error_message under 400, 401, 403, 404 and 429, with no machine-readable code. (12 of 20). The 8 October call without a key went to a path my.meteoblue.com's robots.txt now closes, so that reading is struck. Every endpoint is a read-only GET, and retry guidance is published. Whether a failed call is charged credits is not stated (16 of 20). Only lat, lon and apikey are required, and elevation and time zone are detected. One official SDK, meteoblue-dataset-sdk for Python, covers the Dataset API only and dates from January 2025 (8 of 15).

Meteosource Weather MCP 75

Seven tools, about 20 KB (25). Date ranges and location limits on history (12 of 20). Documented error messages with fixes (15 of 20). No annotations on the tools (8 of 20, all reads). Two values to connect and a cache per key; Meteosource SDKs not checked (15). 25 + 12 + 15 + 8 + 15 = 75.

meteoblue Weather API 51

An account can hold several named keys, each deletable, each with a daily credit limit, an optional IP allow list, a referrer and origin allow list, and an optional shared secret that makes every URL carry an HMAC-SHA256 signature and an expiry. There are no scopes. The key is accepted only as the apikey query parameter (25 less 10, 15 of 30). All data is read-only, and package access follows the plan (16 of 20). Warning text is relayed from national authorities and place names from GeoNames. The rest is numeric (10 of 15). /account/usage returns request counts and credits per day and type, the key manager charts each key, and each response carries MB-Credits-Accounted. No per-call log was found (8 of 15). security.txt returns 404 on four hosts, and no disclosure policy, bounty, SOC 2 or ISO 27001 was found. The ISO 9001:2015 certificate covers quality management (2 of 20).

Meteosource Weather MCP 42

One API key per account in a header, never in the URL (20 of 30). All tools are reads (10 of 20). Weather data only, no third-party text (10). No audit log (0). No security programme found (2 of 20). Keys travel to the hosted server, which says it doesn't store them in full. 20 + 10 + 10 + 0 + 2 = 42.

meteoblue Weather API 77

OpenAPI 3.1 specs at openapi.json beside each ReDoc page, for the Forecast (54 paths), History, Accounting, Model-Run Archive, Dataset, Image, Warnings and Measurements APIs (25). business.meteoblue.com/llms.txt is a product index that links the docs. docs.meteoblue.com/llms.txt returns 404 and no Markdown docs were found (4 of 10). Package descriptions run long and say what each holds, which packages cannot be combined and when raw should not be set. They say less on choosing between similar packages (16 of 20). Coordinates carry minimum and maximum, units, formats, time formats and model domains are enums with defaults, and the History API marks five parameters required. The package path parameter is a comma-joined array (13 of 15). Samples in JavaScript, Python, shell and Java, and typed response fields with example values. Every error status shares one schema with a free-text error_message (10 of 15). Specs carry a version number, 2.0.0 for forecasts, with none in the path. The public changelog has 19 dated entries, mostly data additions (9 of 15).

Meteosource Weather MCP 72

Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72.