Google Weather API (Maps Platform) vs Meteosource Weather MCP

Google Weather API (Maps Platform) 85

The Google Maps Platform status dashboard lists Weather API as its own product, one of 37 (20). Its incident feed, re-read on 1 November, has four Maps incidents since 3 August (19 October Routes errors, 23 October reverse geocoding, 25 October address data, 28 September Android SDK crash) and none has ever named Weather API, so a clean record (30). Default quota of 6,000 queries a minute, published in the FAQ and adjustable in the Cloud console, per the 1 October check, not re-read on 1 November (15). No 429, Retry-After or backoff guidance found in the Weather docs (0). Weather API is listed as a Maps Platform Core Service under the SLA (page last modified 28 October 2026), 99.9 per cent monthly uptime with credits of 10 to 50 per cent (10). Current conditions, forecasts, history and alerts are GA, and the minute forecast is Experimental (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.

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.

Google Weather API (Maps Platform) 20

The last Weather API release note is still the alerts endpoint going GA on 18 November 2025 (page last updated 30 October 2026), 348 days before 1 November. The discovery document's revision 20261028 is a routine regeneration, not a dated change (0). No dated releases in the last 90 days (0). Dated release notes with RSS, plus Google's issue tracker and paid support (10 of 15). Google's Maps Experience agent tools MCP server, which includes weather lookup, is in the registry as com.googleapis.mapstools/mcp, version 1.0.0 of 19 April 2026, unchanged on 1 November. It's a separate product, so partial credit (10 of 15). No package to judge (0). 0 + 0 + 10 + 10 + 0 = 20.

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.

Google Weather API (Maps Platform) 72

Closed service with Maps Platform terms last modified 26 August 2026, re-read on 1 November (15). Google's privacy policy, the Controller-Controller Data Protection Terms and GDPR, LGPD and Standard Contractual Clauses commitments on the trust centre agree with each other (22 of 30). The terms promise 12 months' notice before discontinuing a service or making a backwards-incompatible API change (20). The trust centre covers compliance frameworks, but we didn't find a Weather or Maps subprocessor list or data locations (8 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.

Google Weather API (Maps Platform) 73

Google Cloud API keys can be restricted to the Weather API and to IPs or apps, and rotated. OAuth 2.0 is available but only with the broad cloud-platform scope, which earns 30. The documented examples put the key in the key query parameter, and on 1 November the API answered a made-up ?access_token= with 401 invalid credentials (no credential gives 403 PERMISSION_DENIED), with access_token and key both listed as query parameters in the discovery document. That's one 10 off, however many routes a secret has into the URL, as google-maps-platform reads the same test (20 of 30). Read-only data (15 of 20). Alerts text comes from national agencies (10 of 15). Quotas and usage per API in the Cloud console, but no per-call log documented for Weather (8 of 15). google.com's security.txt is valid to 1 April 2030 and names the vulnerability reward programme, and the Maps Platform trust centre lists ISO/IEC 27001:2022 and 27017, SOC 2 and SOC 3, both read on 1 November. Read as google-maps-platform reads the same trust centre (20). 20 + 15 + 10 + 8 + 20 = 73.

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.

Google Weather API (Maps Platform) 82

A Google discovery document at weather.googleapis.com (revision 20261028 on 1 November) defines seven methods, enums and a description on every parameter (25). No llms.txt or Markdown twin found (0). Method docs state what each returns, and the coverage page says where alerts apply (16 of 20). Typed parameters with enums for units, conditions and event types, days and hours bounds and a required location (14 of 15). Request and response examples, and the FAQ documents the 404 for unsupported locations. Errors otherwise follow Google's generic error model (12 of 15). Versioned v1 path, dated release notes with launch stages and an RSS feed (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.

Google Weather API (Maps Platform) 40

No x402, MPP or L402 (0). Tiered per-1,000 prices published without login, $0.15 per 1,000 to 100,000 down to $0.038 above 5 million, re-read on 1 November (20). 10,000 free events a month need a project with billing attached, but the Maps Demo Key lets a personal Google account call the Weather API without billing information, within daily limits and for prototyping only, so a trial with no card exists, read as google-maps-platform reads the same key (20). A person signs in to a Google account and accepts terms in a browser before a key exists (0). 0 + 20 + 20 + 0 = 40.

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.