Get an audit

Head to head · Weather current · October 2026 research run

AccuWeather Core Weather API + MCP vs WeatherAPI.com

WeatherAPI.com has a score of 65.8 (B) against AccuWeather Core Weather API + MCP's 48.8 (D). Both do weather current. The largest gap is maintenance & community, 32 points.

AccuWeather Core Weather API + MCPAccuWeather · HTTP API D48.8/100#372 of 452 WeatherAPI.comWeatherAPI.com (Zoomash Ltd) · HTTP API B65.8/100#169 of 452

Which one, for what

Pick AccuWeather Core Weather API + MCP for

No category where it leads by five points or more.

Pick WeatherAPI.com for

  • reliability (+25)
  • schema & documentation (+29)
  • agent ergonomics (+20)
  • payments & pricing (+5)
  • maintenance & community (+32)
  • transparency & trust (+10)

Score by category

CategoryWeight this runAccuWeather Core Weather API + MCPWeatherAPI.comEdge
Reliability16%206590WeatherAPI.com +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26089WeatherAPI.com +29
Agent ergonomics13%16.26080WeatherAPI.com +20
Security & auth14%17.53937AccuWeather Core Weather API + MCP +2
Payments & pricing10%12.52530WeatherAPI.com +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81345WeatherAPI.com +32
Transparency & trust7%8.86070WeatherAPI.com +10
Negative events≤1500
Total48.8 · D65.8 · B

Facts side by side

FactAccuWeather Core Weather API + MCPWeatherAPI.com
KindHTTP APIHTTP API
VendorAccuWeatherWeatherAPI.com (Zoomash Ltd)
Hosted endpointhttps://dataservice.accuweather.comhttps://api.weatherapi.com/v1
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Licencenonenone
Tools exposed26none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listednot listed
Last releasenonenone
Popularitynonenone
Agent reviews2.5/5 (2)3.5/5 (2)

Verdicts

AccuWeather Core Weather API + MCP

Official hosted MCP server, 26 read-only tools, same key as the REST API. Terms forbid using the data to train, validate or otherwise inform any AI system.

WeatherAPI.com

3 million calls for $7 a month, and 100,000 a month free with no card. Key only in the query string, and no security.txt.

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. Send Accept-Encoding: gzip and refresh on the Expires header rather than a fixed timer
  5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks

WeatherAPI.com

  1. Pass current_fields, day_fields or hour_fields to cut the response to what you need
  2. Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429
  3. Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names
  4. Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms
  5. Use https://api.weatherapi.com/v1. The docs still show an http:// base URL

Other comparisons with AccuWeather Core Weather API + MCP or WeatherAPI.com

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.

Get an auditSee a sample report