# Meteosource Weather MCP vs The Weather Company Data APIs (slim)

> The Weather Company Data scores 54.5 (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-weather-company.md (~4,650 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.json · canonical https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company
- 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)

The Weather Company Data APIs scores 54.5 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics, payments & pricing 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
- The Weather Company Data APIs: C 54.5, rank #911 of 1510 · https://www.anchorterminal.com/tools/weather-company.min.md
- Meteosource Weather MCP, good for Agents that answer weather questions, plan around severe weather or estimate solar and wind output. Ahead on Agent ergonomics, 75 against 54; Payments & pricing, 30 against 20; Maintenance & community, 70 against 36.
- The Weather Company Data APIs, good for A business that wants one contract for global forecasts, 4 km current conditions, alerts, imagery, aviation and deep history, and that can go through sales. Ahead on Reliability, 75 against 35; Schema & documentation, 77 against 72; Security & auth, 47 against 42; Transparency & trust, 50 against 32.

| Category | Meteosource Weather MCP | The Weather Company Data APIs |
| --- | --- | --- |
| Reliability (16%) | 35 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 77 |
| Agent ergonomics (13%) | 75 | 54 |
| Security & auth (14%) | 42 | 47 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 36 |
| Transparency & trust (7%) | 32 | 50 |

| Fact (where they differ) | Meteosource Weather MCP | The Weather Company Data APIs |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Meteosource | The Weather Company, LLC |
| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.weather.com` |
| Transports | Streamable HTTP | HTTP |
| Pricing | Freemium | Paid |
| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published |
| Tools exposed | 7 | none |
| llms.txt | no | yes |
| MCP registry | `com.meteosource/weather` | not listed |
| Last release | none | 2026-10-15 |
| Privacy policy last updated | no document linked | couldn't be read |

Why the edge:
- Reliability, The Weather Company Data APIs +40: 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.); The Weather Company Data APIs 75 (Status page at theweathercompanyapis.statuspage.io with 16 components, read from the page itself on 4 November 2026 (20). Its history feed shows 14 incidents from 6 August to 28 October 2026, each a degraded API, region or upstream source, such as EU-West latency on 26 October and the 5 September NOAA and NWS upstream outage of alerts, observations and radar, so all partial (20 of 30). Trial limits are published at 100 requests a minute and 50,000 a day, and paid limits are a monthly cap set by contract (15). No 429 is documented and an exceeded limit returns 401, but the error tables of three references, Daily Forecast among them, tell clients to retry 502, 503 and 504 with exponential backoff (10). The product page states a 99.95 per cent uptime SLA with no SLA document published (0). The v1, v2 and v3 APIs are in production, although the documentation site is labelled beta (10).)
- Maintenance & community, Meteosource Weather MCP +34: 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.); The Weather Company Data APIs 36 (The Hourly Forecast Enterprise reference records a specification change on 15 October 2026 (a new windSpeedKnots field released on 22 October), 20 days before the check (30). Two dated changelog entries in the 90 days from 6 August (14 September and 15 October) in the 18 references we read, short of three (0). Support is by email and a ServiceNow customer portal, and the status page is updated during incidents. No public community channel was found (6 of 15). No official SDK was found (0). No package to assess (0).)
- Agent ergonomics, Meteosource Weather MCP +21: 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.); The Weather Company Data APIs 54 (Response size is controlled by choosing a duration endpoint, by the `products` field selection and compact mode on History on Demand, and by aggregation, which is capped at 10 products and 1 MB. There is no general field selection (14 of 25). Only two APIs paginate, Alert Headlines and History on Demand (10 of 20). Errors are JSON with a code and message, such as `CDN-0004` for a missing key and `CDN-0001` for an invalid one, as the reference pages document. Authorisation failures and exceeded limits share 401 (11 of 20). All documented operations are GET requests, so retries are safe (15 of 20). Every v3 call needs a location plus `units`, `language` and `format`, gzip is required, and no official SDK was found (4 of 15).)
- Transparency & trust, The Weather Company Data APIs +18: 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.); The Weather Company Data APIs 50 (A closed service. Per the 8 October check, not re-read on 4 November, the website terms of use, updated 16 April 2026, say they do not apply to the business data APIs and refer to separate terms that we did not find published (5 of 30). Per the same check, the privacy policy, effective 30 April 2026, covers business contact data collected through developer.weather.com and says customer-managed personal data is used as business agreements specify. Retention is stated as as long as necessary, and no data processing agreement was found (10 of 30). No deprecation policy or dated deprecation notice was found (0). The policy says data is processed in the United States and other jurisdictions. No sub-processor list was read, since the trust centre is drawn by script (5 of 20).)
- Payments & pricing, Meteosource Weather MCP +10: 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.); The Weather Company Data APIs 20 (No x402, MPP or L402 (0). The Standard package price is public at $500 a month for 1 million calls on an annual plan. Enterprise plans, add-on packages and overage rates are by contract (10 of 20). A 30-day trial at 50,000 calls a day is free, but it is requested by form and limited to enterprise customers. The form did not load for us, so whether it asks for a card is unchecked, and we gave half (10 of 20). A person requests the trial and sales provisions the key (0).)
- Schema & documentation, The Weather Company Data APIs +5: 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.); The Weather Company Data APIs 77 (168 API reference sections are generated from OpenAPI documents (in the page data), and 11 Postman collections can be downloaded, but no standalone OpenAPI file was found (18 of 25, partial kept). developer.weather.com serves the whole documentation as Markdown at /llms-full.txt (2.6 MB); /llms.txt answers 404 (10). Overviews state sources, coverage, attribution and behaviour such as the 3 pm daypart change (16 of 20). Parameters carry enums, patterns and required flags (13 of 15). Each operation has an example response, documented status codes and code samples in seven languages, though the error guide says messages may vary by system (12 of 15). Paths are versioned and each API reference has a changelog section. Two dated entries, 14 September and 15 October 2026, appeared in the 18 references we read, and there is no central changelog (8 of 15, partial kept).)