# Meteosource Weather MCP vs WeatherAPI.com (slim)

> WeatherAPI.com scores 64.6 (B) 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-weatherapi-com.md (~4,600 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.json · canonical https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com
- 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)

WeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security & auth and 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
- WeatherAPI.com: B 64.6, rank #460 of 1510 · https://www.anchorterminal.com/tools/weatherapi-com.min.md
- Meteosource Weather MCP, good for Agents that answer weather questions, plan around severe weather or estimate solar and wind output. Ahead on Security & auth, 42 against 37; Maintenance & community, 70 against 60.
- WeatherAPI.com, good for Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP. Ahead on Reliability, 80 against 35; Schema & documentation, 89 against 72; Agent ergonomics, 80 against 75; Transparency & trust, 65 against 32. Also Free to start without a card.

| Category | Meteosource Weather MCP | WeatherAPI.com |
| --- | --- | --- |
| Reliability (16%) | 35 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 89 |
| Agent ergonomics (13%) | 75 | 80 |
| Security & auth (14%) | 42 | 37 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 60 |
| Transparency & trust (7%) | 32 | 65 |

| Fact (where they differ) | Meteosource Weather MCP | WeatherAPI.com |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Meteosource | WeatherAPI.com (Zoomash Ltd) |
| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.weatherapi.com/v1` |
| Transports | Streamable HTTP | HTTP |
| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | none |
| Tools exposed | 7 | none |
| llms.txt | no | yes |
| MCP registry | `com.meteosource/weather` | not listed |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Reliability, WeatherAPI.com +45: 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.); WeatherAPI.com 80 (Status page at status.weatherapi.com on Better Stack, with api.weatherapi.com and the website as components (20). Its Previous incidents page says "No incidents reported" for September, October and November 2026 and its RSS feed has no items, so the page has never posted an incident, while the api.weatherapi.com monitor shows 99.839, 99.920 and 99.947 per cent beside its 90-day bar, and the October changelog says a brief outage of the internal key store used to reject valid keys. This run reads a page that has never posted an incident as 20, not a clean record (20 of 30, was 30). Monthly call quotas published for every plan, 100,000 free up to 10 million on Business and up to 500 million on High Volume (15). A spent quota returns 403 with error code 2007, distinct from auth errors, but there's no 429, Retry-After or backoff guidance (5 of 15). The terms promise 99.9 per cent to High Volume customers with service credits, and the plan table lists uptime per plan (10). Generally available (10). 20 + 20 + 15 + 5 + 10 + 10 = 80.)
- Transparency & trust, WeatherAPI.com +33: 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.); WeatherAPI.com 65 (Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20).)
- Schema & documentation, WeatherAPI.com +17: 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.); WeatherAPI.com 89 (OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though `q` is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15).)
- Maintenance & community, Meteosource Weather MCP +10: 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.); WeatherAPI.com 60 (The changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60.)
- Agent ergonomics, WeatherAPI.com +5: 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.); WeatherAPI.com 80 (`current_fields`, `day_fields` and `hour_fields` trim responses, and `aqi`, `alerts` and `days` keep them small. The official MCP server has 11 tools (22 of 25). `days`, `hour`, field filters and bulk requests on Pro+ (17 of 20). Numeric error codes such as 1006 (no location found) and 2007 (quota exceeded) let an agent tell the cases apart (18 of 20). Read-only GETs, and the bulk POST only reads. The MCP tools carry no readOnlyHint annotations (13 of 20). Only `key` and `q` are required, and SDKs exist for Node.js, Java, PHP and Go, but none has a commit since 2021 (10 of 15).)
- Security & auth, Meteosource Weather MCP +5: 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.); WeatherAPI.com 37 (The key goes only in the `key` query parameter, so it lands in URLs and logs (20 less 10). Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, but none can be scoped, and Business adds IP blocking (12 of 30). Read-only data (15 of 20). Alerts come from government agencies (10 of 15). Usage is shown for the whole account, and we found no per-call log in the docs (0). No security.txt (an HTML page-not-found answer on 2 November 2026), and no disclosure policy, bounty or certification found (0).)