# AccuWeather Core Weather API + MCP vs Meteosource Weather MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.md (~4,650 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.json · canonical https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp
- 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)

Meteosource Weather MCP scores 50.9 (D) on agent readiness against AccuWeather Core Weather API + MCP's 49.2 (D), and leads in 5 of 7 scored categories. AccuWeather Core Weather API + MCP leads on reliability and transparency & trust. Both do weather forecasts.

- AccuWeather Core Weather API + MCP: D 49.2, rank #1102 of 1510 · https://www.anchorterminal.com/tools/accuweather-api.min.md
- Meteosource Weather MCP: D 50.9, rank #1048 of 1510 · https://www.anchorterminal.com/tools/meteosource-mcp.min.md
- AccuWeather Core Weather API + MCP, good for Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user. Ahead on Reliability, 75 against 35; Transparency & trust, 51 against 32.
- Meteosource Weather MCP, good for Agents that answer weather questions, plan around severe weather or estimate solar and wind output. Ahead on Schema & documentation, 72 against 60; Agent ergonomics, 75 against 60; Payments & pricing, 30 against 25; Maintenance & community, 70 against 3.

| Category | AccuWeather Core Weather API + MCP | Meteosource Weather MCP |
| --- | --- | --- |
| Reliability (16%) | 75 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 60 | 72 |
| Agent ergonomics (13%) | 60 | 75 |
| Security & auth (14%) | 39 | 42 |
| Payments & pricing (10%) | 25 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 3 | 70 |
| Transparency & trust (7%) | 51 | 32 |

| Fact (where they differ) | AccuWeather Core Weather API + MCP | Meteosource Weather MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | AccuWeather | Meteosource |
| Hosted endpoint | `https://dataservice.accuweather.com` | `https://mcp.meteosource.com/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Licence | none | Proprietary service. The repository's MIT licence covers its docs and manifest |
| Tools exposed | 27 | 7 |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | not listed | `com.meteosource/weather` |
| Terms last updated | 2026-04-28 | no document linked |
| Privacy policy last updated | couldn't be read | 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 | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Maintenance & community, Meteosource Weather MCP +67: AccuWeather Core Weather API + MCP 3 (No release notes or changelog on the portal, re-read on 4 November. The API terms update of 28 April 2026 was the only dated change on 1 October, and a terms date isn't an API change in this run's reading; it is also now 190 days old (0). The MCP server grew from 26 to 27 tools with no dated entry (0). No dated changes in the last 90 days (0). Support through a contact form, with no public changelog or community channel (3 of 15). The official MCP server isn't in the registry, per the 1 October check, and there's no official SDK (0). No package to judge (0). 0 + 0 + 3 + 0 + 0 = 3.); 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.)
- Reliability, AccuWeather Core Weather API + MCP +40: AccuWeather Core Weather API + MCP 75 (Status page at status.accuweather.com with Enterprise API and Developer Portal API components (20). Its history feed, read in full on 4 November, lists in the 90 days from 6 August intermittent degraded performance with 'our APIs' on 20 August (1 hour 22 minutes) and from 21 to 23 August, the Historical and Lightning APIs on 19 October and MinuteCast on 2 November. All four are degraded performance, three name one or two products, and none reports the API down, so they read as partial and the record is minor incidents only. The 26 August and 23 September entries were announced maintenance with windows (20 of 30). Call quotas published per package, 500 a day on the trial up to 2.4 million a month on Elite, but no per-second limit (15). 429 and 503 are defined in the status code table, and the MCP troubleshooting table says to 'Wait and retry' on 429, with no Retry-After header documented. Every call is a read. Backoff guidance alone (10). No SLA, and the terms cap liability at $100 (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 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.)
- Transparency & trust, AccuWeather Core Weather API + MCP +19: AccuWeather Core Weather API + MCP 51 (Closed service with API terms last updated 28 April 2026, re-read on 4 November (15). The API terms let AccuWeather collect, store and use request data such as locations and IP addresses and point to the privacy policy on www.accuweather.com. That host's robots.txt answered Access Denied on 4 November, so the 1 October reading of the privacy policy (retention tied to the account) is struck. No DPA found. The terms clause partly meets the line, so the earlier partial is kept (12 of 30). The terms say AccuWeather 'may change the APIs at any time without notice' (0). The provider list and the United States processing statement came from the privacy policy and are struck (0 of 20). 15 + 12 + 0 + 0 = 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.)
- Agent ergonomics, Meteosource Weather MCP +15: AccuWeather Core Weather API + MCP 60 (27 MCP tools covering all 106 Core Weather GET endpoints, with no toolsets or subset option found. REST responses shrink a little with `details=false` and by choosing the 1, 5, 10 or 15-day endpoint (15 of 25). No field selection or paging (10 of 20). RFC 7807 errors with a trace id and a documented status table (16 of 20). Read-only GETs, and the docs describe the MCP server as read-only (15 of 20). Every weather call needs a location key from a separate search call first, and there's no official SDK (4 of 15). 15 + 10 + 16 + 15 + 4 = 60.); 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.)
- Schema & documentation, Meteosource Weather MCP +12: AccuWeather Core Weather API + MCP 60 (No OpenAPI or other machine-readable contract found. The Core Weather, MinuteCast and Lightning references are drawn from OpenAPI documents, but no page we read links a spec as a download. The MCP tools page lists each tool's arguments, which we couldn't check as JSON Schema without a key. The earlier partial is kept (8 of 25). llms.txt, llms-full.txt and a .md twin for every docs page (10). The MCP tools page says what each tool returns and where coverage stops, such as MinuteCast and Lightning staying on REST (14 of 20). Parameters are documented, mostly location keys, language codes and booleans (10 of 15). Quick-start examples and an 11-row status code table, with RFC 7807 problem bodies carrying type, title, status and trace (13 of 15). Versioned /v1 paths, but no changelog or release notes anywhere on the portal, re-read on 4 November (5 of 15). 8 + 10 + 14 + 10 + 13 + 5 = 60.); 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.)
- Payments & pricing, Meteosource Weather MCP +5: AccuWeather Core Weather API + MCP 25 (No x402, MPP or L402 (0). Package prices and per-1,000 overage rates are public, from $2 a month for 15,000 calls with $0.25 per 1,000 over (15 of 20). A 14-day trial at 500 Core Weather calls a day. Neither the FAQ nor llms-full.txt says whether it needs a card, so we gave half (10 of 20, the earlier partial kept). A person signs up in a browser (0). 0 + 15 + 10 + 0 = 25.); 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.)