{ "data": { "a": { "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" } }, "answer": "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 \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "weather-company", "name": "The Weather Company Data APIs", "vendor": "The Weather Company, LLC", "vendorUrl": "https://www.weathercompany.com", "kind": "http-api", "category": "weather", "summary": "The Weather Company Data APIs return current conditions, forecasts to 15 days, historical data, government alerts, imagery and aviation weather from the company behind weather.com. Access is by API key at `api.weather.com`, sold in packages to businesses.", "url": "https://www.anchorterminal.com/tools/weather-company", "markdownUrl": "https://www.anchorterminal.com/tools/weather-company.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/weather-company.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/weather-company.json", "dns": "weather-company.grade.anchorterminal.com", "license": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "transports": [ "http" ], "remoteUrl": "https://api.weather.com", "packages": [], "auth": "api-key", "authNotes": "An API key is required and is sent as the `apiKey` query parameter on every request. No header option is documented. Keys are not self-serve. A person requests a 30-day trial by form or contacts sales, the company provisions the key, and the key is read in the API customer portal after an invitation. Each key is entitled to the endpoints in the customer's package, and an endpoint outside it returns 401.", "pricing": "paid", "pricingNotes": "Standard package $500 a month on an annual plan for 1 million API calls. Enterprise plans and add-on packages are by quote, and overage is charged as the contract defines. A free 30-day trial allows 50,000 calls a day at 100 a minute, is requested by form and is limited to enterprise customers, so an agent cannot start without a person and sales approval (checked 2026-10-08).", "priceSummary": "$500 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer documentation, the API references or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.weather.com/docs/home", "llmsTxt": "https://developer.weather.com/llms-full.txt", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "paid", "enterprise", "sales-led", "closed-source", "status-page", "api-key", "aviation", "air-quality" ], "lastRelease": "2026-10-15", "graded": true, "anchor": { "graded": true, "score": 54.5, "grade": "C", "agentReady": false, "rank": 911, "ranked": true, "rankOf": 1510, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 75, "schema": 77, "security": 47, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "A wide weather data API with 168 API references built from OpenAPI documents, Markdown docs for agents, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.", "bestFor": "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.", "strengths": [ "168 API reference sections on developer.weather.com are generated from OpenAPI documents, with enums, patterns, required fields, example responses and documented response codes.", "The whole documentation is served as Markdown at /llms-full.txt.", "History on Demand returns hourly gridded history at about 4 km from June 2015, in JSON, CSV or Parquet, with paging, field selection and a compact mode.", "The status page lists 16 components. Its feed shows 14 incidents from 6 August to 28 October 2026, each confined to one API, region or upstream source.", "The Standard package price is public, $500 a month on an annual plan for 1 million calls, and the trial allows 50,000 calls a day for 30 days." ], "weaknesses": [ "No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.", "The API key is accepted only as the `apiKey` query parameter, so it appears in every request URL. No header option is documented.", "The website terms of use say they do not apply to the data APIs and point to separate terms, which we did not find published.", "Exceeding a rate limit returns 401, the same status as a missing key. No 429 or Retry-After is documented.", "No downloadable OpenAPI file, no official SDK and no MCP server were found. Two dated changelog entries appeared in 18 API references read." ], "agentNotes": [ "Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.", "Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.", "Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.", "Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.", "Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.5 } ], "editorialScores": { "ergonomics": 54, "maintenance": 36, "payments": 20, "reliability": 75, "schema": 77, "security": 47, "transparency": 20 }, "provenanceScore": 80, "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 --compressed \"https://api.weather.com/v3/wx/forecast/daily/3day?geocode=33.74,-84.39\u0026units=e\u0026language=en-US\u0026format=json\u0026apiKey=$TWC_API_KEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/weather-company" }, "area": "domain-data", "unitPrices": [ { "item": "Standard package, annual plan", "unit": "month", "usd": 500, "note": "1 million API calls a month" }, { "item": "Call on Standard, at the plan cap", "unit": "1k-requests", "usd": 0.5, "note": "$500 over 1 million calls" } ], "provenance": { "legalEntity": "The Weather Company, LLC", "domain": "weather.com", "domainRegistered": "1994-08-09", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://weather.com/privacy/privacy-policy", "statusPage": "https://theweathercompanyapis.statuspage.io", "changelog": "", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy policy, effective 30 April 2026, names The Weather Company, LLC, 1001 Summit Boulevard NE, Brookhaven, GA 30319. Its section on data collection outside consumer products covers developer.weather.com enquiries and business customers.", "No terms document is given. The website terms of use (updated 16 April 2026) say they do not apply to the business data APIs, and the separate terms they refer to were not found on the pricing, trial or documentation pages.", "The API answers at api.weather.com and the documentation at developer.weather.com. The company site is www.weathercompany.com (registered 1998-03-24).", "weather.com/.well-known/security.txt gives a security contact and expires on 31 December 2026. www.weathercompany.com and developer.weather.com return 404 for the same path.", "RDAP for weather.com gives a registration date of 1994-08-09 and CSC Corporate Domains, Inc. as registrar.", "There is no central changelog. Each API reference has its own changelog section, most of them empty." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/weather-company.json", "live": { "slug": "weather-company", "probe": { "target": "https://api.weather.com", "method": "get", "lastAt": "2026-11-08T00:56:14.081945539Z", "lastOk": true, "lastStatus": 401, "lastMs": 62, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 105, "samples24h": 244, "samples30d": 7486, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "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": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "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": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://theweathercompanyapis.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:55:43.322245168Z" }, "securityTxt": { "url": "https://weather.com/.well-known/security.txt", "state": "valid", "expires": "2026-12-31T16:00:00.000Z", "checkedAt": "2026-11-07T16:01:16.571847049Z" }, "llmsTxt": { "url": "https://developer.weather.com/llms-full.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:22.215139957Z" }, "domain": { "domain": "weather.com", "registered": "1994-08-09", "source": "https://rdap.verisign.com/com/v1/domain/weather.com", "checkedAt": "2026-11-01T14:22:39.617017385Z" }, "pages": [ { "url": "https://weather.com/privacy/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:23:40.369310347Z", "changedAt": "2026-10-29T05:18:40.675881165Z", "fingerprint": "08bbf067ab6c" } ], "updatedAt": "2026-11-08T00:56:14.081945539Z" } }, "edges": [ { "by": 40, "category": "reliability", "leads": "weather-company", "name": "Reliability", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 35, "b": 75 } }, { "by": 34, "category": "maintenance", "leads": "meteosource-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 70, "b": 36 } }, { "by": 21, "category": "ergonomics", "leads": "meteosource-mcp", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 75, "b": 54 } }, { "by": 18, "category": "transparency", "leads": "weather-company", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 32, "b": 50 } }, { "by": 10, "category": "payments", "leads": "meteosource-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 30, "b": 20 } }, { "by": 5, "category": "schema", "leads": "weather-company", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 72, "b": 77 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Meteosource", "b": "The Weather Company, LLC", "name": "Vendor" }, { "a": "https://mcp.meteosource.com/mcp", "b": "https://api.weather.com", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The repository's MIT licence covers its docs and manifest", "b": "Proprietary service. Use is under a content licensing agreement with The Weather Company, which is not published", "name": "Licence" }, { "a": "7", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "com.meteosource/weather", "b": "not listed", "name": "MCP registry" }, { "a": "none", "b": "2026-10-15", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "no document linked", "b": "couldn't be read", "name": "Privacy policy last updated" } ], "faq": [ { "answer": "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 \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Meteosource Weather MCP or The Weather Company Data APIs?" }, { "answer": "Both need an API key.", "question": "Do Meteosource Weather MCP and The Weather Company Data APIs need an API key?" }, { "answer": "Yes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and The Weather Company Data APIs at https://api.weather.com.", "question": "Can an agent call Meteosource Weather MCP and The Weather Company Data APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 75 against 54", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 70 against 36" ], "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" }, { "aheadOn": [ "Reliability, 75 against 35", "Schema \u0026 documentation, 77 against 72", "Security \u0026 auth, 47 against 42", "Transparency \u0026 trust, 50 against 32" ], "also": null, "goodFor": "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.", "slug": "weather-company", "watchFor": "No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form." } ], "history": { "meteosource-mcp": null, "weather-company": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-04", "delta": 1.8, "from": 52.7, "fromGrade": "D", "to": 54.5, "toGrade": "C" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 52.6, "fromGrade": "D", "to": 52.7, "toGrade": "D" } ] }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "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/google-weather-api-vs-weather-company.json", "title": "Google Weather API (Maps Platform) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company.json", "title": "Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.json", "title": "meteoblue Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "title": "Meteomatics Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company.json", "title": "NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.json", "title": "OpenWeather One Call API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company.json", "title": "Pirate Weather vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.json", "title": "Tomorrow.io Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.json", "title": "Visual Crossing Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.json", "title": "The Weather Company Data APIs vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.json", "title": "The Weather Company Data APIs vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/weather-company-vs-xweather.json", "title": "The Weather Company Data APIs vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/weather-company-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.json", "title": "AccuWeather Core Weather API + MCP vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp" }, { "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-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/stormglass-vs-weather-company.json", "title": "Stormglass API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/stormglass-vs-weather-company" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/open-meteo-vs-weather-company.json", "title": "Open-Meteo vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/open-meteo-vs-weather-company" } ], "panel": null, "scores": [ { "by": 40, "edge": "weather-company", "key": "reliability", "meteosource-mcp": 35, "name": "Reliability", "weather-company": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "weather-company", "key": "schema", "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "weather-company": 77, "weight": 13 }, { "by": 21, "edge": "meteosource-mcp", "key": "ergonomics", "meteosource-mcp": 75, "name": "Agent ergonomics", "weather-company": 54, "weight": 13 }, { "by": 5, "edge": "weather-company", "key": "security", "meteosource-mcp": 42, "name": "Security \u0026 auth", "weather-company": 47, "weight": 14 }, { "by": 10, "edge": "meteosource-mcp", "key": "payments", "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "weather-company": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 34, "edge": "meteosource-mcp", "key": "maintenance", "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "weather-company": 36, "weight": 7 }, { "by": 18, "edge": "weather-company", "key": "transparency", "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "weather-company": 50, "weight": 7 } ], "summary": "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 \u0026 pricing and maintenance \u0026 community. Both do weather forecasts.", "tasks": null, "tutorials": [], "verdicts": { "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.", "weather-company": "A wide weather data API with 168 API references built from OpenAPI documents, Markdown docs for agents, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company", "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.min.md" }, "markdown": "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 \u0026 pricing and maintenance \u0026 community. Both do weather forecasts.\n\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- The Weather Company Data APIs: grade C, 54.5/100, rank #911 of 1510. Markdown https://www.anchorterminal.com/tools/weather-company.md · JSON https://www.anchorterminal.com/api/v1/tools/weather-company.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### 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- Agent ergonomics, 75 against 54\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 70 against 36\n\nWatch for: Plain API key, no OAuth\n\n### The Weather Company Data APIs (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 75 against 35\n- Schema \u0026 documentation, 77 against 72\n- Security \u0026 auth, 47 against 42\n- Transparency \u0026 trust, 50 against 32\n\nWatch for: No self-serve signup. The trial is requested through a form, is limited to enterprise customers, and the Buy now button opens a contact form.\n\n\n## Why the edge\n\n### Reliability: The Weather Company Data APIs +40\n\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- 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).\n\n### Maintenance \u0026 community: Meteosource Weather MCP +34\n\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- 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).\n\n### Agent ergonomics: Meteosource Weather MCP +21\n\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- 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).\n\n### Transparency \u0026 trust: The Weather Company Data APIs +18\n\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- 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).\n\n### Payments \u0026 pricing: Meteosource Weather MCP +10\n\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- 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).\n\n### Schema \u0026 documentation: The Weather Company Data APIs +5\n\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- 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).\n\n## Score by category\n\n| Category | Weight | Meteosource Weather MCP | The Weather Company Data APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 75 | The Weather Company Data APIs +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 77 | The Weather Company Data APIs +5 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 54 | Meteosource Weather MCP +21 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 47 | The Weather Company Data APIs +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Meteosource Weather MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 36 | Meteosource Weather MCP +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 50 | The Weather Company Data APIs +18 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.9 · D** | **54.5 · C** | |\n\n## Facts side by side\n\n| Fact | Meteosource Weather MCP | The Weather Company Data APIs |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Meteosource | The Weather Company, LLC |\n| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.weather.com` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 7 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `com.meteosource/weather` | not listed |\n| Last release | none | 2026-10-15 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | couldn't be read |\n\n## How the scores have moved\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n### The Weather Company Data APIs\n\n- +1.8 on 4 November 2026 (D to C): new evidence, correction\n- +0.1 on 28 October 2026: new evidence\n\n## Verdicts\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**The Weather Company Data APIs.** A wide weather data API with 168 API references built from OpenAPI documents, Markdown docs for agents, hourly history from June 2015 and a status page with component history. Keys come only through a sales-reviewed trial or contract, travel only in the URL, and the terms that govern the API are not published.\n\n## Before you call either\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### The Weather Company Data APIs\n\n1. Send `units`, `language` and `format=json` with a location on every v3 call, plus `Accept-Encoding: gzip`, which the usage guide marks as required.\n2. Keep the key out of logs and client-side code, because it travels in the query string as `apiKey`.\n3. Treat a 401 as either a bad key, an endpoint outside the key's package or an exceeded limit, and treat a 204 as no data for the query.\n4. Each forecast duration (`3day` to `15day`) is a separate entitlement. Request only durations the contract covers.\n5. Use `/v3/aggcommon` to combine up to 10 products in one request. Each product and each location still counts as one call.\n\n## Questions\n\n### Which is better for AI agents, Meteosource Weather MCP or The Weather Company Data APIs?\n\nThe 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 \u0026 pricing and maintenance \u0026 community.\n\n### Do Meteosource Weather MCP and The Weather Company Data APIs need an API key?\n\nBoth need an API key.\n\n### Can an agent call Meteosource Weather MCP and The Weather Company Data APIs without installing anything?\n\nYes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and The Weather Company Data APIs at https://api.weather.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteosource-mcp\", \"b\": \"weather-company\"}`. From a terminal: `anchor compare meteosource-mcp weather-company`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json and https://www.anchorterminal.com/api/v1/tools/weather-company.json\n\n## Other comparisons with Meteosource Weather MCP or The Weather Company Data APIs\n\n- [AccuWeather Core Weather API + MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/accuweather-api-vs-weather-company.md)\n- [Google Weather API (Maps Platform) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/google-weather-api-vs-weather-company.md)\n- [Met Office Weather DataHub (Site Specific) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/met-office-datahub-vs-weather-company.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)\n- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)\n- [NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/nws-api-vs-weather-company.md)\n- [OpenWeather One Call API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/openweather-one-call-vs-weather-company.md)\n- [Pirate Weather vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/pirate-weather-vs-weather-company.md)\n- [Tomorrow.io Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/tomorrow-io-vs-weather-company.md)\n- [Visual Crossing Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.md)\n- [The Weather Company Data APIs vs WeatherAPI.com](https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.md)\n- [The Weather Company Data APIs vs Weatherbit API](https://www.anchorterminal.com/compare/weather-company-vs-weatherbit.md)\n- [The Weather Company Data APIs vs Xweather Weather API](https://www.anchorterminal.com/compare/weather-company-vs-xweather.md)\n- [AccuWeather Core Weather API + MCP vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.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 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- [Stormglass API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/stormglass-vs-weather-company.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n- [Open-Meteo vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/open-meteo-vs-weather-company.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": "Meteosource Weather MCP vs The Weather Company Data APIs", "url": "" } ], "description": "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.", "facts": [ "Meteosource Weather MCP D 50.9", "The Weather Company Data APIs C 54.5", "scores" ], "h1": "Meteosource Weather MCP vs The Weather Company Data APIs", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteosource-mcp-vs-weather-company", "published": "2026-10-01", "section": "tools", "title": "Meteosource Weather MCP vs The Weather Company Data (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company" }, "tokens": { "markdown": 4650, "slim": 2430 }, "version": 1 }