# Meteosource Weather MCP vs OpenWeather One Call API (slim)

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

- Full: https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.md (~3,850 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.json · canonical https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

OpenWeather One Call API scores 55.4 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 3 of 7 scored categories. Meteosource Weather MCP leads on maintenance & community. Both do weather forecasts.

- Meteosource Weather MCP: D 50.9, rank #1048 of 1510 · https://www.anchorterminal.com/tools/meteosource-mcp.min.md
- OpenWeather One Call API: C 55.4, rank #871 of 1510 · https://www.anchorterminal.com/tools/openweather-one-call.min.md
- Meteosource Weather MCP, good for Agents that answer weather questions, plan around severe weather or estimate solar and wind output. Ahead on Maintenance & community, 70 against 40.
- OpenWeather One Call API, good for Agents that need a global forecast plus deep history from one vendor at low cost, and for any agent that has to provision its own key. Ahead on Reliability, 45 against 35; Payments & pricing, 60 against 30; Transparency & trust, 59 against 32. Also Free to start without a card.

| Category | Meteosource Weather MCP | OpenWeather One Call API |
| --- | --- | --- |
| Reliability (16%) | 35 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 68 |
| Agent ergonomics (13%) | 75 | 73 |
| Security & auth (14%) | 42 | 42 |
| Payments & pricing (10%) | 30 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 40 |
| Transparency & trust (7%) | 32 | 59 |

| Fact (where they differ) | Meteosource Weather MCP | OpenWeather One Call API |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Meteosource | OpenWeather |
| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.openweathermap.org/data/3.0/onecall` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | none |
| Tools exposed | 7 | 6 |
| llms.txt | no | yes |
| MCP registry | `com.meteosource/weather` | `org.openweathermap/agents` |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | 2022-07-18 |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Payments & pricing, OpenWeather One Call API +30: Meteosource Weather MCP 30 (No machine payment protocol (0). Plan prices with daily call quotas, public (10). Free plan with 400 calls a day, no card (20). A person signs up in a browser for the key (0). 0 + 10 + 20 + 0 = 30.); OpenWeather One Call API 60 (No x402, MPP or L402. The agent lane's top-ups are card only and need a person (0). Per-call prices published without login, $0.0015 a call on One Call by Call and $0.001 a call on the agent lane (20). The agent lane gives every account 1,000 One Call credits a day with only an email (20). POST an email to agents.openweathermap.org/v1/accounts and the data key comes back in the response (20). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).)
- Maintenance & community, Meteosource Weather MCP +30: 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.); OpenWeather One Call API 40 (The newest dated release is the MCP server's version 0.3.0, published to the official registry on 4 September 2026, 61 days before this check (20). In the 90 days from 6 August, MCP 0.2.0 and 0.3.0 on 4 September and the agent terms revision of 23 September, which isn't a release. Two releases, short of the three the line needs, and no dated API changelog (0). No public changelog for One Call. Support is through the help desk, which we didn't test (5 of 15). The MCP server is in the official registry as org.openweathermap/agents, a domain-verified namespace (15). No package to judge (0). 20 + 0 + 5 + 15 + 0 = 40.)
- Transparency & trust, OpenWeather One Call API +27: 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.); OpenWeather One Call API 59 (Closed service. The terms of sale, re-read on 4 November 2026 at their new address, still put products and services under CC BY-SA 4.0 and the data under ODbL (18 of 30). The privacy policy, last updated 18 July 2022, says API request parameters, IPs and user agents aren't collected or stored and keeps customer records six years. The agent lane runs under a second company, Extreme Electronics Ltd, with its own terms, and we found no DPA (18 of 30). 3.0 is marked deprecated with no date (5 of 20). Google Analytics and group companies in Latvia and the USA are named for transfers (12 of 20). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).)
- Reliability, OpenWeather One Call API +10: 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.); OpenWeather One Call API 45 (No public status page found, and status.openweathermap.org doesn't resolve (0). No incident history to read (5). Limits published with numbers, 1,000 One Call calls a day free, a default cap of 2,000 a day you can change, and 60 a minute on the Free plan (15). 429 is documented as quota exceeded, and the agent lane says its 429 names the interval to wait. All calls are GETs (10 of 15). The subscription table publishes uptime of 95 to 99.9 per cent for the Startup to Expert plans, but nothing for One Call by Call (5 of 10). One Call 4.0 is the current version (10). Readings per the 1 October check, not re-read on 4 November 2026 (the website terms bar robots and automatic devices on openweathermap.org, its subdomains and openweather.co.uk).)