# meteoblue Weather API vs Meteosource Weather MCP

> meteoblue Weather scores 60.1 (C) to Meteosource Weather MCP's 50.9 (D) for weather forecasts. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp
- Markdown: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.md (~5,150 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance & community. Both do weather forecasts.

- meteoblue Weather API: grade C, 60.1/100, rank #667 of 1510. Markdown https://www.anchorterminal.com/tools/meteoblue.md · JSON https://www.anchorterminal.com/api/v1/tools/meteoblue.json
- Meteosource Weather MCP: grade D, 50.9/100, rank #1048 of 1510. Markdown https://www.anchorterminal.com/tools/meteosource-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json
- Best weather and climate data APIs for AI agents: https://www.anchorterminal.com/best/weather/index.md
- All 136 weather comparisons: https://www.anchorterminal.com/compare/weather/index.md

## Which one, for what

### meteoblue Weather API (C)

Good for: Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.

Ahead on:
- Reliability, 75 against 35
- Schema & documentation, 77 against 72
- Security & auth, 51 against 42
- Transparency & trust, 62 against 32

Watch for: The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on

### Meteosource Weather MCP (D)

Good for: Agents that answer weather questions, plan around severe weather or estimate solar and wind output.

Ahead on:
- Agent ergonomics, 75 against 66
- Maintenance & community, 70 against 37

Watch for: Plain API key, no OAuth


## Why the edge

### Reliability: meteoblue Weather API +40

- 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.

### Maintenance & community: Meteosource Weather MCP +33

- 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.

### Transparency & trust: meteoblue Weather API +30

- 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.

### Agent ergonomics: Meteosource Weather MCP +9

- 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.

### Security & auth: meteoblue Weather API +9

- 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.

### Schema & documentation: meteoblue Weather API +5

- 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.

## Score by category

| Category | Weight | meteoblue Weather API | Meteosource Weather MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 35 | meteoblue Weather API +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 77 | 72 | meteoblue Weather API +5 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 75 | Meteosource Weather MCP +9 |
| Security & auth | 14% (17.5 this run) | 51 | 42 | meteoblue Weather API +9 |
| Payments & pricing | 10% (12.5 this run) | 34 | 30 | meteoblue Weather API +4 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 37 | 70 | Meteosource Weather MCP +33 |
| Transparency & trust | 7% (8.8 this run) | 62 | 32 | meteoblue Weather API +30 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **60.1 · C** | **50.9 · D** | |

## Facts side by side

| Fact | meteoblue Weather API | Meteosource Weather MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | meteoblue AG | Meteosource |
| Hosted endpoint | `https://my.meteoblue.com` | `https://mcp.meteosource.com/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT | Proprietary service. The repository's MIT licence covers its docs and manifest |
| Tools exposed | none | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | `com.meteosource/weather` |
| Last release | 2026-08-22 | none |
| Terms last updated | 2018-05-24 | no document linked |
| Privacy policy last updated | 2024-05-15 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 8 stars, 512 PyPI/wk | none |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### meteoblue Weather API

- -1.7 on 2 November 2026: time
- +0.1 on 27 October 2026: checklist

### Meteosource Weather MCP

No score change since it was listed.

## Verdicts

**meteoblue Weather API.** Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.

**Meteosource Weather MCP.** Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.

## Before you call either

### meteoblue Weather API

1. Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/<package>`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call
2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read `MB-Credits-Accounted` on each response
3. Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has
4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute
5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send `expire` and `sig` if URLs may be seen by others

### Meteosource Weather MCP

1. Call search_places first to resolve a location
2. Split history requests over 400 location-days into shorter ranges
3. Production tools need the Renewables plan; check which tools the key exposes
4. Send the key in a header, never in a URL

## Questions

### Which is better for AI agents, meteoblue Weather API or Meteosource Weather MCP?

meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance & community.

### Do meteoblue Weather API and Meteosource Weather MCP need an API key?

Both need an API key.

### Can an agent call meteoblue Weather API and Meteosource Weather MCP without installing anything?

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "meteoblue", "b": "meteosource-mcp"}`. From a terminal: `anchor compare meteoblue meteosource-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteoblue.json and https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json

## Other comparisons with meteoblue Weather API or Meteosource Weather MCP

- [AccuWeather Core Weather API + MCP vs meteoblue Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.md)
- [Google Weather API (Maps Platform) vs meteoblue Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.md)
- [Met Office Weather DataHub (Site Specific) vs meteoblue Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.md)
- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)
- [meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.md)
- [meteoblue Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.md)
- [meteoblue Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.md)
- [meteoblue Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md)
- [meteoblue Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.md)
- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)
- [meteoblue Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.md)
- [meteoblue Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.md)
- [meteoblue Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-xweather.md)
- [AccuWeather Core Weather API + MCP vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.md)
- [Google Weather API (Maps Platform) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp.md)
- [Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp.md)
- [meteoblue Weather API vs Stormglass API](https://www.anchorterminal.com/compare/meteoblue-vs-stormglass.md)
- [Meteomatics Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.md)
- [Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.md)
- [Meteosource Weather MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.md)
- [Meteosource Weather MCP vs Pirate Weather](https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.md)
- [Meteosource Weather MCP vs Stormglass API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.md)
- [Meteosource Weather MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.md)
- [Meteosource Weather MCP vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.md)
- [Meteosource Weather MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.md)
- [Meteosource Weather MCP vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.md)
- [Meteosource Weather MCP vs Weatherbit API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit.md)
- [Meteosource Weather MCP vs Xweather Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather.md)
- [meteoblue Weather API vs Open-Meteo](https://www.anchorterminal.com/compare/meteoblue-vs-open-meteo.md)
- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp