{ "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": "WeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "weatherapi-com", "name": "WeatherAPI.com", "vendor": "WeatherAPI.com (Zoomash Ltd)", "vendorUrl": "https://www.weatherapi.com", "kind": "http-api", "category": "weather", "summary": "Weather API for current conditions, forecasts, history, marine data, alerts, air quality, solar PV output and agriculture indices, queried by location over REST with an API key.", "url": "https://www.anchorterminal.com/tools/weatherapi-com", "markdownUrl": "https://www.anchorterminal.com/tools/weatherapi-com.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/weatherapi-com.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/weatherapi-com.json", "dns": "weatherapi-com.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.weatherapi.com/v1", "packages": [], "auth": "api-key", "authNotes": "The key goes in the key query parameter on every request. Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, sharing the plan's quota and response settings; none can be scoped. The terms tie one key to one application.", "pricing": "freemium", "pricingNotes": "Free at 100,000 calls a month with a 3-day forecast and 1 day of history, no card. Starter $7 a month ($75 a year) for 3 million calls, 7-day forecast and 7 days of history. Pro+ $25 ($270 a year) for 5 million calls, 14-day forecast, 365 days of history, marine with tides and bulk requests. Business $65 ($702 a year) for 10 million calls, history back to 2010-01-01, the Solar and Agriculture APIs and 99.9 per cent uptime. High Volume plans from 20 million calls for $95 a month to 500 million for $1,275, chosen from the dashboard. Enterprise on request. Paid plans start with a 7-day trial (https://www.weatherapi.com/pricing, checked 2026-11-02).", "priceSummary": "$7 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://www.weatherapi.com/docs/", "llmsTxt": "https://www.weatherapi.com/llms.txt", "openapi": "https://www.weatherapi.com/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "closed-source", "uk" ], "graded": true, "anchor": { "graded": true, "score": 64.6, "grade": "B", "agentReady": false, "rank": 460, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 60, "payments": 30, "reliability": 80, "schema": 89, "security": 37, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found.", "bestFor": "Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.", "strengths": [ "3 million calls for $7 a month, and 100,000 a month free with no card", "OpenAPI 3.1 file (version 1.0.4, 14 paths) with structured errors, 15 numbered error codes, and llms.txt", "Field filters (current_fields, day_fields, hour_fields) to trim responses", "Monthly quotas published for every plan up to 500 million calls, and 99.9 per cent with service credits for High Volume customers", "12 months' written notice before an API deprecation, in the terms" ], "weaknesses": [ "Key only in the query string, keys can't be scoped, and no security.txt", "Privacy policy undated, with template placeholders and transfers to Russia and China", "SDKs for Node.js, Java, PHP and Go untouched since 2020 and 2021", "No full list of data sources or models", "The status page has never posted an incident, while its API monitor shows downtime and the changelog mentions a key-store outage" ], "agentNotes": [ "Pass current_fields, day_fields or hour_fields to cut the response to what you need", "Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429", "Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names", "Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms", "Keep one named key per app (up to 5 per account); keys share one monthly quota, so a runaway agent on one key can exhaust them all." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.6 } ], "editorialScores": { "ergonomics": 80, "maintenance": 60, "payments": 30, "reliability": 80, "schema": 89, "security": 37, "transparency": 49 }, "provenanceScore": 81, "dataQualityScore": 49, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.weatherapi.com/v1/forecast.json?key=$WEATHERAPI_KEY\u0026q=51.51,-0.13\u0026days=3\u0026aqi=no\u0026alerts=no\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/weatherapi-com" }, "area": "domain-data", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 7, "note": "3 million calls, $75 a year" }, { "item": "Pro+ plan", "unit": "month", "usd": 25, "note": "5 million calls, $270 a year" }, { "item": "Business plan", "unit": "month", "usd": 65, "note": "10 million calls, $702 a year" }, { "item": "High Volume plan, 20 million calls", "unit": "month", "usd": 95, "note": "Up to 500 million calls for $1,275 a month, from the dashboard" }, { "item": "Call on Starter, at the plan cap", "unit": "1k-requests", "usd": 0.0023, "note": "$7 over 3 million calls" }, { "item": "Call on Business, at the plan cap", "unit": "1k-requests", "usd": 0.0065, "note": "$65 over 10 million calls" } ], "provenance": { "legalEntity": "Zoomash Ltd", "domain": "weatherapi.com", "domainRegistered": "2014-11-29", "endpointOnVendorDomain": true, "terms": "https://www.weatherapi.com/terms.aspx", "privacy": "https://www.weatherapi.com/privacy.aspx", "statusPage": "https://status.weatherapi.com/", "changelog": "https://www.weatherapi.com/api-changelog.html", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "The terms name Zoomash Ltd under the law of England and Wales but give no registered address or company number, and the privacy policy names no entity beyond WeatherAPI.com.", "The privacy policy says personal data may be transferred to the USA, Russia, Japan, China and India, and names Stripe for payments.", "The status page at status.weatherapi.com runs on Better Stack. Its RSS feed and Previous incidents page list no incident (2 November 2026).", "www.weatherapi.com/.well-known/security.txt returns an HTML page-not-found answer (re-read 2 November 2026).", "The website moved to ASP.NET Core in October 2026 with cleaner addresses (/pricing, /terms, /privacy), and the changelog says old links redirect; the terms and privacy URLs here are the addresses the policy readings used." ], "score": 81 }, "dataQuality": { "coverage": "Global, any coordinate, city, postcode or IP", "coverageRating": 4, "freshness": "Not stated. The terms allow current conditions to be cached for 60 minutes", "freshnessClass": "hourly", "history": "From 2010-01-01 on Business, 365 days on Pro+", "historyYears": 16, "methodology": "", "sourcesDisclosed": false, "licence": "Proprietary. Cache limits, no resale, attribution on Free", "licenceClass": "clear", "standing": "", "standingClass": "none", "reuse": "The terms cap caching at 60 minutes for current and 24 hours for forecast, forbid selling the data on, and end any right to keep it when the subscription ends. Showing it in your own app or service is allowed.", "score": 49, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/weatherapi-com.json", "live": { "slug": "weatherapi-com", "probe": { "target": "https://api.weatherapi.com/v1", "method": "get", "lastAt": "2026-11-08T00:56:14.14457494Z", "lastOk": true, "lastStatus": 404, "lastMs": 198, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 82, "p95ms24h": 264, "samples24h": 244, "samples30d": 7704, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "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://status.weatherapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:32:36.521387184Z" }, "securityTxt": { "url": "https://weatherapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:52.556130293Z" }, "llmsTxt": { "url": "https://www.weatherapi.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:20.835396581Z" }, "domain": { "domain": "weatherapi.com", "registered": "2014-11-29", "source": "https://rdap.verisign.com/com/v1/domain/weatherapi.com", "checkedAt": "2026-11-01T14:18:16.129956027Z" }, "pages": [ { "url": "https://www.weatherapi.com/api-changelog.html", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:36:53.169548049Z", "changedAt": "2026-11-07T14:36:53.169548049Z", "fingerprint": "d0ba9aca95e8" }, { "url": "https://www.weatherapi.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:36:58.551927904Z", "changedAt": "2026-11-07T14:36:58.551927904Z", "fingerprint": "5aaeaf19355f" }, { "url": "https://www.weatherapi.com/pricing.aspx", "kind": "pricing", "status": 200, "checkedAt": "2026-11-02T07:39:41.547838366Z", "changedAt": "2026-11-01T07:06:33.06921532Z", "fingerprint": "34876b084c13" }, { "url": "https://www.weatherapi.com/privacy.aspx", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:36:58.65903773Z", "changedAt": "2026-11-07T14:36:58.65903773Z", "fingerprint": "0e87f1e43657" }, { "url": "https://www.weatherapi.com/terms.aspx", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:03.866755503Z", "changedAt": "2026-11-07T14:37:03.866755503Z", "fingerprint": "a8e324b19501" } ], "updatedAt": "2026-11-08T00:56:14.14457494Z" } }, "edges": [ { "by": 45, "category": "reliability", "leads": "weatherapi-com", "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 status.weatherapi.com on Better Stack, with api.weatherapi.com and the website as components (20). Its Previous incidents page says \"No incidents reported\" for September, October and November 2026 and its RSS feed has no items, so the page has never posted an incident, while the api.weatherapi.com monitor shows 99.839, 99.920 and 99.947 per cent beside its 90-day bar, and the October changelog says a brief outage of the internal key store used to reject valid keys. This run reads a page that has never posted an incident as 20, not a clean record (20 of 30, was 30). Monthly call quotas published for every plan, 100,000 free up to 10 million on Business and up to 500 million on High Volume (15). A spent quota returns 403 with error code 2007, distinct from auth errors, but there's no 429, Retry-After or backoff guidance (5 of 15). The terms promise 99.9 per cent to High Volume customers with service credits, and the plan table lists uptime per plan (10). Generally available (10). 20 + 20 + 15 + 5 + 10 + 10 = 80." }, "scores": { "a": 35, "b": 80 } }, { "by": 33, "category": "transparency", "leads": "weatherapi-com", "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": "Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20)." }, "scores": { "a": 32, "b": 65 } }, { "by": 17, "category": "schema", "leads": "weatherapi-com", "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": "OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though `q` is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15)." }, "scores": { "a": 72, "b": 89 } }, { "by": 10, "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 changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60." }, "scores": { "a": 70, "b": 60 } }, { "by": 5, "category": "ergonomics", "leads": "weatherapi-com", "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": "`current_fields`, `day_fields` and `hour_fields` trim responses, and `aqi`, `alerts` and `days` keep them small. The official MCP server has 11 tools (22 of 25). `days`, `hour`, field filters and bulk requests on Pro+ (17 of 20). Numeric error codes such as 1006 (no location found) and 2007 (quota exceeded) let an agent tell the cases apart (18 of 20). Read-only GETs, and the bulk POST only reads. The MCP tools carry no readOnlyHint annotations (13 of 20). Only `key` and `q` are required, and SDKs exist for Node.js, Java, PHP and Go, but none has a commit since 2021 (10 of 15)." }, "scores": { "a": 75, "b": 80 } }, { "by": 5, "category": "security", "leads": "meteosource-mcp", "name": "Security \u0026 auth", "reasons": { "a": "One API key per account in a header, never in the URL (20 of 30). All tools are reads (10 of 20). Weather data only, no third-party text (10). No audit log (0). No security programme found (2 of 20). Keys travel to the hosted server, which says it doesn't store them in full. 20 + 10 + 10 + 0 + 2 = 42.", "b": "The key goes only in the `key` query parameter, so it lands in URLs and logs (20 less 10). Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, but none can be scoped, and Business adds IP blocking (12 of 30). Read-only data (15 of 20). Alerts come from government agencies (10 of 15). Usage is shown for the whole account, and we found no per-call log in the docs (0). No security.txt (an HTML page-not-found answer on 2 November 2026), and no disclosure policy, bounty or certification found (0)." }, "scores": { "a": 42, "b": 37 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Meteosource", "b": "WeatherAPI.com (Zoomash Ltd)", "name": "Vendor" }, { "a": "https://mcp.meteosource.com/mcp", "b": "https://api.weatherapi.com/v1", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The repository's MIT licence covers its docs and manifest", "b": "none", "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": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "WeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Meteosource Weather MCP or WeatherAPI.com?" }, { "answer": "Both need an API key.", "question": "Do Meteosource Weather MCP and WeatherAPI.com need an API key?" }, { "answer": "Yes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and WeatherAPI.com at https://api.weatherapi.com/v1.", "question": "Can an agent call Meteosource Weather MCP and WeatherAPI.com without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 42 against 37", "Maintenance \u0026 community, 70 against 60" ], "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, 80 against 35", "Schema \u0026 documentation, 89 against 72", "Agent ergonomics, 80 against 75", "Transparency \u0026 trust, 65 against 32" ], "also": [ "Free to start without a card" ], "goodFor": "Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.", "slug": "weatherapi-com", "watchFor": "Key only in the query string, keys can't be scoped, and no security.txt" } ], "history": { "meteosource-mcp": null, "weatherapi-com": [ { "causes": [ "product", "correction" ], "date": "2026-11-02", "delta": -0.7, "from": 65.3, "fromGrade": "B", "to": 64.6, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.5, "from": 65.8, "fromGrade": "B", "to": 65.3, "toGrade": "B" } ] }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "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/google-weather-api-vs-weatherapi-com.json", "title": "Google Weather API (Maps Platform) vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weatherapi-com.json", "title": "Met Office Weather DataHub (Site Specific) vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.json", "title": "meteoblue Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.json", "title": "Meteomatics Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.json", "title": "NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com.json", "title": "OpenWeather One Call API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-weatherapi-com.json", "title": "Pirate Weather vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.json", "title": "Tomorrow.io Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com.json", "title": "Visual Crossing Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com" }, { "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/weatherapi-com-vs-weatherbit.json", "title": "WeatherAPI.com vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/weatherapi-com-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/weatherapi-com-vs-xweather.json", "title": "WeatherAPI.com vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/weatherapi-com-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-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-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-weatherapi-com.json", "title": "Stormglass API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/stormglass-vs-weatherapi-com" }, { "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-weatherapi-com.json", "title": "Open-Meteo vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/open-meteo-vs-weatherapi-com" } ], "panel": null, "scores": [ { "by": 45, "edge": "weatherapi-com", "key": "reliability", "meteosource-mcp": 35, "name": "Reliability", "weatherapi-com": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 17, "edge": "weatherapi-com", "key": "schema", "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "weatherapi-com": 89, "weight": 13 }, { "by": 5, "edge": "weatherapi-com", "key": "ergonomics", "meteosource-mcp": 75, "name": "Agent ergonomics", "weatherapi-com": 80, "weight": 13 }, { "by": 5, "edge": "meteosource-mcp", "key": "security", "meteosource-mcp": 42, "name": "Security \u0026 auth", "weatherapi-com": 37, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "weatherapi-com": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "meteosource-mcp", "key": "maintenance", "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "weatherapi-com": 60, "weight": 7 }, { "by": 33, "edge": "weatherapi-com", "key": "transparency", "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "weatherapi-com": 65, "weight": 7 } ], "summary": "WeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security \u0026 auth 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.", "weatherapi-com": "WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com", "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.min.md" }, "markdown": "WeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security \u0026 auth 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- WeatherAPI.com: grade B, 64.6/100, rank #460 of 1510. Markdown https://www.anchorterminal.com/tools/weatherapi-com.md · JSON https://www.anchorterminal.com/api/v1/tools/weatherapi-com.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- Security \u0026 auth, 42 against 37\n- Maintenance \u0026 community, 70 against 60\n\nWatch for: Plain API key, no OAuth\n\n### WeatherAPI.com (B)\n\nGood for: Cheap, high-volume consumer forecasts where the location arrives as a city, postcode or IP.\n\nAhead on:\n- Reliability, 80 against 35\n- Schema \u0026 documentation, 89 against 72\n- Agent ergonomics, 80 against 75\n- Transparency \u0026 trust, 65 against 32\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Key only in the query string, keys can't be scoped, and no security.txt\n\n\n## Why the edge\n\n### Reliability: WeatherAPI.com +45\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- WeatherAPI.com (80): Status page at status.weatherapi.com on Better Stack, with api.weatherapi.com and the website as components (20). Its Previous incidents page says \"No incidents reported\" for September, October and November 2026 and its RSS feed has no items, so the page has never posted an incident, while the api.weatherapi.com monitor shows 99.839, 99.920 and 99.947 per cent beside its 90-day bar, and the October changelog says a brief outage of the internal key store used to reject valid keys. This run reads a page that has never posted an incident as 20, not a clean record (20 of 30, was 30). Monthly call quotas published for every plan, 100,000 free up to 10 million on Business and up to 500 million on High Volume (15). A spent quota returns 403 with error code 2007, distinct from auth errors, but there's no 429, Retry-After or backoff guidance (5 of 15). The terms promise 99.9 per cent to High Volume customers with service credits, and the plan table lists uptime per plan (10). Generally available (10). 20 + 20 + 15 + 5 + 10 + 10 = 80.\n\n### Transparency \u0026 trust: WeatherAPI.com +33\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- WeatherAPI.com (65): Closed service with terms under English law. The MCP server is MIT (15). The privacy policy is undated, names no entity beyond WeatherAPI.com, logs IP and location, gives no retention periods and leaves template placeholders in its deletion section (8 of 30). The terms promise 12 months' written notice before an API deprecation and 90 days before changes to access rights (18 of 20). Stripe is named, and transfers to the USA, Russia, Japan, China and India are disclosed, but no hosting provider (8 of 20).\n\n### Schema \u0026 documentation: WeatherAPI.com +17\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- WeatherAPI.com (89): OpenAPI 3.1.0 at weatherapi.com/openapi.json, version 1.0.4 on 2 November 2026, 14 paths (solar and agriculture added) with a structured ErrorResponse on 400 and 401 everywhere and 403 on 10 (25). llms.txt at weatherapi.com/llms.txt, published April 2026 per the changelog (10). Endpoint descriptions state purpose and note plan limits (16 of 20). Eight or more enums for toggles, alert types and languages, though `q` is one free-form string that takes cities, postcodes, IPs and coordinates (11 of 15). 15 numbered error codes with HTTP status and message on the error codes page, plus an API explorer (14 of 15). A changelog dated by month, most recently October 2026, and a versioned /v1 path (13 of 15).\n\n### Maintenance \u0026 community: Meteosource Weather MCP +10\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- WeatherAPI.com (60): The changelog has 13 entries dated October 2026, among them the Agriculture API (/agriculture.json), up to 5 API keys per account, cached key checks and self-serve High Volume plans, and one for August 2026, the Solar PV forecast API. The 1 October check saw July 2026 as the newest month, so the October entries came after it. Dated by month only, they are 2 to 32 days old on 2 November. The OpenAPI file, now version 1.0.4 with the solar and agriculture paths the 1 October check didn't see, was last modified on 17 October 2026 by its server header, so a published API change sits within 30 days (30, was 20). 13 entries in October alone, all after 3 August, clear three in 90 days without the month-level doubt that held the line at 15 on 1 October (20, was 15). A public changelog, and support by email we didn't test (8 of 15). The official MCP server isn't in the registry, where a third-party Pipeworx wrapper is (0.2.0 on 2 November), and the SDKs haven't changed since 2020 and 2021 (0). The npm package weatherapi-mcp is at 1.0.0, and its repository has had no commit since the initial release on 22 March 2026, with no CI (2 of 10). 30 + 20 + 8 + 0 + 2 = 60.\n\n### Agent ergonomics: WeatherAPI.com +5\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- WeatherAPI.com (80): `current_fields`, `day_fields` and `hour_fields` trim responses, and `aqi`, `alerts` and `days` keep them small. The official MCP server has 11 tools (22 of 25). `days`, `hour`, field filters and bulk requests on Pro+ (17 of 20). Numeric error codes such as 1006 (no location found) and 2007 (quota exceeded) let an agent tell the cases apart (18 of 20). Read-only GETs, and the bulk POST only reads. The MCP tools carry no readOnlyHint annotations (13 of 20). Only `key` and `q` are required, and SDKs exist for Node.js, Java, PHP and Go, but none has a commit since 2021 (10 of 15).\n\n### Security \u0026 auth: Meteosource Weather MCP +5\n\n- Meteosource Weather MCP (42): One API key per account in a header, never in the URL (20 of 30). All tools are reads (10 of 20). Weather data only, no third-party text (10). No audit log (0). No security programme found (2 of 20). Keys travel to the hosted server, which says it doesn't store them in full. 20 + 10 + 10 + 0 + 2 = 42.\n- WeatherAPI.com (37): The key goes only in the `key` query parameter, so it lands in URLs and logs (20 less 10). Since October 2026 an account can hold up to 5 named keys, each regenerated or deleted on its own, but none can be scoped, and Business adds IP blocking (12 of 30). Read-only data (15 of 20). Alerts come from government agencies (10 of 15). Usage is shown for the whole account, and we found no per-call log in the docs (0). No security.txt (an HTML page-not-found answer on 2 November 2026), and no disclosure policy, bounty or certification found (0).\n\n## Score by category\n\n| Category | Weight | Meteosource Weather MCP | WeatherAPI.com | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 80 | WeatherAPI.com +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 89 | WeatherAPI.com +17 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 80 | WeatherAPI.com +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 37 | Meteosource Weather MCP +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 60 | Meteosource Weather MCP +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 65 | WeatherAPI.com +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.9 · D** | **64.6 · B** | |\n\n## Facts side by side\n\n| Fact | Meteosource Weather MCP | WeatherAPI.com |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Meteosource | WeatherAPI.com (Zoomash Ltd) |\n| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.weatherapi.com/v1` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | none |\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| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n### WeatherAPI.com\n\n- -0.7 on 2 November 2026: product, correction\n- -0.5 on 8 October 2026: checklist\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**WeatherAPI.com.** WeatherAPI.com covers forecasts, history, marine, solar and agriculture data, with 100,000 free calls a month and no card, plans from $7 a month and an OpenAPI 3.1 file. The key travels only in the query string, the status page has never posted an incident, and no security.txt or disclosure policy was found.\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### WeatherAPI.com\n\n1. Pass current_fields, day_fields or hour_fields to cut the response to what you need\n2. Treat a 403 with error code 2007 as the monthly quota, not a bad key. There's no 429\n3. Reuse the id from search.json (q=id:NNN) to avoid ambiguous city names\n4. Cache history freely, current for under an hour and forecasts for under a day, to stay inside the terms\n5. Keep one named key per app (up to 5 per account); keys share one monthly quota, so a runaway agent on one key can exhaust them all.\n\n## Questions\n\n### Which is better for AI agents, Meteosource Weather MCP or WeatherAPI.com?\n\nWeatherAPI.com scores 64.6 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 4 of 7 scored categories. Meteosource Weather MCP leads on security \u0026 auth and maintenance \u0026 community.\n\n### Do Meteosource Weather MCP and WeatherAPI.com need an API key?\n\nBoth need an API key.\n\n### Can an agent call Meteosource Weather MCP and WeatherAPI.com without installing anything?\n\nYes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and WeatherAPI.com at https://api.weatherapi.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteosource-mcp\", \"b\": \"weatherapi-com\"}`. From a terminal: `anchor compare meteosource-mcp weatherapi-com`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json and https://www.anchorterminal.com/api/v1/tools/weatherapi-com.json\n\n## Other comparisons with Meteosource Weather MCP or WeatherAPI.com\n\n- [AccuWeather Core Weather API + MCP vs WeatherAPI.com](https://www.anchorterminal.com/compare/accuweather-api-vs-weatherapi-com.md)\n- [Google Weather API (Maps Platform) vs WeatherAPI.com](https://www.anchorterminal.com/compare/google-weather-api-vs-weatherapi-com.md)\n- [Met Office Weather DataHub (Site Specific) vs WeatherAPI.com](https://www.anchorterminal.com/compare/met-office-datahub-vs-weatherapi-com.md)\n- [meteoblue Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.md)\n- [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md)\n- [NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com](https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.md)\n- [OpenWeather One Call API vs WeatherAPI.com](https://www.anchorterminal.com/compare/openweather-one-call-vs-weatherapi-com.md)\n- [Pirate Weather vs WeatherAPI.com](https://www.anchorterminal.com/compare/pirate-weather-vs-weatherapi-com.md)\n- [Tomorrow.io Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/tomorrow-io-vs-weatherapi-com.md)\n- [Visual Crossing Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com.md)\n- [The Weather Company Data APIs vs WeatherAPI.com](https://www.anchorterminal.com/compare/weather-company-vs-weatherapi-com.md)\n- [WeatherAPI.com vs Weatherbit API](https://www.anchorterminal.com/compare/weatherapi-com-vs-weatherbit.md)\n- [WeatherAPI.com vs Xweather Weather API](https://www.anchorterminal.com/compare/weatherapi-com-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 The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.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 WeatherAPI.com](https://www.anchorterminal.com/compare/stormglass-vs-weatherapi-com.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n- [Open-Meteo vs WeatherAPI.com](https://www.anchorterminal.com/compare/open-meteo-vs-weatherapi-com.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 WeatherAPI.com", "url": "" } ], "description": "WeatherAPI.com scores 64.6 (B) 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", "WeatherAPI.com B 64.6", "scores" ], "h1": "Meteosource Weather MCP vs WeatherAPI.com", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteosource-mcp-vs-weatherapi-com", "published": "2026-10-01", "section": "tools", "title": "Meteosource Weather MCP vs WeatherAPI.com for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com" }, "tokens": { "markdown": 4600, "slim": 2530 }, "version": 1 }