Head to head · Weather forecasts · October 2026 research run

AccuWeather Core Weather API + MCP vs Meteosource Weather MCP

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.

Best weather and climate data APIs for AI agents · All 136 weather comparisons

Which one, for what

AccuWeather Core Weather API + MCP D

Best 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

Watch for

Terms forbid using the data to train, validate or otherwise inform any AI system

Meteosource Weather MCP D

Best 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

Watch for

Plain API key, no OAuth

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

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.

Score by category

CategoryWeight this runAccuWeather Core Weather API + MCPMeteosource Weather MCPEdge
Reliability16%207535AccuWeather Core Weather API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26072Meteosource Weather MCP +12
Agent ergonomics13%16.26075Meteosource Weather MCP +15
Security & auth14%17.53942Meteosource Weather MCP +3
Payments & pricing10%12.52530Meteosource Weather MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8370Meteosource Weather MCP +67
Transparency & trust7%8.85132AccuWeather Core Weather API + MCP +19
Negative events≤1500
TotalD 49.2/100D 50.9/100

Facts side by side

FactAccuWeather Core Weather API + MCPMeteosource Weather MCP
KindHTTP APIMCP server
VendorAccuWeatherMeteosource
Hosted endpointhttps://dataservice.accuweather.comhttps://mcp.meteosource.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service. The repository's MIT licence covers its docs and manifest
Tools exposed277
Read-only variant documentedyesno
llms.txtyesno
MCP registrynot listedcom.meteosource/weather
Terms last updated2026-04-28no document linked
Privacy policy last updatedcouldn't be readno document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

AccuWeather Core Weather API + MCP

An official hosted MCP server exposes all 106 Core Weather GET endpoints as 27 read-only tools on the same key as the REST API, and the status page shows only partial incidents since August. There is no changelog, the terms allow API changes without notice, and they forbid using the data to train or inform any AI system.

Meteosource Weather MCP

Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.

Before you call either

AccuWeather Core Weather API + MCP

  1. Cache location keys. They don't change, and the lookup is the call worth saving
  2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns
  3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs
  4. On 429 wait and retry. On the trial it usually means the 500-call daily allowance is spent until it resets
  5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

Meteosource Weather MCP

  1. Call search_places first to resolve a location
  2. Split history requests over 400 location-days into shorter ranges
  3. Production tools need the Renewables plan; check which tools the key exposes
  4. Send the key in a header, never in a URL

Questions

Which is better for AI agents, AccuWeather Core Weather API + MCP or Meteosource Weather MCP?

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.

Do AccuWeather Core Weather API + MCP and Meteosource Weather MCP need an API key?

Both need an API key.

Can an agent call AccuWeather Core Weather API + MCP and Meteosource Weather MCP without installing anything?

Yes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.

Other comparisons with AccuWeather Core Weather API + MCP or Meteosource Weather MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.