{ "data": { "a": { "slug": "accuweather-api", "name": "AccuWeather Core Weather API + MCP", "vendor": "AccuWeather", "vendorUrl": "https://developer.accuweather.com", "kind": "http-api", "category": "weather", "summary": "Weather API for current conditions, forecasts, alerts and radar imagery, with an official read-only MCP server.", "url": "https://www.anchorterminal.com/tools/accuweather-api", "markdownUrl": "https://www.anchorterminal.com/tools/accuweather-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/accuweather-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/accuweather-api.json", "dns": "accuweather-api.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://dataservice.accuweather.com", "packages": [], "auth": "api-key", "authNotes": "Authorization: Bearer with the Core Weather key on REST, the only method the authentication page documents. The MCP server also takes the key as an apikey parameter on its URL, which the connection guide uses for clients without header support. Keys are rotated on the subscriptions page. Every weather call needs a location key first, from the locations search or geoposition endpoints.", "pricing": "freemium", "pricingNotes": "Free 14-day trial at 500 Core Weather calls a day, MCP included. Starter $2 a month for 15,000 calls ($0.25 per 1,000 over), Standard $25 for 225,000 ($0.12 over), Prime $250 for 1.8 million ($0.15 over), Elite $500 for 2.4 million ($0.22 over, MCP included), Enterprise on request. MinuteCast is a separate product, 50 calls a day free, Lite $25 for 10,000, Full $100 for 675,000. Lightning is Enterprise only (https://developer.accuweather.com/llms-full.txt). The previous free tier was retired with the new portal and old trial accounts have to sign up again (https://developer.accuweather.com/faq).", "priceSummary": "$2 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 27, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.accuweather.com/documentation/overview", "llmsTxt": "https://developer.accuweather.com/llms.txt", "capabilities": [ "weather.current", "weather.forecast", "weather.alerts", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "llms-txt", "closed-source", "enterprise" ], "graded": true, "anchor": { "graded": true, "score": 49.2, "grade": "D", "agentReady": false, "rank": 1102, "ranked": true, "rankOf": 1510, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 3, "payments": 25, "reliability": 75, "schema": 60, "security": 39, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "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.", "bestFor": "Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user.", "strengths": [ "Official hosted MCP server, 27 read-only tools over all 106 Core Weather GET endpoints, same key as the REST API", "Packages from $2 a month, with published overage rates per 1,000 calls", "llms.txt, llms-full.txt and a Markdown twin for every docs page", "RFC 7807 error bodies and a documented status code table", "Status page with Enterprise and Developer Portal API components and a readable history feed" ], "weaknesses": [ "Terms forbid using the data to train, validate or otherwise inform any AI system", "MCP access only on the trial and Elite ($500 a month)", "No changelog or dated API change found, and the terms allow API changes without notice", "Two calls per new place, a location key lookup then the forecast", "No security.txt, SLA or official SDK, and the MCP guide puts the key in the URL for some clients" ], "agentNotes": [ "Cache location keys. They don't change, and the lookup is the call worth saving", "Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns", "Send the key as a Bearer header, not in the MCP URL, so it stays out of logs", "On 429 wait and retry. On the trial it usually means the 500-call daily allowance is spent until it resets", "Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.2 } ], "editorialScores": { "ergonomics": 60, "maintenance": 3, "payments": 25, "reliability": 75, "schema": 60, "security": 39, "transparency": 27 }, "provenanceScore": 75, "dataQualityScore": 39, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"Authorization: Bearer $ACCUWEATHER_API_KEY\" -H \"Accept-Encoding: gzip\" --compressed \"https://dataservice.accuweather.com/currentconditions/v1/349727\"", "claudeCode": "claude mcp add --transport http accuweather https://dataservice.accuweather.com/mcp --header \"Authorization: Bearer $ACCUWEATHER_API_KEY\"", "config": { "mcpServers": { "accuweather": { "headers": { "Authorization": "Bearer ${ACCUWEATHER_API_KEY}" }, "type": "http", "url": "https://dataservice.accuweather.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/accuweather-api" }, "area": "domain-data", "unitPrices": [ { "item": "Starter package", "unit": "month", "usd": 2, "note": "15,000 calls" }, { "item": "Standard package", "unit": "month", "usd": 25, "note": "225,000 calls" }, { "item": "Elite package", "unit": "month", "usd": 500, "note": "2.4 million calls, MCP access" }, { "item": "Overage on Starter", "unit": "1k-requests", "usd": 0.25 }, { "item": "Overage on Standard", "unit": "1k-requests", "usd": 0.12 }, { "item": "Call on Starter, at the plan cap", "unit": "1k-requests", "usd": 0.13, "note": "$2 over 15,000 calls" } ], "provenance": { "legalEntity": "AccuWeather Intl., LLC (API terms), AccuWeather, Inc. (privacy)", "domain": "accuweather.com", "domainRegistered": "1995-10-27", "endpointOnVendorDomain": true, "terms": "https://developer.accuweather.com/documentation/terms-of-use", "privacy": "https://www.accuweather.com/en/privacy", "statusPage": "https://status.accuweather.com/", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The API terms (updated 2026-04-28) name AccuWeather Intl., LLC under Pennsylvania law and point to the privacy policy at www.accuweather.com/en/privacy.", "www.accuweather.com answered robots.txt with Access Denied on 4 November 2026, so the privacy policy (and the controller AccuWeather, Inc. read there on 1 October) can't be read. The 1 October reading is struck pending the founder.", "security.txt returned 404 on developer.accuweather.com on 1 October.", "status.accuweather.com lists Enterprise API and Developer Portal API components, with a history feed read on 4 November.", "The portal has no release notes or changelog, and the terms reserve the right to change the APIs without notice.", "The old developer portal's free tier was retired at the relaunch, and existing trial accounts had to sign up again." ], "score": 75 }, "dataQuality": { "coverage": "Global, by AccuWeather location key", "coverageRating": 4, "freshness": "Not stated as a cadence. Responses carry an Expires header the docs say to refresh on", "freshnessClass": "hourly", "history": "Past 24 hours of conditions", "historyYears": 0.003, "methodology": "", "sourcesDisclosed": false, "licence": "Proprietary. Two-week cache, no redistribution, no AI training, logo attribution", "licenceClass": "clear", "standing": "", "standingClass": "none", "reuse": "The terms allow caching for up to two weeks to improve the user experience and forbid storing the data for any other purpose, reselling or redistributing it, or using it to train, validate or inform an AI or ML model.", "score": 39, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/accuweather-api.json", "live": { "slug": "accuweather-api", "probe": { "target": "https://dataservice.accuweather.com", "method": "get", "lastAt": "2026-11-08T01:01:16.526696818Z", "lastOk": true, "lastStatus": 404, "lastMs": 58, "authRequired": false, "uptime24h": 100, "uptime30d": 99.95, "p50ms24h": 64, "p95ms24h": 185, "samples24h": 244, "samples30d": 7705, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 267 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 252 }, { "date": "2026-10-23", "probes": 248, "ok": 246 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.accuweather.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:54:09.765377632Z" }, "securityTxt": { "url": "https://accuweather.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:01:16.432488655Z" }, "llmsTxt": { "url": "https://developer.accuweather.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:04.9282674Z" }, "domain": { "domain": "accuweather.com", "registered": "1995-10-27", "source": "https://rdap.verisign.com/com/v1/domain/accuweather.com", "checkedAt": "2026-11-01T14:21:17.097804863Z" }, "pages": [ { "url": "https://www.accuweather.com/en/privacy", "kind": "privacy", "status": 403, "checkedAt": "2026-11-07T14:24:07.943204426Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://developer.accuweather.com/documentation/terms-of-use", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:02:49.028861722Z", "changedAt": "2026-10-21T00:22:22.01168246Z", "fingerprint": "a8458bfdc2a8" } ], "mcpTools": { "url": "https://dataservice.accuweather.com/mcp", "checkedAt": "2026-11-07T01:42:18.856901967Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:42:18.856901967Z" }, "updatedAt": "2026-11-08T01:01:16.526696818Z" } }, "answer": "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 \u0026 trust.", "b": { "slug": "meteosource-mcp", "name": "Meteosource Weather MCP", "vendor": "Meteosource", "vendorUrl": "https://www.meteosource.com", "kind": "mcp", "category": "weather", "summary": "Meteosource's hosted MCP server gives an agent seven tools for place search, forecasts, severe-weather alerts, air quality, 20 years of weather history, and solar and wind production estimates, with a Meteosource API key.", "url": "https://www.anchorterminal.com/tools/meteosource-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json", "dns": "meteosource-mcp.grade.anchorterminal.com", "repo": "https://github.com/Meteosource/meteosource-weather-mcp", "license": "Proprietary service. The repository's MIT licence covers its docs and manifest", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.meteosource.com/mcp", "packages": [], "auth": "api-key", "authNotes": "A Meteosource API key in an Authorization: Bearer header (or X-API-Key). No OAuth. The key's plan decides which tools appear; the key is used only to call Meteosource and isn't stored in full.", "pricing": "freemium", "pricingNotes": "Free plan with 400 calls a day and no card, asking for a mention and backlink; Startup $9 a month (10,000 calls a day); Standard $29 a month; Renewables plan for production tools (checked 2026-11-07).", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://mcp.meteosource.com", "registryName": "com.meteosource/weather", "capabilities": [ "weather.forecast", "weather.historical", "weather.alerts", "weather.air-quality", "energy.solar" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 1048, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 32 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "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.", "bestFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "strengths": [ "Seven compact tools with plan requirements in the descriptions", "Documented error messages with fixes", "Forecasts, alerts, air quality, 20 years of history and solar and wind production", "Free plan with 400 calls a day and no card", "Official registry entry" ], "weaknesses": [ "Plain API key, no OAuth", "No tool annotations", "Status page unreachable and no incident history", "Terms and privacy not found" ], "agentNotes": [ "Call search_places first to resolve a location", "Split history requests over 400 location-days into shorter ranges", "Production tools need the Renewables plan; check which tools the key exposes", "Send the key in a header, never in a URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 25 }, "provenanceScore": 38, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add meteosource --transport http https://mcp.meteosource.com/mcp --header \"Authorization: Bearer $METEOSOURCE_API_KEY\"", "config": { "mcpServers": { "meteosource": { "headers": { "Authorization": "Bearer YOUR_METEOSOURCE_API_KEY" }, "url": "https://mcp.meteosource.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.forecast", "tool": "https://letme.dev/meteosource-mcp" }, "area": "domain-data", "unitPrices": [ { "item": "Startup plan", "unit": "month", "usd": 9, "note": "10,000 calls a day" }, { "item": "Standard plan", "unit": "month", "usd": 29, "note": "20,000 calls a day" } ], "provenance": { "legalEntity": "Meteosource", "domain": "meteosource.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The repository licence names Meteosource (2026). Terms and privacy URLs weren't found at the usual paths." ], "score": 38 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.json", "live": { "slug": "meteosource-mcp", "probe": { "target": "https://mcp.meteosource.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T00:55:52.070466931Z", "lastOk": true, "lastStatus": 200, "lastMs": 108, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 151, "p95ms24h": 199, "samples24h": 63, "samples30d": 63, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-08T00:55:52.070466931Z" } }, "edges": [ { "by": 67, "category": "maintenance", "leads": "meteosource-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 3, "b": 70 } }, { "by": 40, "category": "reliability", "leads": "accuweather-api", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 75, "b": 35 } }, { "by": 19, "category": "transparency", "leads": "accuweather-api", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 51, "b": 32 } }, { "by": 15, "category": "ergonomics", "leads": "meteosource-mcp", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 60, "b": 75 } }, { "by": 12, "category": "schema", "leads": "meteosource-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 60, "b": 72 } }, { "by": 5, "category": "payments", "leads": "meteosource-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 25, "b": 30 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "AccuWeather", "b": "Meteosource", "name": "Vendor" }, { "a": "https://dataservice.accuweather.com", "b": "https://mcp.meteosource.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service. The repository's MIT licence covers its docs and manifest", "name": "Licence" }, { "a": "27", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "com.meteosource/weather", "name": "MCP registry" }, { "a": "2026-04-28", "b": "no document linked", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 trust.", "question": "Which is better for AI agents, AccuWeather Core Weather API + MCP or Meteosource Weather MCP?" }, { "answer": "Both need an API key.", "question": "Do AccuWeather Core Weather API + MCP and Meteosource Weather MCP need an API key?" }, { "answer": "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.", "question": "Can an agent call AccuWeather Core Weather API + MCP and Meteosource Weather MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 35", "Transparency \u0026 trust, 51 against 32" ], "also": null, "goodFor": "Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user.", "slug": "accuweather-api", "watchFor": "Terms forbid using the data to train, validate or otherwise inform any AI system" }, { "aheadOn": [ "Schema \u0026 documentation, 72 against 60", "Agent ergonomics, 75 against 60", "Payments \u0026 pricing, 30 against 25", "Maintenance \u0026 community, 70 against 3" ], "also": null, "goodFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "slug": "meteosource-mcp", "watchFor": "Plain API key, no OAuth" } ], "history": { "accuweather-api": [ { "causes": [ "evidence", "time" ], "date": "2026-11-04", "delta": 0.6, "from": 48.6, "fromGrade": "D", "to": 49.2, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 48.4, "fromGrade": "D", "to": 48.6, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.4, "from": 48.8, "fromGrade": "D", "to": 48.4, "toGrade": "D" } ], "meteosource-mcp": null }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-google-weather-api.json", "title": "AccuWeather Core Weather API + MCP vs Google Weather API (Maps Platform)", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-google-weather-api" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-met-office-datahub.json", "title": "AccuWeather Core Weather API + MCP vs Met Office Weather DataHub (Site Specific)", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-met-office-datahub" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.json", "title": "AccuWeather Core Weather API + MCP vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.json", "title": "AccuWeather Core Weather API + MCP vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api.json", "title": "AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-openweather-one-call.json", "title": "AccuWeather Core Weather API + MCP vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-pirate-weather.json", "title": "AccuWeather Core Weather API + MCP vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.json", "title": "AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing.json", "title": "AccuWeather Core Weather API + MCP vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.json", "title": "AccuWeather Core Weather API + MCP vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-weatherapi-com.json", "title": "AccuWeather Core Weather API + MCP vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-weatherbit.json", "title": "AccuWeather Core Weather API + MCP vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-xweather.json", "title": "AccuWeather Core Weather API + MCP vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-stormglass.json", "title": "AccuWeather Core Weather API + MCP vs Stormglass API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-stormglass" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp.json", "title": "Google Weather API (Maps Platform) vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp.json", "title": "Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.json", "title": "meteoblue Weather API vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.json", "title": "Meteomatics Weather API vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.json", "title": "Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.json", "title": "Meteosource Weather MCP vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.json", "title": "Meteosource Weather MCP vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.json", "title": "Meteosource Weather MCP vs Stormglass API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.json", "title": "Meteosource Weather MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.json", "title": "Meteosource Weather MCP vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.json", "title": "Meteosource Weather MCP vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.json", "title": "Meteosource Weather MCP vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit.json", "title": "Meteosource Weather MCP vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather.json", "title": "Meteosource Weather MCP vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-open-meteo.json", "title": "AccuWeather Core Weather API + MCP vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-open-meteo" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.json", "title": "Meteosource Weather MCP vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo" } ], "panel": null, "scores": [ { "accuweather-api": 75, "by": 40, "edge": "accuweather-api", "key": "reliability", "meteosource-mcp": 35, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "accuweather-api": 60, "by": 12, "edge": "meteosource-mcp", "key": "schema", "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "weight": 13 }, { "accuweather-api": 60, "by": 15, "edge": "meteosource-mcp", "key": "ergonomics", "meteosource-mcp": 75, "name": "Agent ergonomics", "weight": 13 }, { "accuweather-api": 39, "by": 3, "edge": "meteosource-mcp", "key": "security", "meteosource-mcp": 42, "name": "Security \u0026 auth", "weight": 14 }, { "accuweather-api": 25, "by": 5, "edge": "meteosource-mcp", "key": "payments", "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "accuweather-api": 3, "by": 67, "edge": "meteosource-mcp", "key": "maintenance", "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "weight": 7 }, { "accuweather-api": 51, "by": 19, "edge": "accuweather-api", "key": "transparency", "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 trust. Both do weather forecasts.", "tasks": null, "tutorials": [], "verdicts": { "accuweather-api": "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-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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp", "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.min.md" }, "markdown": "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 \u0026 trust. Both do weather forecasts.\n\n- AccuWeather Core Weather API + MCP: grade D, 49.2/100, rank #1102 of 1510. Markdown https://www.anchorterminal.com/tools/accuweather-api.md · JSON https://www.anchorterminal.com/api/v1/tools/accuweather-api.json\n- Meteosource Weather MCP: grade D, 50.9/100, rank #1048 of 1510. Markdown https://www.anchorterminal.com/tools/meteosource-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n- Best weather and climate data APIs for AI agents: https://www.anchorterminal.com/best/weather/index.md\n- All 136 weather comparisons: https://www.anchorterminal.com/compare/weather/index.md\n\n## Which one, for what\n\n### AccuWeather Core Weather API + MCP (D)\n\nGood for: Consumer-facing current conditions and forecasts where the AccuWeather name matters to the user.\n\nAhead on:\n- Reliability, 75 against 35\n- Transparency \u0026 trust, 51 against 32\n\nWatch for: Terms forbid using the data to train, validate or otherwise inform any AI system\n\n### Meteosource Weather MCP (D)\n\nGood for: Agents that answer weather questions, plan around severe weather or estimate solar and wind output.\n\nAhead on:\n- Schema \u0026 documentation, 72 against 60\n- Agent ergonomics, 75 against 60\n- Payments \u0026 pricing, 30 against 25\n- Maintenance \u0026 community, 70 against 3\n\nWatch for: Plain API key, no OAuth\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Meteosource Weather MCP +67\n\n- 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.\n- 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.\n\n### Reliability: AccuWeather Core Weather API + MCP +40\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: AccuWeather Core Weather API + MCP +19\n\n- 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.\n- 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.\n\n### Agent ergonomics: Meteosource Weather MCP +15\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Meteosource Weather MCP +12\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Meteosource Weather MCP +5\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | AccuWeather Core Weather API + MCP | Meteosource Weather MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 35 | AccuWeather Core Weather API + MCP +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 72 | Meteosource Weather MCP +12 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 75 | Meteosource Weather MCP +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 39 | 42 | Meteosource Weather MCP +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 30 | Meteosource Weather MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 3 | 70 | Meteosource Weather MCP +67 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 51 | 32 | AccuWeather Core Weather API + MCP +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.2 · D** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | AccuWeather Core Weather API + MCP | Meteosource Weather MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | AccuWeather | Meteosource |\n| Hosted endpoint | `https://dataservice.accuweather.com` | `https://mcp.meteosource.com/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service. The repository's MIT licence covers its docs and manifest |\n| Tools exposed | 27 | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| MCP registry | not listed | `com.meteosource/weather` |\n| Terms last updated | 2026-04-28 | no document linked |\n| Privacy policy last updated | couldn't be read | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Agent reviews | 2.5/5 (2) | none |\n\n## How the scores have moved\n\n### AccuWeather Core Weather API + MCP\n\n- +0.6 on 4 November 2026: new evidence, time\n- +0.2 on 27 October 2026: checklist\n- -0.4 on 8 October 2026: checklist\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### AccuWeather Core Weather API + MCP\n\n1. Cache location keys. They don't change, and the lookup is the call worth saving\n2. Use the geoposition search first when you hold coordinates, then the forecast tools with the key it returns\n3. Send the key as a Bearer header, not in the MCP URL, so it stays out of logs\n4. On 429 wait and retry. On the trial it usually means the 500-call daily allowance is spent until it resets\n5. Show the AccuWeather name and logo next to the data, and keep nothing older than two weeks\n\n### Meteosource Weather MCP\n\n1. Call search_places first to resolve a location\n2. Split history requests over 400 location-days into shorter ranges\n3. Production tools need the Renewables plan; check which tools the key exposes\n4. Send the key in a header, never in a URL\n\n## Questions\n\n### Which is better for AI agents, AccuWeather Core Weather API + MCP or Meteosource Weather MCP?\n\nMeteosource 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 \u0026 trust.\n\n### Do AccuWeather Core Weather API + MCP and Meteosource Weather MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call AccuWeather Core Weather API + MCP and Meteosource Weather MCP without installing anything?\n\nYes. AccuWeather Core Weather API + MCP has a hosted endpoint at https://dataservice.accuweather.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"accuweather-api\", \"b\": \"meteosource-mcp\"}`. From a terminal: `anchor compare accuweather-api meteosource-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/accuweather-api.json and https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n\n## Other comparisons with AccuWeather Core Weather API + MCP or Meteosource Weather MCP\n\n- [AccuWeather Core Weather API + MCP vs Google Weather API (Maps Platform)](https://www.anchorterminal.com/compare/accuweather-api-vs-google-weather-api.md)\n- [AccuWeather Core Weather API + MCP vs Met Office Weather DataHub (Site Specific)](https://www.anchorterminal.com/compare/accuweather-api-vs-met-office-datahub.md)\n- [AccuWeather Core Weather API + MCP vs meteoblue Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.md)\n- [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md)\n- [AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api.md)\n- [AccuWeather Core Weather API + MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/accuweather-api-vs-openweather-one-call.md)\n- [AccuWeather Core Weather API + MCP vs Pirate Weather](https://www.anchorterminal.com/compare/accuweather-api-vs-pirate-weather.md)\n- [AccuWeather Core Weather API + MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-tomorrow-io.md)\n- [AccuWeather Core Weather API + MCP vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing.md)\n- [AccuWeather Core Weather API + MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.md)\n- [AccuWeather Core Weather API + MCP vs WeatherAPI.com](https://www.anchorterminal.com/compare/accuweather-api-vs-weatherapi-com.md)\n- [AccuWeather Core Weather API + MCP vs Weatherbit API](https://www.anchorterminal.com/compare/accuweather-api-vs-weatherbit.md)\n- [AccuWeather Core Weather API + MCP vs Xweather Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-xweather.md)\n- [AccuWeather Core Weather API + MCP vs Stormglass API](https://www.anchorterminal.com/compare/accuweather-api-vs-stormglass.md)\n- [Google Weather API (Maps Platform) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp.md)\n- [Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp.md)\n- [meteoblue Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.md)\n- [Meteomatics Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.md)\n- [Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.md)\n- [Meteosource Weather MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.md)\n- [Meteosource Weather MCP vs Pirate Weather](https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.md)\n- [Meteosource Weather MCP vs Stormglass API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.md)\n- [Meteosource Weather MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.md)\n- [Meteosource Weather MCP vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.md)\n- [Meteosource Weather MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.md)\n- [Meteosource Weather MCP vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.md)\n- [Meteosource Weather MCP vs Weatherbit API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit.md)\n- [Meteosource Weather MCP vs Xweather Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather.md)\n- [AccuWeather Core Weather API + MCP vs Open-Meteo](https://www.anchorterminal.com/compare/accuweather-api-vs-open-meteo.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "AccuWeather Core Weather API + MCP vs Meteosource Weather MCP", "url": "" } ], "description": "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.", "facts": [ "AccuWeather Core Weather API + MCP D 49.2", "Meteosource Weather MCP D 50.9", "scores" ], "h1": "AccuWeather Core Weather API + MCP vs Meteosource Weather MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/accuweather-api-vs-meteosource-mcp", "published": "2026-10-01", "section": "tools", "title": "AccuWeather Core Weather vs Meteosource Weather MCP (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp" }, "tokens": { "markdown": 4650, "slim": 2480 }, "version": 1 }