{ "data": { "a": { "slug": "meteomatics", "name": "Meteomatics Weather API", "vendor": "Meteomatics AG", "vendorUrl": "https://www.meteomatics.com", "kind": "http-api", "category": "weather", "summary": "Meteomatics Weather API returns forecasts, current observations, history back to 1940 and climate scenarios for points, routes, grids and polygons. It is a REST API with a hosted MCP server in beta, sold by contract to businesses.", "url": "https://www.anchorterminal.com/tools/meteomatics", "markdownUrl": "https://www.anchorterminal.com/tools/meteomatics.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteomatics.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteomatics.json", "dns": "meteomatics.grade.anchorterminal.com", "repo": "https://github.com/meteomatics/python-connector-api", "license": "Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT", "transports": [ "http" ], "remoteUrl": "https://api.meteomatics.com", "packages": [ { "registry": "pypi", "name": "meteomatics" } ], "auth": "mixed", "authNotes": "Access is granted by sales. A person talks to Meteomatics, signs an offer and receives a username and password by email. REST calls send them as HTTP Basic, or exchange them at https://login.meteomatics.com/api/v1/token for a token that lasts 2 hours and is documented as an `access_token` query parameter. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE, refresh tokens and one scope, `weather:read`, and logs in with the same account.", "pricing": "paid", "pricingNotes": "No public price. The pricing page says prices are based on usage and package and leads to a sales form. No free tier, sandbox or self-serve trial is on the site, so an agent can't start without a contract. The general terms allow a trial through an individual offer, fees are non-refundable and may be adjusted yearly, and the term renews unless ended 3 months ahead (https://www.meteomatics.com/en/pricing/, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 56, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://www.meteomatics.com/en/api/getting-started/", "llmsTxt": "https://www.meteomatics.com/llms.txt", "openapi": "https://swagger-ui.meteomatics.com/meteomatics_swagger_definition.yaml", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "weather.marine" ], "tags": [ "hosted", "enterprise", "sales-led", "closed-source", "openapi", "llms-txt", "mcp", "oauth", "python", "sla", "iso27001" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 45.7, "grade": "E", "agentReady": false, "rank": 1192, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 52, "payments": 0, "reliability": 34, "schema": 41, "security": 54, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Meteomatics sells a REST weather API with a published SLA that compensates downtime, ISO 27001 certification and a hosted MCP server in beta. Access needs a sales contract, with no public price, free tier or self-serve signup. No status page was found, its docs link no OpenAPI file, and REST calls authenticate with a username and password.", "bestFor": "Companies in energy, aviation, insurance and logistics that need many models, long history, polygon and route queries and an SLA, and will buy by contract.", "strengths": [ "Published SLA dated 7 May 2025 with 99.5 and 99.9 per cent uptime guarantees on the two paid support levels, compensated in free months", "ISO 27001 and Cyber Essentials certification, and a named security address for vulnerability reports", "`llms.txt` and `llms-full.txt` index the site and every API docs page", "One URL pattern covers history from 1940, forecasts and climate scenarios, in JSON, CSV, XML, NetCDF or image formats, and trajectory queries went live on 4 November 2026", "Hosted MCP server at https://mcp.meteomatics.com/mcp with OAuth, PKCE and a single read scope" ], "weaknesses": [ "No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation", "No status page found. The site links none and status.meteomatics.com didn't connect", "REST calls use HTTP Basic with the account username and password, and the two-hour token may travel as an `access_token` query parameter", "No OpenAPI file is linked from the docs. The Swagger UI loads one by script and is marked documentation only", "No request rate is published. The query count is set by contract, and 429 carries no documented `Retry-After` or backoff guidance", "No API changelog or deprecation policy found, and the MCP server's tools aren't documented on its page" ], "agentNotes": [ "Ask the account owner for credentials first. There is no signup, and both the REST API and the MCP server need a Meteomatics account with API access", "Build REST URLs as validdatetime/parameters/location/format, for example `2026-10-08T00:00:00Z/t_2m:C/52.52,13.40/json`. Parameter names carry their unit after a colon", "Keep each query to 10 locations and 10 parameters unless the contract says otherwise, and use POST when a GET URL passes 2,000 characters", "Send a trajectory as a POST body of timed points, up to 10,000, to `trajectory-3d` or `trajectory-4d` when the location moves", "Send credentials or the token in the `Authorization` header. Avoid the documented `access_token` query parameter, which puts the token in URLs and logs", "Read `/user_stats_json` before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.7 } ], "editorialScores": { "ergonomics": 80, "maintenance": 52, "payments": 0, "reliability": 34, "schema": 41, "security": 54, "transparency": 50 }, "provenanceScore": 69, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install meteomatics", "http": "curl -u USERNAME:PASSWORD 'https://api.meteomatics.com/2026-10-08T00:00:00Z/t_2m:C/52.520551,13.461804/json'", "config": { "name": "meteomatics", "type": "url", "url": "https://mcp.meteomatics.com/mcp" } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/meteomatics" }, "area": "domain-data", "provenance": { "legalEntity": "Meteomatics AG", "domain": "meteomatics.com", "domainRegistered": "2011-09-21", "endpointOnVendorDomain": true, "terms": "https://www.meteomatics.com/en/gtc-meteomatics-ag/", "privacy": "https://www.meteomatics.com/en/privacy-policy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The imprint names Meteomatics AG, Unterstrasse 12, 9000 St. Gallen, Switzerland, company number CHE-375.414.829, with group companies in England, Norway, Germany and the United States.", "The terms are the General Terms and Conditions for Enterprise Customers of Meteomatics AG, dated August 2026. Separate versions exist for Meteomatics GmbH, Meteomatics Limited and Meteomatics Inc.", "The privacy notice (latest update 20 August 2026) covers the group, names the Weather API and names Meteomatics AG as controller. A Data Processing Agreement is published beside it.", "The REST API answers at api.meteomatics.com, tokens at login.meteomatics.com and the MCP server at mcp.meteomatics.com.", "No status page was found. meteomatics.statuspage.io redirected to an inactive notice on 8 October, and status.meteomatics.com didn't connect for us on 8 October or 4 November.", "No API changelog was found. Product updates are posted as news articles at www.meteomatics.com/en/news/.", "www.meteomatics.com, mcp.meteomatics.com and login.meteomatics.com return 404 for /.well-known/security.txt. The information security page gives a contact address for vulnerability reports.", "The registration date was read from RDAP on 8 October, a data API this run doesn't use; not re-read." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteomatics.json", "live": { "slug": "meteomatics", "probe": { "target": "https://api.meteomatics.com", "method": "get", "lastAt": "2026-11-08T00:55:51.948913094Z", "lastOk": true, "lastStatus": 200, "lastMs": 237, "authRequired": false, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 248, "p95ms24h": 399, "samples24h": 244, "samples30d": 7486, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 253 }, { "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 } ] }, "versions": [ { "registry": "github", "name": "meteomatics/python-connector-api", "version": "v3.0.0", "released": "2025-11-06", "seenAt": "2026-11-06T23:44:32.439793694Z" }, { "registry": "pypi", "name": "meteomatics", "version": "4.0.0", "released": "2026-04-29", "seenAt": "2026-11-06T23:44:32.246932378Z" } ], "githubStars": 56, "pypiWeekly": 16554, "securityTxt": { "url": "https://meteomatics.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:45.333750067Z" }, "llmsTxt": { "url": "https://www.meteomatics.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:00.41811719Z" }, "domain": { "domain": "meteomatics.com", "registered": "2011-09-21", "source": "https://rdap.verisign.com/com/v1/domain/meteomatics.com", "checkedAt": "2026-11-01T14:15:25.548201161Z" }, "pages": [ { "url": "https://www.meteomatics.com/en/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:31:35.850749529Z", "changedAt": "2026-10-14T21:14:53.893308145Z", "fingerprint": "210f52744a64" }, { "url": "https://www.meteomatics.com/en/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:37.000839071Z", "changedAt": "2026-10-14T21:14:55.823213235Z", "fingerprint": "1f7ce1052a2a" }, { "url": "https://www.meteomatics.com/en/gtc-meteomatics-ag/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:32.748242574Z", "changedAt": "2026-10-14T21:14:51.657671498Z", "fingerprint": "670aac159502" } ], "github": { "repo": "meteomatics/python-connector-api", "checkedAt": "2026-11-02T09:05:33.08357588Z", "stars": 56, "archived": false, "issuesEnabled": true, "pushedAt": "2026-06-15T13:48:38Z", "openIssues": 1, "openPRs": 2, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 25, "unanswered": 1, "medianDays": 245 } }, "updatedAt": "2026-11-08T00:55:51.948913094Z" } }, "answer": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth and transparency \u0026 trust.", "b": { "slug": "meteosource-mcp", "name": "Meteosource Weather MCP", "vendor": "Meteosource", "vendorUrl": "https://www.meteosource.com", "kind": "mcp", "category": "weather", "summary": "Meteosource's hosted MCP server gives an agent seven tools for place search, forecasts, severe-weather alerts, air quality, 20 years of weather history, and solar and wind production estimates, with a Meteosource API key.", "url": "https://www.anchorterminal.com/tools/meteosource-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json", "dns": "meteosource-mcp.grade.anchorterminal.com", "repo": "https://github.com/Meteosource/meteosource-weather-mcp", "license": "Proprietary service. The repository's MIT licence covers its docs and manifest", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.meteosource.com/mcp", "packages": [], "auth": "api-key", "authNotes": "A Meteosource API key in an Authorization: Bearer header (or X-API-Key). No OAuth. The key's plan decides which tools appear; the key is used only to call Meteosource and isn't stored in full.", "pricing": "freemium", "pricingNotes": "Free plan with 400 calls a day and no card, asking for a mention and backlink; Startup $9 a month (10,000 calls a day); Standard $29 a month; Renewables plan for production tools (checked 2026-11-07).", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://mcp.meteosource.com", "registryName": "com.meteosource/weather", "capabilities": [ "weather.forecast", "weather.historical", "weather.alerts", "weather.air-quality", "energy.solar" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 1048, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 32 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.", "bestFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "strengths": [ "Seven compact tools with plan requirements in the descriptions", "Documented error messages with fixes", "Forecasts, alerts, air quality, 20 years of history and solar and wind production", "Free plan with 400 calls a day and no card", "Official registry entry" ], "weaknesses": [ "Plain API key, no OAuth", "No tool annotations", "Status page unreachable and no incident history", "Terms and privacy not found" ], "agentNotes": [ "Call search_places first to resolve a location", "Split history requests over 400 location-days into shorter ranges", "Production tools need the Renewables plan; check which tools the key exposes", "Send the key in a header, never in a URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 25 }, "provenanceScore": 38, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add meteosource --transport http https://mcp.meteosource.com/mcp --header \"Authorization: Bearer $METEOSOURCE_API_KEY\"", "config": { "mcpServers": { "meteosource": { "headers": { "Authorization": "Bearer YOUR_METEOSOURCE_API_KEY" }, "url": "https://mcp.meteosource.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.forecast", "tool": "https://letme.dev/meteosource-mcp" }, "area": "domain-data", "unitPrices": [ { "item": "Startup plan", "unit": "month", "usd": 9, "note": "10,000 calls a day" }, { "item": "Standard plan", "unit": "month", "usd": 29, "note": "20,000 calls a day" } ], "provenance": { "legalEntity": "Meteosource", "domain": "meteosource.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The repository licence names Meteosource (2026). Terms and privacy URLs weren't found at the usual paths." ], "score": 38 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.json", "live": { "slug": "meteosource-mcp", "probe": { "target": "https://mcp.meteosource.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T00:55:52.070466931Z", "lastOk": true, "lastStatus": 200, "lastMs": 108, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 151, "p95ms24h": 199, "samples24h": 63, "samples30d": 63, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-08T00:55:52.070466931Z" } }, "edges": [ { "by": 31, "category": "schema", "leads": "meteosource-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "No machine-readable contract counts. The Swagger page links only the Swagger UI, which loads its YAML file by script, and neither llms.txt nor any docs page read links the file, so this run doesn't count it; the MCP tool schemas were read on 8 October only by calling the server, a reading this run strikes (0 of 25). `llms.txt` and `llms-full.txt` at www.meteomatics.com index the site and the API docs (10). The docs explain each URL segment, option and request type, such as trajectory queries, with no guidance on when not to use them (12 of 20). The core request is a URL grammar of free strings; parameter names carry their unit and the docs give allowed values in prose tables, with no typed schema (4 of 15). Example URLs and responses on every docs page and a table of 17 HTTP codes, with errors returned as plain text (10 of 15). No API version in the path and no API changelog. Product update posts appear every two to three months (5 of 15). 0 + 10 + 12 + 4 + 10 + 5 = 41.", "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": 41, "b": 72 } }, { "by": 30, "category": "payments", "leads": "meteosource-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 in the docs or the OpenAPI file. The error table lists 402, with no payment protocol behind it (0). The pricing page says prices are based on usage and gives no figure, only a form to talk to sales (0). No free tier or trial is on the site. The general terms let Meteomatics grant a trial through an individual offer (0). A person talks to sales and receives a username and password by email. The MCP server registers OAuth clients by API but still needs that account (0). The pricing page re-read on 4 November still says 'Talk to our experts to learn more about our pricing'. 0 + 0 + 0 + 0 = 0.", "b": "No machine payment protocol (0). Plan prices with daily call quotas, public (10). Free plan with 400 calls a day, no card (20). A person signs up in a browser for the key (0). 0 + 10 + 20 + 0 = 30." }, "scores": { "a": 0, "b": 30 } }, { "by": 28, "category": "transparency", "leads": "meteomatics", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under general terms for enterprise customers dated August 2026, published per group company, with Swiss law and the courts at the vendor's seat. The Python connector is MIT (15 of 30). The privacy notice, last updated 20 August 2026, names the Weather API, says technical data and usage logs are kept for 3 months, and names Meteomatics AG as controller. A published Data Processing Agreement covers breach notice, deletion or return at the end of the contract and 30 days' notice of a new sub-processor (22 of 30). No deprecation policy was found. The terms let the vendor change them by posting a new version, and a commit marked as breaking on the Python connector, dated 29 April 2026, deprecates the `ecmwf-ens-cluster` source with no notice period stated (3 of 20). The privacy notice names nine services with their countries, among them HubSpot, Stripe, Gong and OpenAI. No hosting provider or data location for the API is named (10 of 20). The general terms (August 2026) and privacy notice (latest update 20 August 2026) were re-read on 4 November. 15 + 22 + 3 + 10 = 50.", "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": 60, "b": 32 } }, { "by": 18, "category": "maintenance", "leads": "meteosource-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest dated API change is the product update of 4 November 2026, which puts trajectory queries live (`trajectory-3d` and `trajectory-4d` POST requests with up to 10,000 points), 0 days before this check (30). Two dated entries in the 90 days from 6 August, 24 August and 4 November 2026, and no connector commits in that window, so not three (0). Product update posts on 15 June, 24 August and 4 November 2026, support by email around the clock per the SLA, and a pull request merged on the Python connector on 15 June 2026 (9 of 15). The Python connector's version file reads 4.0.0 from 29 April 2026 with Python 3.9 or later, and the R, Kotlin and Julia connectors were updated in May 2026 (10 of 15). The connector repository has no CI workflow, tests or changelog file (3 of 10). 30 + 0 + 9 + 10 + 3 = 52.", "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": 52, "b": 70 } }, { "by": 12, "category": "security", "leads": "meteomatics", "name": "Security \u0026 auth", "reasons": { "a": "REST calls use HTTP Basic with a username and password sent by email, or a token from login.meteomatics.com that lasts 2 hours and is documented as an `access_token` query parameter. No key rotation or separate keys were found in the docs. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE (S256), refresh tokens and one scope, `weather:read` (12 of 30, after the 10-point deduction for a secret in the URL). The whole API is read-only and the single OAuth scope is a read scope (15 of 20). Responses are mostly numbers. Aviation bulletins and official alerts carry third-party text, and the MCP guide tells users to check model output, with no guidance on untrusted content (9 of 15). `/user_stats` and `/user_stats_json` report query counts against contract limits, and the privacy notice says usage logs are kept for 3 months. No per-call log for the customer was found (5 of 15). ISO 27001 and Cyber Essentials certification on the information security page (re-read 4 November), with a security address for vulnerability reports and a promise to 'respond promptly'. No security.txt (404 on 8 October) and no bug bounty (13 of 20). 12 + 15 + 9 + 5 + 13 = 54.", "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": 54, "b": 42 } }, { "by": 5, "category": "ergonomics", "leads": "meteomatics", "name": "Agent ergonomics", "reasons": { "a": "The parameter list, time range, step and format in the URL size each response (23 of 25). No pagination. Output is bounded by the time range and interval, 10 locations and 10 parameters a query, a `timeout` option and a choice of JSON, CSV, XML, NetCDF or images (13 of 20). HTTP codes with a plain-text message that says which part of the URL is wrong or what data is available, 206 for partial content, and no machine-readable error key (12 of 20). Every REST call is a read, including the POST forms, so retries are safe; the MCP tool annotations read on 8 October came from a struck request to the server and aren't relied on (20). The default source is the vendor's mix model. A call needs four URL segments and parameter names with units. The Python connector is at 4.0.0 in its repository, and connectors for R, Go, Java, C++, Kotlin and Julia are on GitHub (12 of 15). 23 + 13 + 12 + 20 + 12 = 80.", "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": 80, "b": 75 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Meteomatics AG", "b": "Meteosource", "name": "Vendor" }, { "a": "https://api.meteomatics.com", "b": "https://mcp.meteosource.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT", "b": "Proprietary service. The repository's MIT licence covers its docs and manifest", "name": "Licence" }, { "a": "9", "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-11-04", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "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": "56 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, Meteomatics Weather API or Meteosource Weather MCP?" }, { "answer": "Meteomatics Weather API takes an API key or an OAuth sign-in. Meteosource Weather MCP needs an API key.", "question": "Do Meteomatics Weather API and Meteosource Weather MCP need an API key?" }, { "answer": "Yes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.com and Meteosource Weather MCP at https://mcp.meteosource.com/mcp.", "question": "Can an agent call Meteomatics Weather API and Meteosource Weather MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 80 against 75", "Security \u0026 auth, 54 against 42", "Transparency \u0026 trust, 60 against 32" ], "also": null, "goodFor": "Companies in energy, aviation, insurance and logistics that need many models, long history, polygon and route queries and an SLA, and will buy by contract.", "slug": "meteomatics", "watchFor": "No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation" }, { "aheadOn": [ "Schema \u0026 documentation, 72 against 41", "Payments \u0026 pricing, 30 against 0", "Maintenance \u0026 community, 70 against 52" ], "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": { "meteomatics": [ { "causes": [ "product", "correction" ], "date": "2026-11-04", "delta": -4, "from": 49.7, "fromGrade": "D", "to": 45.7, "toGrade": "E" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 49.8, "fromGrade": "D", "to": 49.7, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 49.6, "fromGrade": "D", "to": 49.8, "toGrade": "D" } ], "meteosource-mcp": null }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.json", "title": "AccuWeather Core Weather API + MCP vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.json", "title": "Google Weather API (Maps Platform) vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.json", "title": "Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics" }, { "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/meteomatics-vs-nws-api.json", "title": "Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.json", "title": "Meteomatics Weather API vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.json", "title": "Meteomatics Weather API vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.json", "title": "Meteomatics Weather API vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.json", "title": "Meteomatics Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.json", "title": "Meteomatics Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/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/meteomatics-vs-weatherbit.json", "title": "Meteomatics Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-xweather.json", "title": "Meteomatics Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/meteomatics-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-stormglass.json", "title": "Meteomatics Weather API vs Stormglass API", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-stormglass" }, { "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/meteomatics-vs-open-meteo.json", "title": "Meteomatics Weather API vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/meteomatics-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": 1, "edge": "meteosource-mcp", "key": "reliability", "meteomatics": 34, "meteosource-mcp": 35, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 31, "edge": "meteosource-mcp", "key": "schema", "meteomatics": 41, "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 5, "edge": "meteomatics", "key": "ergonomics", "meteomatics": 80, "meteosource-mcp": 75, "name": "Agent ergonomics", "weight": 13 }, { "by": 12, "edge": "meteomatics", "key": "security", "meteomatics": 54, "meteosource-mcp": 42, "name": "Security \u0026 auth", "weight": 14 }, { "by": 30, "edge": "meteosource-mcp", "key": "payments", "meteomatics": 0, "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 18, "edge": "meteosource-mcp", "key": "maintenance", "meteomatics": 52, "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 28, "edge": "meteomatics", "key": "transparency", "meteomatics": 60, "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do weather forecasts.", "tasks": null, "tutorials": [], "verdicts": { "meteomatics": "Meteomatics sells a REST weather API with a published SLA that compensates downtime, ISO 27001 certification and a hosted MCP server in beta. Access needs a sales contract, with no public price, free tier or self-serve signup. No status page was found, its docs link no OpenAPI file, and REST calls authenticate with a username and password.", "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/meteomatics-vs-meteosource-mcp", "json": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.min.md" }, "markdown": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do weather forecasts.\n\n- Meteomatics Weather API: grade E, 45.7/100, rank #1192 of 1510. Markdown https://www.anchorterminal.com/tools/meteomatics.md · JSON https://www.anchorterminal.com/api/v1/tools/meteomatics.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### Meteomatics Weather API (E)\n\nGood for: Companies in energy, aviation, insurance and logistics that need many models, long history, polygon and route queries and an SLA, and will buy by contract.\n\nAhead on:\n- Agent ergonomics, 80 against 75\n- Security \u0026 auth, 54 against 42\n- Transparency \u0026 trust, 60 against 32\n\nWatch for: No public price, free tier or self-serve signup found. Credentials arrive by email after a sales conversation\n\n### Meteosource Weather MCP (D)\n\nGood for: Agents that answer weather questions, plan around severe weather or estimate solar and wind output.\n\nAhead on:\n- Schema \u0026 documentation, 72 against 41\n- Payments \u0026 pricing, 30 against 0\n- Maintenance \u0026 community, 70 against 52\n\nWatch for: Plain API key, no OAuth\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Meteosource Weather MCP +31\n\n- Meteomatics Weather API (41): No machine-readable contract counts. The Swagger page links only the Swagger UI, which loads its YAML file by script, and neither llms.txt nor any docs page read links the file, so this run doesn't count it; the MCP tool schemas were read on 8 October only by calling the server, a reading this run strikes (0 of 25). `llms.txt` and `llms-full.txt` at www.meteomatics.com index the site and the API docs (10). The docs explain each URL segment, option and request type, such as trajectory queries, with no guidance on when not to use them (12 of 20). The core request is a URL grammar of free strings; parameter names carry their unit and the docs give allowed values in prose tables, with no typed schema (4 of 15). Example URLs and responses on every docs page and a table of 17 HTTP codes, with errors returned as plain text (10 of 15). No API version in the path and no API changelog. Product update posts appear every two to three months (5 of 15). 0 + 10 + 12 + 4 + 10 + 5 = 41.\n- Meteosource Weather MCP (72): Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72.\n\n### Payments \u0026 pricing: Meteosource Weather MCP +30\n\n- Meteomatics Weather API (0): No x402, MPP or L402 in the docs or the OpenAPI file. The error table lists 402, with no payment protocol behind it (0). The pricing page says prices are based on usage and gives no figure, only a form to talk to sales (0). No free tier or trial is on the site. The general terms let Meteomatics grant a trial through an individual offer (0). A person talks to sales and receives a username and password by email. The MCP server registers OAuth clients by API but still needs that account (0). The pricing page re-read on 4 November still says 'Talk to our experts to learn more about our pricing'. 0 + 0 + 0 + 0 = 0.\n- Meteosource Weather MCP (30): No machine payment protocol (0). Plan prices with daily call quotas, public (10). Free plan with 400 calls a day, no card (20). A person signs up in a browser for the key (0). 0 + 10 + 20 + 0 = 30.\n\n### Transparency \u0026 trust: Meteomatics Weather API +28\n\n- Meteomatics Weather API (60): Closed service under general terms for enterprise customers dated August 2026, published per group company, with Swiss law and the courts at the vendor's seat. The Python connector is MIT (15 of 30). The privacy notice, last updated 20 August 2026, names the Weather API, says technical data and usage logs are kept for 3 months, and names Meteomatics AG as controller. A published Data Processing Agreement covers breach notice, deletion or return at the end of the contract and 30 days' notice of a new sub-processor (22 of 30). No deprecation policy was found. The terms let the vendor change them by posting a new version, and a commit marked as breaking on the Python connector, dated 29 April 2026, deprecates the `ecmwf-ens-cluster` source with no notice period stated (3 of 20). The privacy notice names nine services with their countries, among them HubSpot, Stripe, Gong and OpenAI. No hosting provider or data location for the API is named (10 of 20). The general terms (August 2026) and privacy notice (latest update 20 August 2026) were re-read on 4 November. 15 + 22 + 3 + 10 = 50.\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### Maintenance \u0026 community: Meteosource Weather MCP +18\n\n- Meteomatics Weather API (52): The newest dated API change is the product update of 4 November 2026, which puts trajectory queries live (`trajectory-3d` and `trajectory-4d` POST requests with up to 10,000 points), 0 days before this check (30). Two dated entries in the 90 days from 6 August, 24 August and 4 November 2026, and no connector commits in that window, so not three (0). Product update posts on 15 June, 24 August and 4 November 2026, support by email around the clock per the SLA, and a pull request merged on the Python connector on 15 June 2026 (9 of 15). The Python connector's version file reads 4.0.0 from 29 April 2026 with Python 3.9 or later, and the R, Kotlin and Julia connectors were updated in May 2026 (10 of 15). The connector repository has no CI workflow, tests or changelog file (3 of 10). 30 + 0 + 9 + 10 + 3 = 52.\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### Security \u0026 auth: Meteomatics Weather API +12\n\n- Meteomatics Weather API (54): REST calls use HTTP Basic with a username and password sent by email, or a token from login.meteomatics.com that lasts 2 hours and is documented as an `access_token` query parameter. No key rotation or separate keys were found in the docs. The MCP server uses OAuth with dynamic client registration, the authorisation code grant with PKCE (S256), refresh tokens and one scope, `weather:read` (12 of 30, after the 10-point deduction for a secret in the URL). The whole API is read-only and the single OAuth scope is a read scope (15 of 20). Responses are mostly numbers. Aviation bulletins and official alerts carry third-party text, and the MCP guide tells users to check model output, with no guidance on untrusted content (9 of 15). `/user_stats` and `/user_stats_json` report query counts against contract limits, and the privacy notice says usage logs are kept for 3 months. No per-call log for the customer was found (5 of 15). ISO 27001 and Cyber Essentials certification on the information security page (re-read 4 November), with a security address for vulnerability reports and a promise to 'respond promptly'. No security.txt (404 on 8 October) and no bug bounty (13 of 20). 12 + 15 + 9 + 5 + 13 = 54.\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### Agent ergonomics: Meteomatics Weather API +5\n\n- Meteomatics Weather API (80): The parameter list, time range, step and format in the URL size each response (23 of 25). No pagination. Output is bounded by the time range and interval, 10 locations and 10 parameters a query, a `timeout` option and a choice of JSON, CSV, XML, NetCDF or images (13 of 20). HTTP codes with a plain-text message that says which part of the URL is wrong or what data is available, 206 for partial content, and no machine-readable error key (12 of 20). Every REST call is a read, including the POST forms, so retries are safe; the MCP tool annotations read on 8 October came from a struck request to the server and aren't relied on (20). The default source is the vendor's mix model. A call needs four URL segments and parameter names with units. The Python connector is at 4.0.0 in its repository, and connectors for R, Go, Java, C++, Kotlin and Julia are on GitHub (12 of 15). 23 + 13 + 12 + 20 + 12 = 80.\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## Score by category\n\n| Category | Weight | Meteomatics Weather API | Meteosource Weather MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 34 | 35 | Meteosource Weather MCP +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 41 | 72 | Meteosource Weather MCP +31 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 75 | Meteomatics Weather API +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 42 | Meteomatics Weather API +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 30 | Meteosource Weather MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 52 | 70 | Meteosource Weather MCP +18 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 32 | Meteomatics Weather API +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.7 · E** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | Meteomatics Weather API | Meteosource Weather MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Meteomatics AG | Meteosource |\n| Hosted endpoint | `https://api.meteomatics.com` | `https://mcp.meteosource.com/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Meteomatics' general terms and conditions. The Python connector on GitHub is MIT | Proprietary service. The repository's MIT licence covers its docs and manifest |\n| Tools exposed | 9 | 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-11-04 | none |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | 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 | 56 stars | none |\n\n## How the scores have moved\n\n### Meteomatics Weather API\n\n- -4.0 on 4 November 2026 (D to E): product, correction\n- -0.1 on 28 October 2026: correction\n- +0.2 on 27 October 2026: checklist\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Meteomatics Weather API.** Meteomatics sells a REST weather API with a published SLA that compensates downtime, ISO 27001 certification and a hosted MCP server in beta. Access needs a sales contract, with no public price, free tier or self-serve signup. No status page was found, its docs link no OpenAPI file, and REST calls authenticate with a username and password.\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### Meteomatics Weather API\n\n1. Ask the account owner for credentials first. There is no signup, and both the REST API and the MCP server need a Meteomatics account with API access\n2. Build REST URLs as validdatetime/parameters/location/format, for example `2026-10-08T00:00:00Z/t_2m:C/52.52,13.40/json`. Parameter names carry their unit after a colon\n3. Keep each query to 10 locations and 10 parameters unless the contract says otherwise, and use POST when a GET URL passes 2,000 characters\n4. Send a trajectory as a POST body of timed points, up to 10,000, to `trajectory-3d` or `trajectory-4d` when the location moves\n5. Send credentials or the token in the `Authorization` header. Avoid the documented `access_token` query parameter, which puts the token in URLs and logs\n6. Read `/user_stats_json` before a large job. It reports queries sent and the contract's limits, and 429 means a limit is spent\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, Meteomatics Weather API or Meteosource Weather MCP?\n\nMeteosource Weather MCP scores 50.9 (D) on agent readiness against Meteomatics Weather API's 45.7 (E), and leads in 4 of 7 scored categories. Meteomatics Weather API leads on agent ergonomics, security \u0026 auth and transparency \u0026 trust.\n\n### Do Meteomatics Weather API and Meteosource Weather MCP need an API key?\n\nMeteomatics Weather API takes an API key or an OAuth sign-in. Meteosource Weather MCP needs an API key.\n\n### Can an agent call Meteomatics Weather API and Meteosource Weather MCP without installing anything?\n\nYes. Meteomatics Weather API has a hosted endpoint at https://api.meteomatics.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/meteomatics-vs-meteosource-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteomatics\", \"b\": \"meteosource-mcp\"}`. From a terminal: `anchor compare meteomatics meteosource-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteomatics.json and https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n\n## Other comparisons with Meteomatics Weather API or Meteosource Weather MCP\n\n- [AccuWeather Core Weather API + MCP vs Meteomatics Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-meteomatics.md)\n- [Google Weather API (Maps Platform) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-meteomatics.md)\n- [Met Office Weather DataHub (Site Specific) vs Meteomatics Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteomatics.md)\n- [meteoblue Weather API vs Meteomatics Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-meteomatics.md)\n- [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md)\n- [Meteomatics Weather API vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteomatics-vs-openweather-one-call.md)\n- [Meteomatics Weather API vs Pirate Weather](https://www.anchorterminal.com/compare/meteomatics-vs-pirate-weather.md)\n- [Meteomatics Weather API vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-tomorrow-io.md)\n- [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md)\n- [Meteomatics Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/meteomatics-vs-weather-company.md)\n- [Meteomatics Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/meteomatics-vs-weatherapi-com.md)\n- [Meteomatics Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/meteomatics-vs-weatherbit.md)\n- [Meteomatics Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/meteomatics-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 Stormglass API](https://www.anchorterminal.com/compare/meteomatics-vs-stormglass.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- [Meteomatics Weather API vs Open-Meteo](https://www.anchorterminal.com/compare/meteomatics-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": "Meteomatics Weather API vs Meteosource Weather MCP", "url": "" } ], "description": "Meteosource Weather MCP scores 50.9 (D) to Meteomatics Weather's 45.7 (E) for weather forecasts. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Meteomatics Weather API E 45.7", "Meteosource Weather MCP D 50.9", "scores" ], "h1": "Meteomatics Weather API vs Meteosource Weather MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteomatics-vs-meteosource-mcp", "published": "2026-10-01", "section": "tools", "title": "Meteomatics Weather vs Meteosource Weather MCP for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp" }, "tokens": { "markdown": 5100, "slim": 2880 }, "version": 1 }