{ "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": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 48.4 (D), and leads in 4 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "nws-api", "name": "NOAA National Weather Service API (api.weather.gov)", "vendor": "National Weather Service", "vendorUrl": "https://www.weather.gov/documentation/services-web-api", "kind": "http-api", "category": "weather", "summary": "The US government's own forecast, alert and observation feed, free, keyless and public domain.", "url": "https://www.anchorterminal.com/tools/nws-api", "markdownUrl": "https://www.anchorterminal.com/tools/nws-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nws-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nws-api.json", "dns": "nws-api.grade.anchorterminal.com", "repo": "https://github.com/weather-gov/api", "license": "Public domain (data)", "transports": [ "http" ], "remoteUrl": "https://api.weather.gov", "packages": [], "auth": "none", "authNotes": "No key. A User-Agent header that identifies the application, ideally with a contact email, is required and requests without one are refused.", "pricing": "free", "pricingNotes": "Free. The rate limit isn't published but is described as generous for typical use, and a throttled request can be retried after about five seconds (https://www.weather.gov/documentation/services-web-api).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 310, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://www.weather.gov/documentation/services-web-api", "openapi": "https://api.weather.gov/openapi.json", "capabilities": [ "weather.current", "weather.forecast", "weather.alerts", "data.weather" ], "tags": [ "hosted", "official", "government", "free", "no-key", "open-data", "openapi" ], "lastRelease": "2026-03-19", "graded": true, "anchor": { "graded": true, "score": 48.4, "grade": "D", "agentReady": false, "rank": 1125, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 8, "payments": 60, "reliability": 25, "schema": 67, "security": 45, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Free, no key and no account, with public domain data. US and territories only.", "bestFor": "The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.", "strengths": [ "Free, no key and no account, with public domain data", "Official watches, warnings and text products from the issuing agency, filterable by point, zone, event and severity", "OpenAPI 3.0 document and RFC 7807 error bodies", "Cache-Control and Last-Modified on every response, so conditional requests work" ], "weaknesses": [ "US and territories only", "Rate limit not published, and no status page or SLA", "No dated API change since 17 March 2026", "No SDK, MCP server, llms.txt or security.txt, and no readable disclosure policy" ], "agentNotes": [ "Set User-Agent to your app name and a contact email or the request is refused with 403", "Cache the /points response per coordinate. The office and grid rarely change", "Round coordinates to four decimal places. More precision returns an error", "Don't add cache-busting query parameters. Unknown parameters return 400", "Back off about five seconds after a throttled request and reuse the last good response", "Fetch station observations within 7 days. Older ones aren't kept" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.4 } ], "editorialScores": { "ergonomics": 66, "maintenance": 8, "payments": 60, "reliability": 25, "schema": 67, "security": 45, "transparency": 53 }, "provenanceScore": 76, "dataQualityScore": 67, "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 -H \"User-Agent: (myagent.example, ops@myagent.example)\" -H \"Accept: application/geo+json\" \"https://api.weather.gov/points/38.8894,-77.0352\"" }, "letme": { "capability": "https://letme.dev/weather.current", "tool": "https://letme.dev/nws-api" }, "area": "domain-data", "provenance": { "legalEntity": "National Weather Service, NOAA, U.S. Department of Commerce", "domain": "weather.gov", "domainRegistered": "1999-04-30", "official": true, "endpointOnVendorDomain": true, "terms": "https://www.weather.gov/disclaimer", "privacy": "https://www.weather.gov/privacy", "statusPage": "", "changelog": "https://www.weather.gov/documentation/services-web-api", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The disclaimer says NWS information is public domain unless noted, is supplied as is, and that the NWS name and identifier are trademarked.", "The privacy policy says the date, time and originating IP of each request are logged and may be kept indefinitely for security.", "www.weather.gov/.well-known/security.txt returns 404. The Department of Commerce vulnerability disclosure policy page on www.commerce.gov couldn't be read on 4 November (its robots.txt answered a bot check).", "The docs page carries a dated list of API changes. Wider service changes go out as NWS Service Change Notices and Public Information Statements.", "There's no status page. Outages are reported to NCO Tech Control, and the NCEP Senior Duty Meteorologist messages are the nearest public log." ], "score": 76 }, "dataQuality": { "coverage": "United States and its territories, on each forecast office's 2.5 km grid", "coverageRating": 2, "freshness": "Not stated per endpoint. Responses carry Cache-Control and Last-Modified so clients can see the age", "freshnessClass": "hourly", "history": "Seven days of station observations. Climate records are at NOAA's NCEI, not this API", "historyYears": 0, "methodology": "https://www.weather.gov/documentation/services-web-api", "sourcesDisclosed": true, "licence": "Public domain", "licenceClass": "open", "standing": "The US federal weather service, issuer of official US watches and warnings", "standingClass": "statutory", "reuse": "Public domain and free for any lawful purpose. Cache and redistribute as you like, don't imply NWS endorsement, and note that works built mostly on NWS material can't claim copyright over it.", "score": 67, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nws-api.json", "live": { "slug": "nws-api", "probe": { "target": "https://api.weather.gov", "method": "get", "lastAt": "2026-11-08T00:55:54.653193517Z", "lastOk": true, "lastStatus": 200, "lastMs": 185, "authRequired": false, "uptime24h": 100, "uptime30d": 99.77, "p50ms24h": 162, "p95ms24h": 306, "samples24h": 244, "samples30d": 7704, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 248 }, { "date": "2026-10-10", "probes": 247, "ok": 245 }, { "date": "2026-10-11", "probes": 247, "ok": 246 }, { "date": "2026-10-12", "probes": 247, "ok": 240 }, { "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": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 250 }, { "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 248 }, { "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": 184 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "githubStars": 311, "securityTxt": { "url": "https://weather.gov/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:32.53522365Z" }, "pages": [ { "url": "https://www.weather.gov/documentation/services-web-api", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:36:53.170681861Z", "changedAt": "2026-11-07T14:36:53.170681861Z", "fingerprint": "9425608debd5" }, { "url": "https://www.weather.gov/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:36:53.433974481Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "00331ba8517d" }, { "url": "https://www.weather.gov/disclaimer", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:36:47.552979542Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f32d8c8c8de4" } ], "github": { "repo": "weather-gov/api", "checkedAt": "2026-11-02T09:37:50.789197641Z", "stars": 311, "archived": false, "issuesEnabled": false, "pushedAt": "2024-05-08T18:52:05Z", "openIssues": 0, "openPRs": 1, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-11-08T00:55:54.653193517Z" } }, "edges": [ { "by": 62, "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 last dated API change is the radar queue limit of 17 March 2026 on the docs page, which still reads 'Updated 3/24/2026' on 4 November, 232 days before this check (0). Service Change Notice 26-80 of 14 September 2026 names api.weather.gov among hosts that drop older TLS 1.2 cipher suites on or about 2 March 2027, a notice of a future change rather than a change (0). No dated changes in the last 90 days (0). A dated changes list on the docs page and a Discussions forum where NWS staff last answered on 3 July 2026, per the 1 October check; GitHub's pages weren't readable on 4 November (8 of 15). No official SDK (0). No package to judge (0). 0 + 0 + 8 + 0 + 0 = 8." }, "scores": { "a": 70, "b": 8 } }, { "by": 33, "category": "transparency", "leads": "nws-api", "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": "The service code isn't published, but the data is public domain and the disclaimer says so plainly. We gave 20 rather than the 15 for closed services because the data licence is as clear as it gets (20 of 30). The privacy policy lists what each request logs (date, time, IP, browser, referrer) and says the logs 'may be preserved indefinitely' for security, while raw logs are 'scheduled for regular destruction' under the National Archives schedule. No separate API data statement (18 of 30). Changes arrive as Service Change Notices and Public Information Statements with dates and comment periods, among them SCN 26-80 (14 September 2026) giving five and a half months' notice of the api.weather.gov cipher change, but no written deprecation policy (15 of 20). No subprocessors or hosting locations named (0). 20 + 18 + 15 + 0 = 53." }, "scores": { "a": 32, "b": 65 } }, { "by": 30, "category": "payments", "leads": "nws-api", "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). Free, and the docs say so (20). No card, no account (20). Keyless, so an agent can call it with nothing but a User-Agent (20). 0 + 20 + 20 + 20 = 60." }, "scores": { "a": 30, "b": 60 } }, { "by": 10, "category": "reliability", "leads": "meteosource-mcp", "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": "No status page for the API (0). Outages go to NCO Tech Control by email or phone, and the NCEP Senior Duty Meteorologist messages are a free-text log with no component history. On 4 November the log reached back to 20 October and none of its messages named the API (one named a forecast.weather.gov website slowdown on 20 October), so there is no readable history (5). The rate limit is described as 'not public information' (0). The docs say a throttled request 'may be retried after the limit clears (typically within 5 seconds)', the disclaimer asks clients to limit retries of an unavailable service to one-minute intervals, and every call is a GET, but no Retry-After header is documented (10 of 15). No SLA, and no paid tier to carry one (0). The API is the operational NWS service (10). 0 + 5 + 0 + 10 + 0 + 10 = 25." }, "scores": { "a": 35, "b": 25 } }, { "by": 9, "category": "ergonomics", "leads": "meteosource-mcp", "name": "Agent ergonomics", "reasons": { "a": "Seven tools, about 20 KB (25). Date ranges and location limits on history (12 of 20). Documented error messages with fixes (15 of 20). No annotations on the tools (8 of 20, all reads). Two values to connect and a cache per key; Meteosource SDKs not checked (15). 25 + 12 + 15 + 8 + 15 = 75.", "b": "Forecasts come back whole, with no field selection, though `units` and the Accept header shape them (12 of 25). Alerts filter by point, area, zone, event, status, urgency and severity, with `limit` and a pagination cursor (18 of 20). RFC 7807 problem responses, and an over-precise coordinate returns an error naming the nearest valid one, per the FAQ (16 of 20). Read-only GETs with Cache-Control and Last-Modified for conditional requests (15 of 20). Every forecast needs the /points call first, and there's no official SDK in any language (5 of 15). 12 + 18 + 16 + 15 + 5 = 66." }, "scores": { "a": 75, "b": 66 } }, { "by": 5, "category": "schema", "leads": "meteosource-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72.", "b": "The docs page links the OpenAPI document at api.weather.gov/openapi.json as 'the specification endpoint', and the FAQ names openapi.json and openapi.yaml. We don't request the API host, so its content is read from the 2021 copy in the public repository (25). No llms.txt or Markdown docs (0). Parameter descriptions are one-liners such as 'Limit', and the FAQ says 'we're still working on documentation for the JSON'. The when-to-use guidance (resolve /points first, cache it) sits in the docs and FAQ, not the spec (8 of 20). The 2021 copy of the spec has 52 enums and bounded integers such as limit 1 to 500 (12 of 15). Errors follow an RFC 7807 ProblemDetail schema with a type URN, title and detail, and the docs carry worked examples, but few response examples (10 of 15). Feature flags sent as a Feature-Flags header, a dated changes list on the docs page (still 'Updated 3/24/2026' on 4 November) and release posts in GitHub Discussions per the 1 October check (12 of 15). 25 + 0 + 8 + 12 + 10 + 12 = 67." }, "scores": { "a": 72, "b": 67 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Meteosource", "b": "National Weather Service", "name": "Vendor" }, { "a": "https://mcp.meteosource.com/mcp", "b": "https://api.weather.gov", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. The repository's MIT licence covers its docs and manifest", "b": "Public domain (data)", "name": "Licence" }, { "a": "7", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "com.meteosource/weather", "b": "not listed", "name": "MCP registry" }, { "a": "none", "b": "2026-03-19", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "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": "310 stars", "name": "Popularity" }, { "a": "none", "b": "4.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 48.4 (D), and leads in 4 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, Meteosource Weather MCP or NOAA National Weather Service API (api.weather.gov)?" }, { "answer": "Meteosource Weather MCP needs an API key. NOAA National Weather Service API (api.weather.gov) needs no key.", "question": "Do Meteosource Weather MCP and NOAA National Weather Service API (api.weather.gov) need an API key?" }, { "answer": "Yes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.", "question": "Can an agent call Meteosource Weather MCP and NOAA National Weather Service API (api.weather.gov) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 35 against 25", "Schema \u0026 documentation, 72 against 67", "Agent ergonomics, 75 against 66", "Maintenance \u0026 community, 70 against 8" ], "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": [ "Payments \u0026 pricing, 60 against 30", "Transparency \u0026 trust, 65 against 32" ], "also": [ "No key needed to call it" ], "goodFor": "The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.", "slug": "nws-api", "watchFor": "US and territories only" } ], "history": { "meteosource-mcp": null, "nws-api": [ { "causes": [ "evidence" ], "date": "2026-11-04", "delta": -1.4, "from": 49.8, "fromGrade": "D", "to": 48.4, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 49.6, "fromGrade": "D", "to": 49.8, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 49.9, "fromGrade": "D", "to": 49.6, "toGrade": "D" } ] }, "job": { "capability": "weather.forecast", "name": "Weather forecasts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api.json", "title": "AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/google-weather-api-vs-nws-api.json", "title": "Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/google-weather-api-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/met-office-datahub-vs-nws-api.json", "title": "Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/met-office-datahub-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.json", "title": "meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)", "url": "https://www.anchorterminal.com/compare/meteoblue-vs-nws-api" }, { "json": "https://www.anchorterminal.com/compare/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/nws-api-vs-openweather-one-call.json", "title": "NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-openweather-one-call" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-pirate-weather.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Pirate Weather", "url": "https://www.anchorterminal.com/compare/nws-api-vs-pirate-weather" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io" }, { "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/nws-api-vs-weather-company.json", "title": "NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weather-company" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.json", "title": "NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-weatherbit.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Weatherbit API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-weatherbit" }, { "json": "https://www.anchorterminal.com/compare/nws-api-vs-xweather.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API", "url": "https://www.anchorterminal.com/compare/nws-api-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-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/nws-api-vs-stormglass.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Stormglass API", "url": "https://www.anchorterminal.com/compare/nws-api-vs-stormglass" }, { "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/nws-api-vs-open-meteo.json", "title": "NOAA National Weather Service API (api.weather.gov) vs Open-Meteo", "url": "https://www.anchorterminal.com/compare/nws-api-vs-open-meteo" } ], "panel": null, "scores": [ { "by": 10, "edge": "meteosource-mcp", "key": "reliability", "meteosource-mcp": 35, "name": "Reliability", "nws-api": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "meteosource-mcp", "key": "schema", "meteosource-mcp": 72, "name": "Schema \u0026 documentation", "nws-api": 67, "weight": 13 }, { "by": 9, "edge": "meteosource-mcp", "key": "ergonomics", "meteosource-mcp": 75, "name": "Agent ergonomics", "nws-api": 66, "weight": 13 }, { "by": 3, "edge": "nws-api", "key": "security", "meteosource-mcp": 42, "name": "Security \u0026 auth", "nws-api": 45, "weight": 14 }, { "by": 30, "edge": "nws-api", "key": "payments", "meteosource-mcp": 30, "name": "Payments \u0026 pricing", "nws-api": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 62, "edge": "meteosource-mcp", "key": "maintenance", "meteosource-mcp": 70, "name": "Maintenance \u0026 community", "nws-api": 8, "weight": 7 }, { "by": 33, "edge": "nws-api", "key": "transparency", "meteosource-mcp": 32, "name": "Transparency \u0026 trust", "nws-api": 65, "weight": 7 } ], "summary": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 48.4 (D), and leads in 4 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing and transparency \u0026 trust. 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.", "nws-api": "Free, no key and no account, with public domain data. US and territories only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api", "json": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.min.md" }, "markdown": "Meteosource Weather MCP scores 50.9 (D) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 48.4 (D), and leads in 4 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing and transparency \u0026 trust. 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- NOAA National Weather Service API (api.weather.gov): grade D, 48.4/100, rank #1125 of 1510. Markdown https://www.anchorterminal.com/tools/nws-api.md · JSON https://www.anchorterminal.com/api/v1/tools/nws-api.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- Reliability, 35 against 25\n- Schema \u0026 documentation, 72 against 67\n- Agent ergonomics, 75 against 66\n- Maintenance \u0026 community, 70 against 8\n\nWatch for: Plain API key, no OAuth\n\n### NOAA National Weather Service API (api.weather.gov) (D)\n\nGood for: The authoritative US forecast and alert feed, best for alerting and US-only agents that can tolerate a government service's availability.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 30\n- Transparency \u0026 trust, 65 against 32\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: US and territories only\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Meteosource Weather MCP +62\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- NOAA National Weather Service API (api.weather.gov) (8): The last dated API change is the radar queue limit of 17 March 2026 on the docs page, which still reads 'Updated 3/24/2026' on 4 November, 232 days before this check (0). Service Change Notice 26-80 of 14 September 2026 names api.weather.gov among hosts that drop older TLS 1.2 cipher suites on or about 2 March 2027, a notice of a future change rather than a change (0). No dated changes in the last 90 days (0). A dated changes list on the docs page and a Discussions forum where NWS staff last answered on 3 July 2026, per the 1 October check; GitHub's pages weren't readable on 4 November (8 of 15). No official SDK (0). No package to judge (0). 0 + 0 + 8 + 0 + 0 = 8.\n\n### Transparency \u0026 trust: NOAA National Weather Service API (api.weather.gov) +33\n\n- Meteosource Weather MCP (32): The repository is MIT (copyright 2026 Meteosource) but holds docs and the registry manifest rather than the server; terms and privacy URLs weren't found (10 of 30). The MCP page says keys aren't stored in full and caches are per key (10 of 30). No deprecation policy (0). Subprocessors not found (5 of 20). 10 + 10 + 0 + 5 = 25.\n- NOAA National Weather Service API (api.weather.gov) (65): The service code isn't published, but the data is public domain and the disclaimer says so plainly. We gave 20 rather than the 15 for closed services because the data licence is as clear as it gets (20 of 30). The privacy policy lists what each request logs (date, time, IP, browser, referrer) and says the logs 'may be preserved indefinitely' for security, while raw logs are 'scheduled for regular destruction' under the National Archives schedule. No separate API data statement (18 of 30). Changes arrive as Service Change Notices and Public Information Statements with dates and comment periods, among them SCN 26-80 (14 September 2026) giving five and a half months' notice of the api.weather.gov cipher change, but no written deprecation policy (15 of 20). No subprocessors or hosting locations named (0). 20 + 18 + 15 + 0 = 53.\n\n### Payments \u0026 pricing: NOAA National Weather Service API (api.weather.gov) +30\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- NOAA National Weather Service API (api.weather.gov) (60): No x402, MPP or L402 (0). Free, and the docs say so (20). No card, no account (20). Keyless, so an agent can call it with nothing but a User-Agent (20). 0 + 20 + 20 + 20 = 60.\n\n### Reliability: Meteosource Weather MCP +10\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- NOAA National Weather Service API (api.weather.gov) (25): No status page for the API (0). Outages go to NCO Tech Control by email or phone, and the NCEP Senior Duty Meteorologist messages are a free-text log with no component history. On 4 November the log reached back to 20 October and none of its messages named the API (one named a forecast.weather.gov website slowdown on 20 October), so there is no readable history (5). The rate limit is described as 'not public information' (0). The docs say a throttled request 'may be retried after the limit clears (typically within 5 seconds)', the disclaimer asks clients to limit retries of an unavailable service to one-minute intervals, and every call is a GET, but no Retry-After header is documented (10 of 15). No SLA, and no paid tier to carry one (0). The API is the operational NWS service (10). 0 + 5 + 0 + 10 + 0 + 10 = 25.\n\n### Agent ergonomics: Meteosource Weather MCP +9\n\n- Meteosource Weather MCP (75): Seven tools, about 20 KB (25). Date ranges and location limits on history (12 of 20). Documented error messages with fixes (15 of 20). No annotations on the tools (8 of 20, all reads). Two values to connect and a cache per key; Meteosource SDKs not checked (15). 25 + 12 + 15 + 8 + 15 = 75.\n- NOAA National Weather Service API (api.weather.gov) (66): Forecasts come back whole, with no field selection, though `units` and the Accept header shape them (12 of 25). Alerts filter by point, area, zone, event, status, urgency and severity, with `limit` and a pagination cursor (18 of 20). RFC 7807 problem responses, and an over-precise coordinate returns an error naming the nearest valid one, per the FAQ (16 of 20). Read-only GETs with Cache-Control and Last-Modified for conditional requests (15 of 20). Every forecast needs the /points call first, and there's no official SDK in any language (5 of 15). 12 + 18 + 16 + 15 + 5 = 66.\n\n### Schema \u0026 documentation: Meteosource Weather MCP +5\n\n- Meteosource Weather MCP (72): Seven tools read from tools/list with JSON Schema inputs (25). No llms.txt found; the README is Markdown on GitHub (5 of 10). Descriptions say what each returns and which plan it needs (15 of 20). Typed inputs, no enums (10 of 15). A README table of error messages and fixes (10 of 15). Tagged releases v0.1.0 to v0.1.2, no changelog file (7 of 15). 25 + 5 + 15 + 10 + 10 + 7 = 72.\n- NOAA National Weather Service API (api.weather.gov) (67): The docs page links the OpenAPI document at api.weather.gov/openapi.json as 'the specification endpoint', and the FAQ names openapi.json and openapi.yaml. We don't request the API host, so its content is read from the 2021 copy in the public repository (25). No llms.txt or Markdown docs (0). Parameter descriptions are one-liners such as 'Limit', and the FAQ says 'we're still working on documentation for the JSON'. The when-to-use guidance (resolve /points first, cache it) sits in the docs and FAQ, not the spec (8 of 20). The 2021 copy of the spec has 52 enums and bounded integers such as limit 1 to 500 (12 of 15). Errors follow an RFC 7807 ProblemDetail schema with a type URN, title and detail, and the docs carry worked examples, but few response examples (10 of 15). Feature flags sent as a Feature-Flags header, a dated changes list on the docs page (still 'Updated 3/24/2026' on 4 November) and release posts in GitHub Discussions per the 1 October check (12 of 15). 25 + 0 + 8 + 12 + 10 + 12 = 67.\n\n## Score by category\n\n| Category | Weight | Meteosource Weather MCP | NOAA National Weather Service API (api.weather.gov) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 25 | Meteosource Weather MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 67 | Meteosource Weather MCP +5 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 66 | Meteosource Weather MCP +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 45 | NOAA National Weather Service API (api.weather.gov) +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 60 | NOAA National Weather Service API (api.weather.gov) +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 8 | Meteosource Weather MCP +62 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 65 | NOAA National Weather Service API (api.weather.gov) +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.9 · D** | **48.4 · D** | |\n\n## Facts side by side\n\n| Fact | Meteosource Weather MCP | NOAA National Weather Service API (api.weather.gov) |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Meteosource | National Weather Service |\n| Hosted endpoint | `https://mcp.meteosource.com/mcp` | `https://api.weather.gov` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | API key | None |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | Public domain (data) |\n| Tools exposed | 7 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| MCP registry | `com.meteosource/weather` | not listed |\n| Last release | none | 2026-03-19 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\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| Popularity | none | 310 stars |\n| Agent reviews | none | 4.5/5 (2) |\n\n## How the scores have moved\n\n### Meteosource Weather MCP\n\nNo score change since it was listed.\n\n### NOAA National Weather Service API (api.weather.gov)\n\n- -1.4 on 4 November 2026: new evidence\n- +0.2 on 27 October 2026: checklist\n- -0.3 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**NOAA National Weather Service API (api.weather.gov).** Free, no key and no account, with public domain data. US and territories only.\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### NOAA National Weather Service API (api.weather.gov)\n\n1. Set User-Agent to your app name and a contact email or the request is refused with 403\n2. Cache the /points response per coordinate. The office and grid rarely change\n3. Round coordinates to four decimal places. More precision returns an error\n4. Don't add cache-busting query parameters. Unknown parameters return 400\n5. Back off about five seconds after a throttled request and reuse the last good response\n6. Fetch station observations within 7 days. Older ones aren't kept\n\n## Questions\n\n### Which is better for AI agents, Meteosource Weather MCP or NOAA National Weather Service API (api.weather.gov)?\n\nMeteosource Weather MCP scores 50.9 (D) on agent readiness against NOAA National Weather Service API (api.weather.gov)'s 48.4 (D), and leads in 4 of 7 scored categories. NOAA National Weather Service API (api.weather.gov) leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do Meteosource Weather MCP and NOAA National Weather Service API (api.weather.gov) need an API key?\n\nMeteosource Weather MCP needs an API key. NOAA National Weather Service API (api.weather.gov) needs no key.\n\n### Can an agent call Meteosource Weather MCP and NOAA National Weather Service API (api.weather.gov) without installing anything?\n\nYes. Meteosource Weather MCP has a hosted endpoint at https://mcp.meteosource.com/mcp and NOAA National Weather Service API (api.weather.gov) at https://api.weather.gov.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"meteosource-mcp\", \"b\": \"nws-api\"}`. From a terminal: `anchor compare meteosource-mcp nws-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meteosource-mcp.json and https://www.anchorterminal.com/api/v1/tools/nws-api.json\n\n## Other comparisons with Meteosource Weather MCP or NOAA National Weather Service API (api.weather.gov)\n\n- [AccuWeather Core Weather API + MCP vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/accuweather-api-vs-nws-api.md)\n- [Google Weather API (Maps Platform) vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/google-weather-api-vs-nws-api.md)\n- [Met Office Weather DataHub (Site Specific) vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/met-office-datahub-vs-nws-api.md)\n- [meteoblue Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteoblue-vs-nws-api.md)\n- [Meteomatics Weather API vs NOAA National Weather Service API (api.weather.gov)](https://www.anchorterminal.com/compare/meteomatics-vs-nws-api.md)\n- [NOAA National Weather Service API (api.weather.gov) vs OpenWeather One Call API](https://www.anchorterminal.com/compare/nws-api-vs-openweather-one-call.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Pirate Weather](https://www.anchorterminal.com/compare/nws-api-vs-pirate-weather.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Tomorrow.io Weather API](https://www.anchorterminal.com/compare/nws-api-vs-tomorrow-io.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- [NOAA National Weather Service API (api.weather.gov) vs The Weather Company Data APIs](https://www.anchorterminal.com/compare/nws-api-vs-weather-company.md)\n- [NOAA National Weather Service API (api.weather.gov) vs WeatherAPI.com](https://www.anchorterminal.com/compare/nws-api-vs-weatherapi-com.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Weatherbit API](https://www.anchorterminal.com/compare/nws-api-vs-weatherbit.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Xweather Weather API](https://www.anchorterminal.com/compare/nws-api-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 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- [NOAA National Weather Service API (api.weather.gov) vs Stormglass API](https://www.anchorterminal.com/compare/nws-api-vs-stormglass.md)\n- [Meteosource Weather MCP vs Open-Meteo](https://www.anchorterminal.com/compare/meteosource-mcp-vs-open-meteo.md)\n- [NOAA National Weather Service API (api.weather.gov) vs Open-Meteo](https://www.anchorterminal.com/compare/nws-api-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": "Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)", "url": "" } ], "description": "Meteosource Weather MCP scores 50.9 (D) to NOAA National Weather Service's 48.4 (D) for weather forecasts. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Meteosource Weather MCP D 50.9", "NOAA National Weather Service API (api.weather.gov) D 48.4", "scores" ], "h1": "Meteosource Weather MCP vs NOAA National Weather Service API (api.weather.gov)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/meteosource-mcp-vs-nws-api", "published": "2026-10-01", "section": "tools", "title": "Meteosource Weather MCP vs NOAA National Weather Service (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/meteosource-mcp-vs-nws-api" }, "tokens": { "markdown": 4800, "slim": 2530 }, "version": 1 }