{ "data": { "a": { "slug": "meteoblue", "name": "meteoblue Weather API", "vendor": "meteoblue AG", "vendorUrl": "https://www.meteoblue.com", "kind": "http-api", "category": "weather", "summary": "Weather data APIs from meteoblue AG of Basel, Switzerland. The Forecast API returns point forecasts in packages by coordinates, with History, Warnings, Dataset, Image and Maps APIs beside it, over HTTPS with an API key.", "url": "https://www.anchorterminal.com/tools/meteoblue", "markdownUrl": "https://www.anchorterminal.com/tools/meteoblue.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteoblue.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteoblue.json", "dns": "meteoblue.grade.anchorterminal.com", "repo": "https://github.com/meteoblue/python-dataset-sdk", "license": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "transports": [ "http" ], "remoteUrl": "https://my.meteoblue.com", "packages": [ { "registry": "pypi", "name": "meteoblue-dataset-sdk" } ], "auth": "api-key", "authNotes": "Self-serve key from a meteoblue account, created in a browser and managed in the Weather API Manager. The key goes in the `apikey` query parameter on every request, and no header option is documented. An account can hold several keys, each with a daily credit limit, an IP allow list, a referrer allow list and an optional shared secret for HMAC-SHA256 signed URLs. Paid plans start with an enquiry.", "pricing": "freemium", "pricingNotes": "Free Weather API with 10 million credits for one year from a free account, covering nine forecast packages, so an agent's owner can start without a contract. Calls cost 4,000 to 96,000 credits by package. The Premium Weather API is shown at EUR 2,400 a year for 40,000 calls a month, with larger tiers by enquiry. Prepaid credit prices are shown only after login (https://business.meteoblue.com/pricing, checked 2026-10-08).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI specs or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 8, "npmWeekly": null, "pypiWeekly": 512, "asOf": "2026-10-08" }, "docsUrl": "https://docs.meteoblue.com/en/weather-apis/introduction/overview", "llmsTxt": "https://business.meteoblue.com/llms.txt", "openapi": "https://my.meteoblue.com/packages/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "openapi", "llms-txt", "python", "status-page", "europe" ], "lastRelease": "2026-08-22", "graded": true, "anchor": { "graded": true, "score": 60.1, "grade": "C", "agentReady": false, "rank": 667, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 37, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.", "bestFor": "Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.", "strengths": [ "OpenAPI 3.1 specs for the Forecast (54 paths), History, Dataset, Image, Warnings, Measurements, Accounting and Model-Run Archive APIs, each at `openapi.json` beside its ReDoc page", "The Forecast API spec lists credits per package, 4,000 for `basic-day` and `current`, 8,000 for `basic-1h`, and each response carries an `MB-Credits-Accounted` header", "Free Weather API with 10 million credits for one year from a self-serve account, with no purchase obligation stated", "Keys can be limited by daily credits, IP range and referrer, or tied to an HMAC-SHA256 signature with an expiry time", "Pingdom status page with 15 monitors and monthly history. Each outage recorded between 4 August and 8 October 2026 touched a single API" ], "weaknesses": [ "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on", "The free trial covers nine forecast packages at hourly or coarser steps. Current conditions, sea, history, warnings and the Dataset API need a paid plan", "No security.txt, disclosure policy, SOC 2 or ISO 27001 was found. The only certificate published is ISO 9001:2015", "The general terms date from 24 May 2018, give no API-specific clauses and let meteoblue change or revoke them at any time", "The History API monitor shows an outage of 1 hour 26 minutes on 1 September 2026, and the status page is served over plain http only", "One dated changelog entry since 4 August 2026, and the only official SDK hasn't released since January 2025" ], "agentNotes": [ "Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call", "Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read `MB-Credits-Accounted` on each response", "Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has", "Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute", "Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send `expire` and `sig` if URLs may be seen by others" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.1 } ], "editorialScores": { "ergonomics": 66, "maintenance": 37, "payments": 34, "reliability": 75, "schema": 77, "security": 51, "transparency": 35 }, "provenanceScore": 88, "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": { "install": "pip install meteoblue-dataset-sdk", "http": "curl \"https://my.meteoblue.com/packages/basic-1h?lat=47.5596\u0026lon=7.5886\u0026tz=utc\u0026apikey=YOUR_APIKEY\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/meteoblue" }, "area": "domain-data", "provenance": { "legalEntity": "meteoblue AG", "domain": "meteoblue.com", "domainRegistered": "2005-11-15", "endpointOnVendorDomain": true, "terms": "https://business.meteoblue.com/terms-conditions", "privacy": "https://business.meteoblue.com/privacy-policy", "statusPage": "http://status.meteoblue.com/", "changelog": "https://business.meteoblue.com/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms and conditions (last revised 24 May 2018) are meteoblue's general terms for all services, products and data, the API included. They name meteoblue AG, Basel, under Swiss law with Basel as forum. No separate API agreement is published, and commercial terms are agreed in writing.", "The privacy policy (last revised 15 May 2024) states that it applies to all meteoblue services however they are used, and names the website, apps and API. The same two texts are also served at content.meteoblue.com/en/about-us/legal/.", "The imprint gives meteoblue AG, Greifengasse 38, CH-4058 Basel, commercial register number CHE-113.182.626.", "The APIs answer at my.meteoblue.com, warnings-api.meteoblue.com and measurements-api.meteoblue.com, behind Cloudflare.", "/.well-known/security.txt returns 404 on www.meteoblue.com, my.meteoblue.com, business.meteoblue.com and docs.meteoblue.com, and 403 on content.meteoblue.com.", "status.meteoblue.com is a Pingdom public report with 15 monitors. It answers over http. Over https the certificate does not match the host name.", "The changelog is on the business site, 19 dated entries from 11 August 2025 to 22 August 2026, mostly data and model additions.", "RDAP for meteoblue.com gives a registration date of 2005-11-15." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteoblue.json", "live": { "slug": "meteoblue", "probe": { "target": "https://my.meteoblue.com", "method": "get", "lastAt": "2026-11-08T00:55:51.940762327Z", "lastOk": true, "lastStatus": 404, "lastMs": 129, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 69, "p95ms24h": 129, "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": 255 }, { "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "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": "http://status.meteoblue.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:31:38.100304466Z" }, "versions": [ { "registry": "github", "name": "meteoblue/python-dataset-sdk", "version": "1.3.5", "released": "2025-01-10", "seenAt": "2026-11-06T23:44:28.676887796Z" }, { "registry": "pypi", "name": "meteoblue-dataset-sdk", "version": "1.3.5", "released": "2025-01-10", "seenAt": "2026-11-06T23:44:28.378554607Z" } ], "githubStars": 8, "pypiWeekly": 534, "securityTxt": { "url": "https://meteoblue.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:35.679564864Z" }, "llmsTxt": { "url": "https://business.meteoblue.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:00.350937106Z" }, "domain": { "domain": "meteoblue.com", "registered": "2005-11-15", "source": "https://rdap.verisign.com/com/v1/domain/meteoblue.com", "checkedAt": "2026-11-01T14:26:11.549002071Z" }, "pages": [ { "url": "https://business.meteoblue.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:00:35.911459063Z", "changedAt": "2026-11-03T07:42:37.575804498Z", "fingerprint": "fdb048d7473b" }, { "url": "https://business.meteoblue.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:00:38.86643174Z", "changedAt": "2026-11-03T07:42:39.725104068Z", "fingerprint": "bdb9ee8d7667" }, { "url": "https://business.meteoblue.com/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:00:39.940060287Z", "changedAt": "2026-11-03T07:42:41.634312871Z", "fingerprint": "efcbaffeb4ab" }, { "url": "https://business.meteoblue.com/terms-conditions", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:00:41.963179988Z", "changedAt": "2026-11-03T07:42:43.752388969Z", "fingerprint": "82fabc113df4" } ], "github": { "repo": "meteoblue/python-dataset-sdk", "checkedAt": "2026-11-02T09:05:27.189418792Z", "stars": 8, "archived": false, "issuesEnabled": true, "pushedAt": "2025-02-19T07:30:19Z", "openIssues": 1, "openPRs": 1, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 8, "unanswered": 1, "medianDays": 2 } }, "updatedAt": "2026-11-08T00:55:51.940762327Z" } }, "answer": "meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance \u0026 community.", "b": { "slug": "meteosource-mcp", "name": "Meteosource Weather MCP", "vendor": "Meteosource", "vendorUrl": "https://www.meteosource.com", "kind": "mcp", "category": "weather", "summary": "Meteosource's hosted MCP server gives an agent seven tools for place search, forecasts, severe-weather alerts, air quality, 20 years of weather history, and solar and wind production estimates, with a Meteosource API key.", "url": "https://www.anchorterminal.com/tools/meteosource-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json", "dns": "meteosource-mcp.grade.anchorterminal.com", "repo": "https://github.com/Meteosource/meteosource-weather-mcp", "license": "Proprietary service. The repository's MIT licence covers its docs and manifest", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.meteosource.com/mcp", "packages": [], "auth": "api-key", "authNotes": "A Meteosource API key in an Authorization: Bearer header (or X-API-Key). No OAuth. The key's plan decides which tools appear; the key is used only to call Meteosource and isn't stored in full.", "pricing": "freemium", "pricingNotes": "Free plan with 400 calls a day and no card, asking for a mention and backlink; Startup $9 a month (10,000 calls a day); Standard $29 a month; Renewables plan for production tools (checked 2026-11-07).", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://mcp.meteosource.com", "registryName": "com.meteosource/weather", "capabilities": [ "weather.forecast", "weather.historical", "weather.alerts", "weather.air-quality", "energy.solar" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 1048, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 32 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.", "bestFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "strengths": [ "Seven compact tools with plan requirements in the descriptions", "Documented error messages with fixes", "Forecasts, alerts, air quality, 20 years of history and solar and wind production", "Free plan with 400 calls a day and no card", "Official registry entry" ], "weaknesses": [ "Plain API key, no OAuth", "No tool annotations", "Status page unreachable and no incident history", "Terms and privacy not found" ], "agentNotes": [ "Call search_places first to resolve a location", "Split history requests over 400 location-days into shorter ranges", "Production tools need the Renewables plan; check which tools the key exposes", "Send the key in a header, never in a URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 25 }, "provenanceScore": 38, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add meteosource --transport http https://mcp.meteosource.com/mcp --header \"Authorization: Bearer $METEOSOURCE_API_KEY\"", "config": { "mcpServers": { "meteosource": { "headers": { "Authorization": "Bearer YOUR_METEOSOURCE_API_KEY" }, "url": "https://mcp.meteosource.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.forecast", "tool": "https://letme.dev/meteosource-mcp" }, "area": "domain-data", "unitPrices": [ { "item": "Startup plan", "unit": "month", "usd": 9, "note": "10,000 calls a day" }, { "item": "Standard plan", "unit": "month", "usd": 29, "note": "20,000 calls a day" } ], "provenance": { "legalEntity": "Meteosource", "domain": "meteosource.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The repository licence names Meteosource (2026). Terms and privacy URLs weren't found at the usual paths." ], "score": 38 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.json", "live": { "slug": "meteosource-mcp", "probe": { "target": "https://mcp.meteosource.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T00:55:52.070466931Z", "lastOk": true, "lastStatus": 200, "lastMs": 108, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 151, "p95ms24h": 199, "samples24h": 63, "samples30d": 63, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-08T00:55:52.070466931Z" } }, "edges": [ { "by": 40, "category": "reliability", "leads": "meteoblue", "name": "Reliability", "reasons": { "a": "Graded as a hosted service. Status page at status.meteoblue.com, a Pingdom public report with 15 monitors, one-minute checks and monthly history, served over http only, per the 8 October check, not re-read on 2 November 2026 because the host didn't resolve from our network (20). In the 90-day window from 4 August, the monitors read on 8 October show the History API down for 1 hour 26 minutes on 1 September, the Forecast API for 2 minutes on 15 September, and the Warnings, Dataset, Image and Location Search monitors for 1 to 17 minutes. Each touched one API, so each is partial. 9 October to 2 November is unread because the host didn't resolve, so \"minor only\" can't be confirmed for the whole window. The line holds at the 8 October award, as mailtrap's and merge-accounting's were held when their status hosts stopped answering, until the history can be read (15). 500 calls a minute and daily credit limits per account and key are documented (15). 429 is in every spec, and the availability page advises a 30-second timeout, a 30-second wait and at most 10 retries. No Retry-After header is documented. Every call is a GET (12 of 15). Custom SLAs are listed for enterprise plans with no published figure or credits. The availability page publishes yearly availability, 99.95 per cent for 2025, as a record and not a commitment (3 of 10). The Forecast API is generally available as version 2.0.0 (10). 20 + 15 + 15 + 12 + 3 + 10 = 75.", "b": "status.meteosource.com wasn't reachable (0). No history (5). Daily call quotas per plan, and the README's plans-and-limits section (15). Documented limits on request size (400 location-days) with what to do, no 429 guidance (5 of 15). No SLA found (0). Version 0.1.2, not labelled beta (10). 0 + 5 + 15 + 5 + 0 + 10 = 35." }, "scores": { "a": 75, "b": 35 } }, { "by": 33, "category": "maintenance", "leads": "meteosource-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "The latest dated changelog entry is 22 August 2026 (ICON-CH1 and ICON-CH2 added), 72 days before this check (20 of 30). It is the only changelog entry in the 90-day window from 4 August, since the two 29 July entries have left it. The only official SDK has no release since 10 January 2025, no official MCP server is listed, and docs page stamps (overview 30 July, Model-Run Archive 2 October) aren't releases or changelog entries (0). A public changelog, a community forum and email support for self-serve users, none of which we tested (9 of 15). The only official SDK, `meteoblue-dataset-sdk` 1.3.5, was last released on 10 January 2025 and covers one API (4 of 15). Its repository has test and publish workflows and a last commit on 19 February 2025 (4 of 10). 20 + 0 + 9 + 4 + 4 = 37.", "b": "Repository commit and tag v0.1.2 on 26 October 2026 (30). Three tags in 90 days (20). Repository issues not read (0). Official registry entry com.meteosource/weather (15). Small repository with server.json; server source not public (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API." }, "scores": { "a": 37, "b": 70 } }, { "by": 30, "category": "transparency", "leads": "meteoblue", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under general terms last revised on 24 May 2018. They grant a non-commercial licence for open and registered access and leave commercial terms to a written agreement, while the Free Weather API table marks commercial use as allowed. The Python SDK is MIT (12 of 30). The privacy policy, last revised 15 May 2024, covers the API by name. It gives no retention period beyond as long as necessary, and no DPA was found (12 of 30). No deprecation policy was found. The terms let meteoblue change or revoke them at any time, and the changelog records removals after the fact, such as two COSMO models on 11 August 2025 (4 of 20). The policy names Google and Microsoft Clarity for the website and lists other contractors by category. The docs name Datatrans for payments, and the API answers through Cloudflare. No subprocessor list or stated data location for API logs was found (7 of 20).", "b": "The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25." }, "scores": { "a": 62, "b": 32 } }, { "by": 9, "category": "ergonomics", "leads": "meteosource-mcp", "name": "Agent ergonomics", "reasons": { "a": "This is an API with no MCP server from the vendor. A caller sizes the response by choosing packages and a resolution and by setting `forecastDays` and `historyDays`. There is no field selection, and `basic-1h` returns 15 fields for each of 168 hours (16 of 25). The History API takes a time range, resolution and one of 14 aggregations, the Accounting API pages with `page` and `per`, and forecasts need no pagination (14 of 20). Errors are JSON with `error` and `error_message` under 400, 401, 403, 404 and 429, with no machine-readable code. (12 of 20). The 8 October call without a key went to a path my.meteoblue.com's robots.txt now closes, so that reading is struck. Every endpoint is a read-only GET, and retry guidance is published. Whether a failed call is charged credits is not stated (16 of 20). Only `lat`, `lon` and `apikey` are required, and elevation and time zone are detected. One official SDK, `meteoblue-dataset-sdk` for Python, covers the Dataset API only and dates from January 2025 (8 of 15).", "b": "Seven tools, about 20 KB (25). Date ranges and location limits on history (12 of 20). Documented error messages with fixes (15 of 20). No annotations on the tools (8 of 20, all reads). Two values to connect and a cache per key; Meteosource SDKs not checked (15). 25 + 12 + 15 + 8 + 15 = 75." }, "scores": { "a": 66, "b": 75 } }, { "by": 9, "category": "security", "leads": "meteoblue", "name": "Security \u0026 auth", "reasons": { "a": "An account can hold several named keys, each deletable, each with a daily credit limit, an optional IP allow list, a referrer and origin allow list, and an optional shared secret that makes every URL carry an HMAC-SHA256 signature and an expiry. There are no scopes. The key is accepted only as the `apikey` query parameter (25 less 10, 15 of 30). All data is read-only, and package access follows the plan (16 of 20). Warning text is relayed from national authorities and place names from GeoNames. The rest is numeric (10 of 15). `/account/usage` returns request counts and credits per day and type, the key manager charts each key, and each response carries `MB-Credits-Accounted`. No per-call log was found (8 of 15). security.txt returns 404 on four hosts, and no disclosure policy, bounty, SOC 2 or ISO 27001 was found. The ISO 9001:2015 certificate covers quality management (2 of 20).", "b": "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." }, "scores": { "a": 51, "b": 42 } }, { "by": 5, "category": "schema", "leads": "meteoblue", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 specs at `openapi.json` beside each ReDoc page, for the Forecast (54 paths), History, Accounting, Model-Run Archive, Dataset, Image, Warnings and Measurements APIs (25). business.meteoblue.com/llms.txt is a product index that links the docs. docs.meteoblue.com/llms.txt returns 404 and no Markdown docs were found (4 of 10). Package descriptions run long and say what each holds, which packages cannot be combined and when `raw` should not be set. They say less on choosing between similar packages (16 of 20). Coordinates carry minimum and maximum, units, formats, time formats and model domains are enums with defaults, and the History API marks five parameters required. The package path parameter is a comma-joined array (13 of 15). Samples in JavaScript, Python, shell and Java, and typed response fields with example values. Every error status shares one schema with a free-text `error_message` (10 of 15). Specs carry a version number, 2.0.0 for forecasts, with none in the path. The public changelog has 19 dated entries, mostly data additions (9 of 15).", "b": "Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72." }, "scores": { "a": 77, "b": 72 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "meteoblue AG", "b": "Meteosource", "name": "Vendor" }, { "a": "https://my.meteoblue.com", "b": "https://mcp.meteosource.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT", "b": "Proprietary service. The repository's MIT licence covers its docs and manifest", "name": "Licence" }, { "a": "none", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "com.meteosource/weather", "name": "MCP registry" }, { "a": "2026-08-22", "b": "none", "name": "Last release" }, { "a": "2018-05-24", "b": "no document linked", "name": "Terms last updated" }, { "a": "2024-05-15", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "8 stars, 512 PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, meteoblue Weather API or Meteosource Weather MCP?" }, { "answer": "Both need an API key.", "question": "Do meteoblue Weather API and Meteosource Weather MCP need an API key?" }, { "answer": "Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.", "question": "Can an agent call meteoblue Weather API and Meteosource Weather MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 35", "Schema \u0026 documentation, 77 against 72", "Security \u0026 auth, 51 against 42", "Transparency \u0026 trust, 62 against 32" ], "also": null, "goodFor": "Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.", "slug": "meteoblue", "watchFor": "The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on" }, { "aheadOn": [ "Agent ergonomics, 75 against 66", "Maintenance \u0026 community, 70 against 37" ], "also": null, "goodFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "slug": "meteosource-mcp", "watchFor": "Plain API key, no OAuth" } ], "history": { "meteoblue": [ { "causes": [ "time" ], "date": "2026-11-02", "delta": -1.7, "from": 61.8, "fromGrade": "C", "to": 60.1, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 61.7, "fromGrade": "C", "to": 61.8, "toGrade": "C" } ], "meteosource-mcp": null }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.json", "title": "AccuWeather Core Weather API + MCP vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.json", "title": "Google Weather API (Maps Platform) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.json", "title": "Met Office Weather DataHub (Site Specific) vs meteoblue Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.json", "title": "meteoblue Weather API vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.json", "title": "meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.json", "title": "meteoblue Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.json", "title": "meteoblue Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.json", "title": "meteoblue Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.json", "title": "meteoblue Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing" }, { "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/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/meteoblue-vs-weatherbit.json", "title": "meteoblue Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-xweather.json", "title": "meteoblue Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteoblue-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-stormglass.json", "title": "meteoblue Weather API vs Stormglass API", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-stormglass" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.json", "title": "Meteomatics Weather API vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.json", "title": "Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.json", "title": "Meteosource Weather MCP vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.json", "title": "Meteosource Weather MCP vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.json", "title": "Meteosource Weather MCP vs Stormglass API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.json", "title": "Meteosource Weather MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.json", "title": "Meteosource Weather MCP vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.json", "title": "Meteosource Weather MCP vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.json", "title": "Meteosource Weather MCP vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit.json", "title": "Meteosource Weather MCP vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather.json", "title": "Meteosource Weather MCP vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-open-meteo.json", "title": "meteoblue Weather API vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-open-meteo" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.json", "title": "Meteosource Weather MCP vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo" } ], "panel": null, "scores": [ { "by": 40, "edge": "meteoblue", "key": "reliability", "meteoblue": 75, "meteosource-mcp": 35, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "meteoblue", "key": "schema", "meteoblue": 77, "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 9, "edge": "meteosource-mcp", "key": "ergonomics", "meteoblue": 66, "meteosource-mcp": 75, "name": "Agent ergonomics", "weight": 13 }, { "by": 9, "edge": "meteoblue", "key": "security", "meteoblue": 51, "meteosource-mcp": 42, "name": "Security \u0026 auth", "weight": 14 }, { "by": 4, "edge": "meteoblue", "key": "payments", "meteoblue": 34, "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 33, "edge": "meteosource-mcp", "key": "maintenance", "meteoblue": 37, "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 30, "edge": "meteoblue", "key": "transparency", "meteoblue": 62, "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance \u0026 community. Both do weather forecasts.", "tasks": null, "tutorials": [], "verdicts": { "meteoblue": "Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.", "meteosource-mcp": "Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp", "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.min.md" }, "markdown": "meteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance \u0026 community. Both do weather forecasts.\n\n- meteoblue Weather API: grade C, 60.1/100, rank #667 of 1510. Markdown https://www.anchorterminal.com/tools/meteoblue.md · JSON https://www.anchorterminal.com/api/v1/tools/meteoblue.json\n- Meteosource Weather MCP: grade D, 50.9/100, rank #1048 of 1510. Markdown https://www.anchorterminal.com/tools/meteosource-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n- Best weather and climate data APIs for AI agents: https://www.anchorterminal.com/best/weather/index.md\n- All 136 weather comparisons: https://www.anchorterminal.com/compare/weather/index.md\n\n## Which one, for what\n\n### meteoblue Weather API (C)\n\nGood for: Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.\n\nAhead on:\n- Reliability, 75 against 35\n- Schema \u0026 documentation, 77 against 72\n- Security \u0026 auth, 51 against 42\n- Transparency \u0026 trust, 62 against 32\n\nWatch for: The key is accepted only as the `apikey` query parameter, so it appears in URLs and logs unless request signing is switched on\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 66\n- Maintenance \u0026 community, 70 against 37\n\nWatch for: Plain API key, no OAuth\n\n\n## Why the edge\n\n### Reliability: meteoblue Weather API +40\n\n- meteoblue Weather API (75): Graded as a hosted service. Status page at status.meteoblue.com, a Pingdom public report with 15 monitors, one-minute checks and monthly history, served over http only, per the 8 October check, not re-read on 2 November 2026 because the host didn't resolve from our network (20). In the 90-day window from 4 August, the monitors read on 8 October show the History API down for 1 hour 26 minutes on 1 September, the Forecast API for 2 minutes on 15 September, and the Warnings, Dataset, Image and Location Search monitors for 1 to 17 minutes. Each touched one API, so each is partial. 9 October to 2 November is unread because the host didn't resolve, so \"minor only\" can't be confirmed for the whole window. The line holds at the 8 October award, as mailtrap's and merge-accounting's were held when their status hosts stopped answering, until the history can be read (15). 500 calls a minute and daily credit limits per account and key are documented (15). 429 is in every spec, and the availability page advises a 30-second timeout, a 30-second wait and at most 10 retries. No Retry-After header is documented. Every call is a GET (12 of 15). Custom SLAs are listed for enterprise plans with no published figure or credits. The availability page publishes yearly availability, 99.95 per cent for 2025, as a record and not a commitment (3 of 10). The Forecast API is generally available as version 2.0.0 (10). 20 + 15 + 15 + 12 + 3 + 10 = 75.\n- Meteosource Weather MCP (35): status.meteosource.com wasn't reachable (0). No history (5). Daily call quotas per plan, and the README's plans-and-limits section (15). Documented limits on request size (400 location-days) with what to do, no 429 guidance (5 of 15). No SLA found (0). Version 0.1.2, not labelled beta (10). 0 + 5 + 15 + 5 + 0 + 10 = 35.\n\n### Maintenance \u0026 community: Meteosource Weather MCP +33\n\n- meteoblue Weather API (37): The latest dated changelog entry is 22 August 2026 (ICON-CH1 and ICON-CH2 added), 72 days before this check (20 of 30). It is the only changelog entry in the 90-day window from 4 August, since the two 29 July entries have left it. The only official SDK has no release since 10 January 2025, no official MCP server is listed, and docs page stamps (overview 30 July, Model-Run Archive 2 October) aren't releases or changelog entries (0). A public changelog, a community forum and email support for self-serve users, none of which we tested (9 of 15). The only official SDK, `meteoblue-dataset-sdk` 1.3.5, was last released on 10 January 2025 and covers one API (4 of 15). Its repository has test and publish workflows and a last commit on 19 February 2025 (4 of 10). 20 + 0 + 9 + 4 + 4 = 37.\n- Meteosource Weather MCP (70): Repository commit and tag v0.1.2 on 26 October 2026 (30). Three tags in 90 days (20). Repository issues not read (0). Official registry entry com.meteosource/weather (15). Small repository with server.json; server source not public (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.\n\n### Transparency \u0026 trust: meteoblue Weather API +30\n\n- meteoblue Weather API (62): Closed service under general terms last revised on 24 May 2018. They grant a non-commercial licence for open and registered access and leave commercial terms to a written agreement, while the Free Weather API table marks commercial use as allowed. The Python SDK is MIT (12 of 30). The privacy policy, last revised 15 May 2024, covers the API by name. It gives no retention period beyond as long as necessary, and no DPA was found (12 of 30). No deprecation policy was found. The terms let meteoblue change or revoke them at any time, and the changelog records removals after the fact, such as two COSMO models on 11 August 2025 (4 of 20). The policy names Google and Microsoft Clarity for the website and lists other contractors by category. The docs name Datatrans for payments, and the API answers through Cloudflare. No subprocessor list or stated data location for API logs was found (7 of 20).\n- Meteosource Weather MCP (32): The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25.\n\n### Agent ergonomics: Meteosource Weather MCP +9\n\n- meteoblue Weather API (66): This is an API with no MCP server from the vendor. A caller sizes the response by choosing packages and a resolution and by setting `forecastDays` and `historyDays`. There is no field selection, and `basic-1h` returns 15 fields for each of 168 hours (16 of 25). The History API takes a time range, resolution and one of 14 aggregations, the Accounting API pages with `page` and `per`, and forecasts need no pagination (14 of 20). Errors are JSON with `error` and `error_message` under 400, 401, 403, 404 and 429, with no machine-readable code. (12 of 20). The 8 October call without a key went to a path my.meteoblue.com's robots.txt now closes, so that reading is struck. Every endpoint is a read-only GET, and retry guidance is published. Whether a failed call is charged credits is not stated (16 of 20). Only `lat`, `lon` and `apikey` are required, and elevation and time zone are detected. One official SDK, `meteoblue-dataset-sdk` for Python, covers the Dataset API only and dates from January 2025 (8 of 15).\n- Meteosource Weather MCP (75): Seven tools, about 20 KB (25). Date ranges and location limits on history (12 of 20). Documented error messages with fixes (15 of 20). No annotations on the tools (8 of 20, all reads). Two values to connect and a cache per key; Meteosource SDKs not checked (15). 25 + 12 + 15 + 8 + 15 = 75.\n\n### Security \u0026 auth: meteoblue Weather API +9\n\n- meteoblue Weather API (51): An account can hold several named keys, each deletable, each with a daily credit limit, an optional IP allow list, a referrer and origin allow list, and an optional shared secret that makes every URL carry an HMAC-SHA256 signature and an expiry. There are no scopes. The key is accepted only as the `apikey` query parameter (25 less 10, 15 of 30). All data is read-only, and package access follows the plan (16 of 20). Warning text is relayed from national authorities and place names from GeoNames. The rest is numeric (10 of 15). `/account/usage` returns request counts and credits per day and type, the key manager charts each key, and each response carries `MB-Credits-Accounted`. No per-call log was found (8 of 15). security.txt returns 404 on four hosts, and no disclosure policy, bounty, SOC 2 or ISO 27001 was found. The ISO 9001:2015 certificate covers quality management (2 of 20).\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\n### Schema \u0026 documentation: meteoblue Weather API +5\n\n- meteoblue Weather API (77): OpenAPI 3.1 specs at `openapi.json` beside each ReDoc page, for the Forecast (54 paths), History, Accounting, Model-Run Archive, Dataset, Image, Warnings and Measurements APIs (25). business.meteoblue.com/llms.txt is a product index that links the docs. docs.meteoblue.com/llms.txt returns 404 and no Markdown docs were found (4 of 10). Package descriptions run long and say what each holds, which packages cannot be combined and when `raw` should not be set. They say less on choosing between similar packages (16 of 20). Coordinates carry minimum and maximum, units, formats, time formats and model domains are enums with defaults, and the History API marks five parameters required. The package path parameter is a comma-joined array (13 of 15). Samples in JavaScript, Python, shell and Java, and typed response fields with example values. Every error status shares one schema with a free-text `error_message` (10 of 15). Specs carry a version number, 2.0.0 for forecasts, with none in the path. The public changelog has 19 dated entries, mostly data additions (9 of 15).\n- Meteosource Weather MCP (72): Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72.\n\n## Score by category\n\n| Category | Weight | meteoblue Weather API | Meteosource Weather MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 35 | meteoblue Weather API +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 72 | meteoblue Weather API +5 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 75 | Meteosource Weather MCP +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 42 | meteoblue Weather API +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 34 | 30 | meteoblue Weather API +4 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 37 | 70 | Meteosource Weather MCP +33 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 32 | meteoblue Weather API +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.1 · C** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | meteoblue Weather API | Meteosource Weather MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | meteoblue AG | Meteosource |\n| Hosted endpoint | `https://my.meteoblue.com` | `https://mcp.meteosource.com/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MIT | Proprietary service. The repository's MIT licence covers its docs and manifest |\n| Tools exposed | none | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | not listed | `com.meteosource/weather` |\n| Last release | 2026-08-22 | none |\n| Terms last updated | 2018-05-24 | no document linked |\n| Privacy policy last updated | 2024-05-15 | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 8 stars, 512 PyPI/wk | none |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### meteoblue Weather API\n\n- -1.7 on 2 November 2026: time\n- +0.1 on 27 October 2026: checklist\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**meteoblue Weather API.** Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.\n\n**Meteosource Weather MCP.** Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.\n\n## Before you call either\n\n### meteoblue Weather API\n\n1. Pass `lat`, `lon` and `apikey` to `https://my.meteoblue.com/packages/\u003cpackage\u003e`. Join packages with commas, such as `basic-1h,basic-day`, to get several in one call\n2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read `MB-Credits-Accounted` on each response\n3. Set `forecastDays` and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has\n4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute\n5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send `expire` and `sig` if URLs may be seen by others\n\n### Meteosource Weather MCP\n\n1. Call search_places first to resolve a location\n2. Split history requests over 400 location-days into shorter ranges\n3. Production tools need the Renewables plan; check which tools the key exposes\n4. Send the key in a header, never in a URL\n\n## Questions\n\n### Which is better for AI agents, meteoblue Weather API or Meteosource Weather MCP?\n\nmeteoblue Weather API scores 60.1 (C) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on agent ergonomics and maintenance \u0026 community.\n\n### Do meteoblue Weather API and Meteosource Weather MCP need an API key?\n\nBoth need an API key.\n\n### Can an agent call meteoblue Weather API and Meteosource Weather MCP without installing anything?\n\nYes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteoblue\", \"b\": \"meteosource-mcp\"}`. From a terminal: `anchor compare meteoblue meteosource-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteoblue.json and https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n\n## Other comparisons with meteoblue Weather API or Meteosource Weather MCP\n\n- [AccuWeather Core Weather API + MCP vs meteoblue Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteoblue.md)\n- [Google Weather API (Maps Platform) vs meteoblue Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteoblue.md)\n- [Met Office Weather DataHub (Site Specific) vs meteoblue Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteoblue.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)\n- [meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.md)\n- [meteoblue Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteoblue-vs-openweather-one-call.md)\n- [meteoblue Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteoblue-vs-pirate-weather.md)\n- [meteoblue Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-tomorrow-io.md)\n- [meteoblue Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.md)\n- [meteoblue Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteoblue-vs-weather-company.md)\n- [meteoblue Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteoblue-vs-weatherapi-com.md)\n- [meteoblue Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteoblue-vs-weatherbit.md)\n- [meteoblue Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteoblue-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 Stormglass API](https://www.anchorterminal.com/compare/meteoblue-vs-stormglass.md)\n- [Meteomatics Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.md)\n- [Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.md)\n- [Meteosource Weather MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.md)\n- [Meteosource Weather MCP vs Pirate Weather](https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.md)\n- [Meteosource Weather MCP vs Stormglass API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.md)\n- [Meteosource Weather MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.md)\n- [Meteosource Weather MCP vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.md)\n- [Meteosource Weather MCP vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weather-company.md)\n- [Meteosource Weather MCP vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherapi-com.md)\n- [Meteosource Weather MCP vs Weatherbit API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-weatherbit.md)\n- [Meteosource Weather MCP vs Xweather Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-xweather.md)\n- [meteoblue Weather API vs Open-Meteo](https://www.anchorterminal.com/compare/meteoblue-vs-open-meteo.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "meteoblue Weather API vs Meteosource Weather MCP", "url": "" } ], "description": "meteoblue Weather scores 60.1 (C) to Meteosource Weather MCP's 50.9 (D) for weather forecasts. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "meteoblue Weather API C 60.1", "Meteosource Weather MCP D 50.9", "scores" ], "h1": "meteoblue Weather API vs Meteosource Weather MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteoblue-vs-meteosource-mcp", "published": "2026-10-01", "section": "tools", "title": "meteoblue Weather vs Meteosource Weather MCP for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp" }, "tokens": { "markdown": 5150, "slim": 2980 }, "version": 1 }