{ "data": { "a": { "slug": "meteosource-mcp", "name": "Meteosource Weather MCP", "vendor": "Meteosource", "vendorUrl": "https://www.meteosource.com", "kind": "mcp", "category": "weather", "summary": "Meteosource's hosted MCP server gives an agent seven tools for place search, forecasts, severe-weather alerts, air quality, 20 years of weather history, and solar and wind production estimates, with a Meteosource API key.", "url": "https://www.anchorterminal.com/tools/meteosource-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json", "dns": "meteosource-mcp.grade.anchorterminal.com", "repo": "https://github.com/Meteosource/meteosource-weather-mcp", "license": "Proprietary service. The repository's MIT licence covers its docs and manifest", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.meteosource.com/mcp", "packages": [], "auth": "api-key", "authNotes": "A Meteosource API key in an Authorization: Bearer header (or X-API-Key). No OAuth. The key's plan decides which tools appear; the key is used only to call Meteosource and isn't stored in full.", "pricing": "freemium", "pricingNotes": "Free plan with 400 calls a day and no card, asking for a mention and backlink; Startup $9 a month (10,000 calls a day); Standard $29 a month; Renewables plan for production tools (checked 2026-11-07).", "priceSummary": "$9 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://mcp.meteosource.com", "registryName": "com.meteosource/weather", "capabilities": [ "weather.forecast", "weather.historical", "weather.alerts", "weather.air-quality", "energy.solar" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "api-key", "freemium", "free-tier", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 1048, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 32 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.", "bestFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "strengths": [ "Seven compact tools with plan requirements in the descriptions", "Documented error messages with fixes", "Forecasts, alerts, air quality, 20 years of history and solar and wind production", "Free plan with 400 calls a day and no card", "Official registry entry" ], "weaknesses": [ "Plain API key, no OAuth", "No tool annotations", "Status page unreachable and no incident history", "Terms and privacy not found" ], "agentNotes": [ "Call search_places first to resolve a location", "Split history requests over 400 location-days into shorter ranges", "Production tools need the Renewables plan; check which tools the key exposes", "Send the key in a header, never in a URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 70, "payments": 30, "reliability": 35, "schema": 72, "security": 42, "transparency": 25 }, "provenanceScore": 38, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add meteosource --transport http https://mcp.meteosource.com/mcp --header \"Authorization: Bearer $METEOSOURCE_API_KEY\"", "config": { "mcpServers": { "meteosource": { "headers": { "Authorization": "Bearer YOUR_METEOSOURCE_API_KEY" }, "url": "https://mcp.meteosource.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.forecast", "tool": "https://letme.dev/meteosource-mcp" }, "area": "domain-data", "unitPrices": [ { "item": "Startup plan", "unit": "month", "usd": 9, "note": "10,000 calls a day" }, { "item": "Standard plan", "unit": "month", "usd": 29, "note": "20,000 calls a day" } ], "provenance": { "legalEntity": "Meteosource", "domain": "meteosource.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The repository licence names Meteosource (2026). Terms and privacy URLs weren't found at the usual paths." ], "score": 38 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/meteosource-mcp.json", "live": { "slug": "meteosource-mcp", "probe": { "target": "https://mcp.meteosource.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T00:55:52.070466931Z", "lastOk": true, "lastStatus": 200, "lastMs": 108, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 151, "p95ms24h": 199, "samples24h": 63, "samples30d": 63, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "updatedAt": "2026-11-08T00:55:52.070466931Z" } }, "answer": "Visual Crossing Weather API scores 62.2 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on maintenance \u0026 community.", "b": { "slug": "visual-crossing", "name": "Visual Crossing Weather API", "vendor": "Visual Crossing", "vendorUrl": "https://www.visualcrossing.com", "kind": "http-api", "category": "weather", "summary": "Weather API for historical conditions, forecasts and climate data by location and date range.", "url": "https://www.anchorterminal.com/tools/visual-crossing", "markdownUrl": "https://www.anchorterminal.com/tools/visual-crossing.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/visual-crossing.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/visual-crossing.json", "dns": "visual-crossing.grade.anchorterminal.com", "repo": "https://github.com/visualcrossing/WeatherApi", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline", "packages": [], "auth": "api-key", "authNotes": "Supported Timeline and Maps requests need no key since 28 October 2026, with usage managed by client IP address. With a key, the Timeline API takes it as the key query parameter. The MCP server takes it in an X-VC-API-Key header, or OAuth (user or machine-to-machine) once Visual Crossing has provisioned it for the account.", "pricing": "freemium", "pricingNotes": "Billed in records. A day of daily data is one record, a day of hourly data is 24, and a full 15-day forecast for one location is one record. Since 28 October 2026 supported Timeline and Maps requests work with no key or account, free for commercial use with attribution, under IP-based fair-use limits with no fixed allowance. Free with a key at 1,000 records a day (30,000 a month), no card, one concurrent request, attribution required. Metered at $0.0001 a record above the free 1,000 a day, up to 25,000 records a query. Professional (10 million records a month) shows no price, and Corporate and Enterprise are contact sales. A February 2023 post put Professional and Corporate at $35 and $150 a month. The plan table lists 99.5 per cent uptime on Free and 99.9 on paid plans (https://www.visualcrossing.com/weather-data-pricing/ and https://www.visualcrossing.com/resources/documentation/weather-api/free-weather-api-no-key/).", "priceSummary": "$0.10 / 1k req", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://www.visualcrossing.com/resources/documentation/weather-api/timeline-weather-api/", "llmsTxt": "https://www.visualcrossing.com/llms.txt", "openapi": "https://www.visualcrossing.com/weather/specs/visualcrossing-weather-api-openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.historical", "weather.alerts", "data.weather" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "closed-source", "usage-priced", "keyless" ], "graded": true, "anchor": { "graded": true, "score": 62.2, "grade": "B", "agentReady": false, "rank": 571, "ranked": true, "rankOf": 1510, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 58, "payments": 55, "reliability": 68, "schema": 74, "security": 40, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "History from 1970, current conditions and a 15-day forecast from one endpoint, and since 28 October callable with no key under IP-based fair-use limits. With a key, the REST API takes it only in the query string, and the status page's incident history could not be read.", "bestFor": "History and backfills, climate normals and date-range questions from one endpoint.", "strengths": [ "History from 1970, current conditions and a 15-day forecast from one endpoint", "No key or account needed for supported requests since 28 October 2026, commercial use allowed with attribution", "$0.0001 a record with 1,000 free a day on a keyed free account and no card", "Official MCP server with one tool, key in a header or OAuth", "llms.txt, an OpenAPI spec and a quarterly changelog, published 4 September 2026" ], "weaknesses": [ "With a key, the REST API takes it only in the query string", "The no-key route publishes no fixed allowance, and limits are shared by everyone behind one IP address", "OpenAPI spec defines no enums and no error responses, and still marks `key` required", "Privacy policy states no retention periods or subprocessors", "No security.txt, disclosure policy or MCP registry entry" ], "agentNotes": [ "Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records", "Try the no-key route first for light use, and on a 429 slow down and retry with backoff rather than switching IP addresses", "Show 'Weather data provided by Visual Crossing Weather' near any displayed data on free use", "Pass unitGroup=metric. The default is US units", "Use the MCP server with X-VC-API-Key rather than pasting a key into a URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.2 } ], "editorialScores": { "ergonomics": 78, "maintenance": 58, "payments": 55, "reliability": 68, "schema": 74, "security": 40, "transparency": 31 }, "provenanceScore": 82, "dataQualityScore": 77, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline/51.51,-0.13/2026-09-01/2026-09-07?unitGroup=metric\u0026include=days\u0026elements=datetime,tempmax,tempmin,precip\u0026contentType=json\u0026key=$VISUALCROSSING_API_KEY\"", "claudeCode": "claude mcp add --transport http visualcrossing https://mcp.visualcrossing.com/VisualCrossingWebServices/rest/api/v1/mcp --header \"X-VC-API-Key: $VISUALCROSSING_API_KEY\"", "config": { "mcpServers": { "visualcrossing": { "headers": { "X-VC-API-Key": "${VISUALCROSSING_API_KEY}" }, "type": "http", "url": "https://mcp.visualcrossing.com/VisualCrossingWebServices/rest/api/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/visual-crossing" }, "area": "domain-data", "unitPrices": [ { "item": "Metered record", "unit": "record", "usd": 0.0001, "note": "First 1,000 records a day free" }, { "item": "Metered, 15-day forecast calls", "unit": "1k-requests", "usd": 0.1, "note": "One record a forecast call, $0.0001 each" } ], "provenance": { "legalEntity": "Visual Crossing Corporation", "domain": "visualcrossing.com", "domainRegistered": "2005-10-11", "endpointOnVendorDomain": true, "terms": "https://www.visualcrossing.com/weather-services-terms/", "privacy": "https://www.visualcrossing.com/privacy/", "statusPage": "https://status.visualcrossing.com/", "changelog": "https://www.visualcrossing.com/resources/documentation/weather-api/weather-api-changelog/", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The terms (last updated January 2023) name Visual Crossing Corporation under Virginia law but give no address.", "The privacy policy is at /privacy/ (updated 23 May 2025). The /privacy-policy/ path returns 404.", "The status page at status.visualcrossing.com runs on UptimeRobot.", "/.well-known/security.txt returns 404 on 4 November 2026.", "The GitHub repository holds sample code in several languages, not an SDK." ], "score": 82 }, "dataQuality": { "coverage": "Global, any address or coordinate, up to 100 locations a query on Professional", "coverageRating": 4, "freshness": "Stations update every 15 to 30 minutes or hourly per the product page. Forecast refresh cadence not stated", "freshnessClass": "hourly", "history": "From 1970-01-01, hourly and daily, plus archived forecasts through the Historical Weather Forecast API added in Q2 2026", "historyYears": 56, "methodology": "https://www.visualcrossing.com/resources/documentation/weather-api/timeline-weather-api/", "sourcesDisclosed": true, "licence": "Proprietary. Storage by licence level, no resale, non-compete", "licenceClass": "clear", "standing": "", "standingClass": "none", "reuse": "Results may be stored in a database only where the licence level permits it, except for personal use. Resale and redistribution are barred, using the data to replicate a Visual Crossing service is barred, and Enterprise is the plan that adds external data-sharing rights. The pricing page's plan table (modified 23 October 2026) now marks results storable for shared internal and external use on every plan, which the January 2023 terms don't say.", "score": 77, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/visual-crossing.json", "live": { "slug": "visual-crossing", "probe": { "target": "https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline", "method": "get", "lastAt": "2026-11-08T00:56:13.393320936Z", "lastOk": true, "lastStatus": 400, "lastMs": 336, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 301, "p95ms24h": 392, "samples24h": 244, "samples30d": 7704, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.visualcrossing.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:32:34.268094167Z" }, "githubStars": 54, "securityTxt": { "url": "https://visualcrossing.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:20.452719032Z" }, "llmsTxt": { "url": "https://www.visualcrossing.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:18.542995208Z" }, "domain": { "domain": "visualcrossing.com", "registered": "2005-10-11", "source": "https://rdap.verisign.com/com/v1/domain/visualcrossing.com", "checkedAt": "2026-11-01T14:11:35.464071116Z" }, "pages": [ { "url": "https://www.visualcrossing.com/resources/documentation/weather-api/weather-api-changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:36:37.686418132Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "77ecfd35a643" }, { "url": "https://www.visualcrossing.com/weather-data-pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:36:42.390605741Z", "changedAt": "2026-10-24T02:38:07.446723832Z", "fingerprint": "74510a6bf6f0" }, { "url": "https://www.visualcrossing.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:36:35.489162756Z", "changedAt": "2026-10-29T05:29:24.390618658Z", "fingerprint": "a90e5e5e70cf" }, { "url": "https://www.visualcrossing.com/weather-services-terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:36:42.572126904Z", "changedAt": "2026-11-04T08:47:15.868785563Z", "fingerprint": "7aca1eeb6563" } ], "mcpTools": { "url": "https://mcp.visualcrossing.com/VisualCrossingWebServices/rest/api/v1/mcp", "checkedAt": "2026-11-07T01:48:57.530427674Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:57.530427674Z" }, "github": { "repo": "visualcrossing/weatherapi", "checkedAt": "2026-11-02T09:36:31.029549689Z", "stars": 54, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-07T11:03:13Z", "openIssues": 5, "openPRs": 28, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 6, "unanswered": 5, "medianDays": 0 } }, "updatedAt": "2026-11-08T00:56:13.393320936Z" } }, "edges": [ { "by": 33, "category": "reliability", "leads": "visual-crossing", "name": "Reliability", "reasons": { "a": "status.meteosource.com wasn't reachable (0). No history (5). Daily call quotas per plan, and the README's plans-and-limits section (15). Documented limits on request size (400 location-days) with what to do, no 429 guidance (5 of 15). No SLA found (0). Version 0.1.2, not labelled beta (10). 0 + 5 + 15 + 5 + 0 + 10 = 35.", "b": "Status page at status.visualcrossing.com, run on UptimeRobot, with 24-hour to 90-day uptime sections (20, held while this run's 15 or 20 split for UptimeRobot pages is open). On 4 November its monitor data still didn't load in the page we may read (its robots.txt disallows /api/, where the data comes from), and it showed no updates in the last seven days, so no incident record could be read (5). Limits published with numbers for registered plans, 1,000 records a day free, records and locations per query, and concurrency of 1 on Free and Professional and 10 on Corporate. The no-key route added on 28 October publishes no fixed allowance (15). 429 is documented for exceeded limits, and the no-key guide and llms.txt now say to retry with exponential backoff after a 429. Every call is a GET, so no write needs safe-retry guidance. Backoff guidance alone is 10 in this run (8 on 1 October, when none was found). The plan table lists 99.5 per cent uptime on Free and 99.9 on paid plans, but the terms only owe compensation where a plan includes crediting provisions (8 of 10). The Timeline API is generally available, with minutes marked beta (10). 20 + 5 + 15 + 10 + 8 + 10 = 68." }, "scores": { "a": 35, "b": 68 } }, { "by": 25, "category": "payments", "leads": "visual-crossing", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). Plan prices with daily call quotas, public (10). Free plan with 400 calls a day, no card (20). A person signs up in a browser for the key (0). 0 + 10 + 20 + 0 = 30.", "b": "No x402, MPP or L402 (0). $0.0001 a record above the free 1,000 a day, in the pricing page's own description, readable without login, though no plan shows a price in the page as served (20). 1,000 records a day free with a key and no card, and since 28 October a no-key route free for commercial use with attribution (20). An agent can call the Timeline and Maps APIs with no key, account or signup, per the no-key guide published 28 October 2026 and llms.txt, under IP-based fair-use limits with no fixed allowance. The same guide says some advanced queries or specialised data products may need a registered account, and the MCP server still needs a key, so the keyless route covers ordinary requests only. Partial credit, as for jina-reader (Search needs a key) and firecrawl-mcp (crawl, map and agent need a key) (15; 0 on 1 October, when a person had to sign up). 0 + 20 + 20 + 15 = 55." }, "scores": { "a": 30, "b": 55 } }, { "by": 25, "category": "transparency", "leads": "visual-crossing", "name": "Transparency \u0026 trust", "reasons": { "a": "The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25.", "b": "Closed service with terms last updated January 2023 that set storage by licence level, bar resale and add a non-compete (15). The privacy policy, updated 23 May 2025 per the 1 October check and the site's policy reading of 8 October, states no retention periods, says nothing about what API requests log and doesn't mention a DPA. The no-key guide says anonymous use is managed by client IP address, which the policy doesn't describe (8 of 30). The changelog promises backwards compatibility unless noted, but there's no deprecation policy or dated notice (8 of 20). No subprocessors or data locations named, beyond Google tags on the site (0). 15 + 8 + 8 + 0 = 31." }, "scores": { "a": 32, "b": 57 } }, { "by": 12, "category": "maintenance", "leads": "meteosource-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "Repository commit and tag v0.1.2 on 26 October 2026 (30). Three tags in 90 days (20). Repository issues not read (0). Official registry entry com.meteosource/weather (15). Small repository with server.json; server source not public (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.", "b": "The no-key guide, published 28 October 2026, adds keyless access to the Timeline and Maps APIs, and the Timeline docs changed the same day to describe it (30). Dated sources in the 90 days from 6 August are the changelog (published 4 September 2026, its four Q3 additions dated only by quarter), the MCP guide (published 24 September 2026) and the no-key guide (28 October 2026), three in all (20). Page modification stamps were not counted. A public changelog, and support by email and forum that we didn't test (8 of 15). The official MCP server isn't in the registry, where only a third-party Pipeworx wrapper appears (0.2.0, 29 October), and there's no official SDK (0). No package to judge (0). 30 + 20 + 8 + 0 + 0 = 58." }, "scores": { "a": 70, "b": 58 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Meteosource", "b": "Visual Crossing", "name": "Vendor" }, { "a": "https://mcp.meteosource.com/mcp", "b": "https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "not published", "b": "$0.10 per 1,000 requests", "name": "Price for weather forecasts" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The repository's MIT licence covers its docs and manifest", "b": "none", "name": "Licence" }, { "a": "7", "b": "1", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "com.meteosource/weather", "b": "not listed", "name": "MCP registry" }, { "a": "no document linked", "b": "2023-01-01", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Visual Crossing Weather API scores 62.2 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Meteosource Weather MCP or Visual Crossing Weather API?" }, { "answer": "Both need an API key.", "question": "Do Meteosource Weather MCP and Visual Crossing Weather API need an API key?" }, { "answer": "Yes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and Visual Crossing Weather API at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline.", "question": "Can an agent call Meteosource Weather MCP and Visual Crossing Weather API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 70 against 58" ], "also": null, "goodFor": "Agents that answer weather questions, plan around severe weather or estimate solar and wind output.", "slug": "meteosource-mcp", "watchFor": "Plain API key, no OAuth" }, { "aheadOn": [ "Reliability, 68 against 35", "Payments \u0026 pricing, 55 against 30", "Transparency \u0026 trust, 57 against 32" ], "also": [ "Free to start without a card" ], "goodFor": "History and backfills, climate normals and date-range questions from one endpoint.", "slug": "visual-crossing", "watchFor": "With a key, the REST API takes it only in the query string" } ], "history": { "meteosource-mcp": null, "visual-crossing": [ { "causes": [ "product" ], "date": "2026-11-04", "delta": 2.2, "from": 60, "fromGrade": "C", "to": 62.2, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 59.9, "fromGrade": "C", "to": 60, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.4, "from": 60.3, "fromGrade": "C", "to": 59.9, "toGrade": "C" } ] }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing.json", "title": "AccuWeather Core Weather API + MCP vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-visual-crossing.json", "title": "Google Weather API (Maps Platform) vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-visual-crossing.json", "title": "Met Office Weather DataHub (Site Specific) vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-visual-crossing" }, { "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/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/nws-api-vs-visual-crossing.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing.json", "title": "OpenWeather One Call API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/pirate-weather-vs-visual-crossing.json", "title": "Pirate Weather vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/pirate-weather-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.json", "title": "Tomorrow.io Weather API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.json", "title": "Visual Crossing Weather API vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com.json", "title": "Visual Crossing Weather API vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit.json", "title": "Visual Crossing Weather API vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/visual-crossing-vs-xweather.json", "title": "Visual Crossing Weather API vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/visual-crossing-vs-xweather" }, { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.json", "title": "AccuWeather Core Weather API + MCP vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp.json", "title": "Google Weather API (Maps Platform) vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp.json", "title": "Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.json", "title": "meteoblue Weather API vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.json", "title": "Meteomatics Weather API vs Meteosource Weather MCP", "url": "https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.json", "title": "Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.json", "title": "Meteosource Weather MCP vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.json", "title": "Meteosource Weather MCP vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.json", "title": "Meteosource Weather MCP vs Stormglass API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.json", "title": "Meteosource Weather MCP vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-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/stormglass-vs-visual-crossing.json", "title": "Stormglass API vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/stormglass-vs-visual-crossing" }, { "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.json", "title": "Meteosource Weather MCP vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo" }, { "json": "https://www.anchorterminal.com/compare/open-meteo-vs-visual-crossing.json", "title": "Open-Meteo vs Visual Crossing Weather API", "url": "https://www.anchorterminal.com/compare/open-meteo-vs-visual-crossing" } ], "panel": null, "scores": [ { "by": 33, "edge": "visual-crossing", "key": "reliability", "meteosource-mcp": 35, "name": "Reliability", "visual-crossing": 68, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "visual-crossing", "key": "schema", "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "visual-crossing": 74, "weight": 13 }, { "by": 3, "edge": "visual-crossing", "key": "ergonomics", "meteosource-mcp": 75, "name": "Agent ergonomics", "visual-crossing": 78, "weight": 13 }, { "by": 2, "edge": "meteosource-mcp", "key": "security", "meteosource-mcp": 42, "name": "Security \u0026 auth", "visual-crossing": 40, "weight": 14 }, { "by": 25, "edge": "visual-crossing", "key": "payments", "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "visual-crossing": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "meteosource-mcp", "key": "maintenance", "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "visual-crossing": 58, "weight": 7 }, { "by": 25, "edge": "visual-crossing", "key": "transparency", "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "visual-crossing": 57, "weight": 7 } ], "summary": "Visual Crossing Weather API scores 62.2 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on maintenance \u0026 community. Both do weather forecasts.", "tasks": null, "tutorials": [], "verdicts": { "meteosource-mcp": "Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.", "visual-crossing": "History from 1970, current conditions and a 15-day forecast from one endpoint, and since 28 October callable with no key under IP-based fair-use limits. With a key, the REST API takes it only in the query string, and the status page's incident history could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing", "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.min.md" }, "markdown": "Visual Crossing Weather API scores 62.2 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on maintenance \u0026 community. Both do weather forecasts.\n\n- Meteosource Weather MCP: grade D, 50.9/100, rank #1048 of 1510. Markdown https://www.anchorterminal.com/tools/meteosource-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json\n- Visual Crossing Weather API: grade B, 62.2/100, rank #571 of 1510. Markdown https://www.anchorterminal.com/tools/visual-crossing.md · JSON https://www.anchorterminal.com/api/v1/tools/visual-crossing.json\n- Best weather and climate data APIs for AI agents: https://www.anchorterminal.com/best/weather/index.md\n- All 136 weather comparisons: https://www.anchorterminal.com/compare/weather/index.md\n\n## Which one, for what\n\n### Meteosource Weather MCP (D)\n\nGood for: Agents that answer weather questions, plan around severe weather or estimate solar and wind output.\n\nAhead on:\n- Maintenance \u0026 community, 70 against 58\n\nWatch for: Plain API key, no OAuth\n\n### Visual Crossing Weather API (B)\n\nGood for: History and backfills, climate normals and date-range questions from one endpoint.\n\nAhead on:\n- Reliability, 68 against 35\n- Payments \u0026 pricing, 55 against 30\n- Transparency \u0026 trust, 57 against 32\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: With a key, the REST API takes it only in the query string\n\n\n## Why the edge\n\n### Reliability: Visual Crossing Weather API +33\n\n- Meteosource Weather MCP (35): status.meteosource.com wasn't reachable (0). No history (5). Daily call quotas per plan, and the README's plans-and-limits section (15). Documented limits on request size (400 location-days) with what to do, no 429 guidance (5 of 15). No SLA found (0). Version 0.1.2, not labelled beta (10). 0 + 5 + 15 + 5 + 0 + 10 = 35.\n- Visual Crossing Weather API (68): Status page at status.visualcrossing.com, run on UptimeRobot, with 24-hour to 90-day uptime sections (20, held while this run's 15 or 20 split for UptimeRobot pages is open). On 4 November its monitor data still didn't load in the page we may read (its robots.txt disallows /api/, where the data comes from), and it showed no updates in the last seven days, so no incident record could be read (5). Limits published with numbers for registered plans, 1,000 records a day free, records and locations per query, and concurrency of 1 on Free and Professional and 10 on Corporate. The no-key route added on 28 October publishes no fixed allowance (15). 429 is documented for exceeded limits, and the no-key guide and llms.txt now say to retry with exponential backoff after a 429. Every call is a GET, so no write needs safe-retry guidance. Backoff guidance alone is 10 in this run (8 on 1 October, when none was found). The plan table lists 99.5 per cent uptime on Free and 99.9 on paid plans, but the terms only owe compensation where a plan includes crediting provisions (8 of 10). The Timeline API is generally available, with minutes marked beta (10). 20 + 5 + 15 + 10 + 8 + 10 = 68.\n\n### Payments \u0026 pricing: Visual Crossing Weather API +25\n\n- Meteosource Weather MCP (30): No machine payment protocol (0). Plan prices with daily call quotas, public (10). Free plan with 400 calls a day, no card (20). A person signs up in a browser for the key (0). 0 + 10 + 20 + 0 = 30.\n- Visual Crossing Weather API (55): No x402, MPP or L402 (0). $0.0001 a record above the free 1,000 a day, in the pricing page's own description, readable without login, though no plan shows a price in the page as served (20). 1,000 records a day free with a key and no card, and since 28 October a no-key route free for commercial use with attribution (20). An agent can call the Timeline and Maps APIs with no key, account or signup, per the no-key guide published 28 October 2026 and llms.txt, under IP-based fair-use limits with no fixed allowance. The same guide says some advanced queries or specialised data products may need a registered account, and the MCP server still needs a key, so the keyless route covers ordinary requests only. Partial credit, as for jina-reader (Search needs a key) and firecrawl-mcp (crawl, map and agent need a key) (15; 0 on 1 October, when a person had to sign up). 0 + 20 + 20 + 15 = 55.\n\n### Transparency \u0026 trust: Visual Crossing Weather API +25\n\n- Meteosource Weather MCP (32): The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25.\n- Visual Crossing Weather API (57): Closed service with terms last updated January 2023 that set storage by licence level, bar resale and add a non-compete (15). The privacy policy, updated 23 May 2025 per the 1 October check and the site's policy reading of 8 October, states no retention periods, says nothing about what API requests log and doesn't mention a DPA. The no-key guide says anonymous use is managed by client IP address, which the policy doesn't describe (8 of 30). The changelog promises backwards compatibility unless noted, but there's no deprecation policy or dated notice (8 of 20). No subprocessors or data locations named, beyond Google tags on the site (0). 15 + 8 + 8 + 0 = 31.\n\n### Maintenance \u0026 community: Meteosource Weather MCP +12\n\n- Meteosource Weather MCP (70): Repository commit and tag v0.1.2 on 26 October 2026 (30). Three tags in 90 days (20). Repository issues not read (0). Official registry entry com.meteosource/weather (15). Small repository with server.json; server source not public (5 of 10). 30 + 20 + 0 + 15 + 5 = 70. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.\n- Visual Crossing Weather API (58): The no-key guide, published 28 October 2026, adds keyless access to the Timeline and Maps APIs, and the Timeline docs changed the same day to describe it (30). Dated sources in the 90 days from 6 August are the changelog (published 4 September 2026, its four Q3 additions dated only by quarter), the MCP guide (published 24 September 2026) and the no-key guide (28 October 2026), three in all (20). Page modification stamps were not counted. A public changelog, and support by email and forum that we didn't test (8 of 15). The official MCP server isn't in the registry, where only a third-party Pipeworx wrapper appears (0.2.0, 29 October), and there's no official SDK (0). No package to judge (0). 30 + 20 + 8 + 0 + 0 = 58.\n\n## Score by category\n\n| Category | Weight | Meteosource Weather MCP | Visual Crossing Weather API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 68 | Visual Crossing Weather API +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 74 | Visual Crossing Weather API +2 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 78 | Visual Crossing Weather API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 40 | Meteosource Weather MCP +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 55 | Visual Crossing Weather API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 58 | Meteosource Weather MCP +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 57 | Visual Crossing Weather API +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.9 · D** | **62.2 · B** | |\n\n## Facts side by side\n\n| Fact | Meteosource Weather MCP | Visual Crossing Weather API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Meteosource | Visual Crossing |\n| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| Price for weather forecasts | not published | $0.10 per 1,000 requests |\n| x402 | no | no |\n| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | none |\n| Tools exposed | 7 | 1 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `com.meteosource/weather` | not listed |\n| Terms last updated | no document linked | 2023-01-01 |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Agent reviews | none | 4/5 (2) |\n\n## How the scores have moved\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n### Visual Crossing Weather API\n\n- +2.2 on 4 November 2026 (C to B): product\n- +0.1 on 27 October 2026: new evidence\n- -0.4 on 8 October 2026: checklist\n\n## Verdicts\n\n**Meteosource Weather MCP.** Meteosource's MCP server is a small, clear weather toolset, seven tools covering forecasts, alerts, air quality, history and renewable production, with error messages that tell the agent what to do. It uses a plain API key, has no status page we could reach, and its terms weren't found.\n\n**Visual Crossing Weather API.** History from 1970, current conditions and a 15-day forecast from one endpoint, and since 28 October callable with no key under IP-based fair-use limits. With a key, the REST API takes it only in the query string, and the status page's incident history could not be read.\n\n## Before you call either\n\n### Meteosource Weather MCP\n\n1. Call search_places first to resolve a location\n2. Split history requests over 400 location-days into shorter ranges\n3. Production tools need the Renewables plan; check which tools the key exposes\n4. Send the key in a header, never in a URL\n\n### Visual Crossing Weather API\n\n1. Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records\n2. Try the no-key route first for light use, and on a 429 slow down and retry with backoff rather than switching IP addresses\n3. Show 'Weather data provided by Visual Crossing Weather' near any displayed data on free use\n4. Pass unitGroup=metric. The default is US units\n5. Use the MCP server with X-VC-API-Key rather than pasting a key into a URL\n\n## Questions\n\n### Which is better for AI agents, Meteosource Weather MCP or Visual Crossing Weather API?\n\nVisual Crossing Weather API scores 62.2 (B) on agent readiness against Meteosource Weather MCP's 50.9 (D), and leads in 5 of 7 scored categories. Meteosource Weather MCP leads on maintenance \u0026 community.\n\n### Do Meteosource Weather MCP and Visual Crossing Weather API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Meteosource Weather MCP and Visual Crossing Weather API without installing anything?\n\nYes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and Visual Crossing Weather API at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteosource-mcp\", \"b\": \"visual-crossing\"}`. From a terminal: `anchor compare meteosource-mcp visual-crossing`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json and https://www.anchorterminal.com/api/v1/tools/visual-crossing.json\n\n## Other comparisons with Meteosource Weather MCP or Visual Crossing Weather API\n\n- [AccuWeather Core Weather API + MCP vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/accuweather-api-vs-visual-crossing.md)\n- [Google Weather API (Maps Platform) vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/google-weather-api-vs-visual-crossing.md)\n- [Met Office Weather DataHub (Site Specific) vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/met-office-datahub-vs-visual-crossing.md)\n- [meteoblue Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteoblue-vs-visual-crossing.md)\n- [Meteomatics Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/meteomatics-vs-visual-crossing.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/nws-api-vs-visual-crossing.md)\n- [OpenWeather One Call API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/openweather-one-call-vs-visual-crossing.md)\n- [Pirate Weather vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/pirate-weather-vs-visual-crossing.md)\n- [Tomorrow.io Weather API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/tomorrow-io-vs-visual-crossing.md)\n- [Visual Crossing Weather API vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/visual-crossing-vs-weather-company.md)\n- [Visual Crossing Weather API vs WeatherAPI.com](https://www.anchorterminal.com/compare/visual-crossing-vs-weatherapi-com.md)\n- [Visual Crossing Weather API vs Weatherbit API](https://www.anchorterminal.com/compare/visual-crossing-vs-weatherbit.md)\n- [Visual Crossing Weather API vs Xweather Weather API](https://www.anchorterminal.com/compare/visual-crossing-vs-xweather.md)\n- [AccuWeather Core Weather API + MCP vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/accuweather-api-vs-meteosource-mcp.md)\n- [Google Weather API (Maps Platform) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/google-weather-api-vs-meteosource-mcp.md)\n- [Met Office Weather DataHub (Site Specific) vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/met-office-datahub-vs-meteosource-mcp.md)\n- [meteoblue Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteoblue-vs-meteosource-mcp.md)\n- [Meteomatics Weather API vs Meteosource Weather MCP](https://www.anchorterminal.com/compare/meteomatics-vs-meteosource-mcp.md)\n- [Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.md)\n- [Meteosource Weather MCP vs OpenWeather One Call API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-openweather-one-call.md)\n- [Meteosource Weather MCP vs Pirate Weather](https://www.anchorterminal.com/compare/meteosource-mcp-vs-pirate-weather.md)\n- [Meteosource Weather MCP vs Stormglass API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-stormglass.md)\n- [Meteosource Weather MCP vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/meteosource-mcp-vs-tomorrow-io.md)\n- [Meteosource Weather MCP vs 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- [Stormglass API vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/stormglass-vs-visual-crossing.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n- [Open-Meteo vs Visual Crossing Weather API](https://www.anchorterminal.com/compare/open-meteo-vs-visual-crossing.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Meteosource Weather MCP vs Visual Crossing Weather API", "url": "" } ], "description": "Visual Crossing Weather scores 62.2 (B) to Meteosource Weather MCP's 50.9 (D) for weather forecasts. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Meteosource Weather MCP D 50.9", "Visual Crossing Weather API B 62.2", "scores" ], "h1": "Meteosource Weather MCP vs Visual Crossing Weather API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteosource-mcp-vs-visual-crossing", "published": "2026-10-01", "section": "tools", "title": "Meteosource Weather MCP vs Visual Crossing Weather (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-visual-crossing" }, "tokens": { "markdown": 4200, "slim": 2030 }, "version": 1 }