Meteosource Weather MCP vs Weatherbit API

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.

Weatherbit API 11

The latest dated API announcement on the blog is still 1 August 2025 on its RSS feed on 4 November, 460 days before this check. The help articles edited in 2026 and the June 2026 timestamps in the docs' sample responses record no change to the API, so they don't set recency (0 of 30). No dated changelog entry or release falls in the 90 days from 6 August (0 of 20). A public blog for API updates that has gone quiet, a help centre, and email support with a stated three business day response that we did not test (6 of 15). pyweatherbit 2.2.2 on PyPI dates from 14 February 2024 and is the only official SDK (3 of 15). Its repository, cloned on 4 November, has no CI and no commit since 13 February 2024 (2 of 10). 0 + 0 + 6 + 3 + 2 = 11.

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.

Weatherbit API 66

Graded as a hosted service. Status page at status.weatherbit.io on UptimeRobot. Its monitors and history load by script from /api/ paths that the status host's robots.txt disallows, so on 4 November we couldn't see which parts of the service it covers, and the 8 October reading of three API monitors came from the same disallowed path and no longer counts. The line is kept at 20 as awarded on 8 October, as sendblue's and visual-crossing's UptimeRobot pages are, until the 15 or 20 reading for such pages is settled (20). The 8 October incident reading came from that path too, so the line takes the no-readable-history score, a limit of our reading and not a finding against Weatherbit (5). Requests per day and per second are published for every plan, 50 and 1 on Free up to 2 million and 150 on Business, re-read on 4 November (15). 429 is documented for both limits, every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and the help centre says to slow down or retry. No Retry-After or backoff schedule was found. Every call is a GET (11 of 15). The pricing table lists 99.5 per cent uptime on paid plans, which the help centre calls best effort, with custom SLAs on request and no published credits (5 of 10). The v2.0 API is generally available (10). 20 + 5 + 15 + 11 + 5 + 10 = 66.

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.

Weatherbit API 63

Closed service with terms updated on 1 May 2025 that set out a commercial licence for paid plans and a Creative Commons non-commercial licence for the free plan. The terms say BY-NC-SA 4.0 and the pricing page links BY-NC 4.0. The Python SDK is MIT (15 of 30). The privacy policy, updated 26 December 2023, covers the API, lists what is logged (IP address, user agent, requested locations) and keeps request logs for no more than two weeks and account records for up to ten years. No DPA was found (17 of 30). No deprecation policy was found, and the terms let Weatherbit end access at any time without notice or reason, though they promise seven days' notice before a renewal when a paid subscription is ended without cause (2 of 20). Stripe and Google Analytics are named. Hosting is given as the United States and Canada, while the help centre says North America and Europe (8 of 20). The terms of 1 May 2025 were re-read on 4 November. 15 + 17 + 2 + 8 = 42.

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.

Weatherbit API 61

This is an API with no MCP server. days and hours cap forecast length and include adds minutely data, alerts or lightning only on request. There is no field selection, and a daily forecast row carries about 40 fields (14 of 25). Date ranges, units, lang and a one-month cap per historical call. No pagination is needed (13 of 20). Five status codes with a JSON error string and no machine-readable code. 204 with an empty body means no data, and 403 covers both a missing key and a plan without access (12 of 20). All 21 endpoints are read-only GETs, safe to retry (15 of 20). Only key and a location are required and units default to metric. One official SDK, pyweatherbit for Python, last released in February 2024 (7 of 15). 14 + 13 + 12 + 15 + 7 = 61.

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.

Weatherbit API 67

Swagger 2.0 at weatherbit.io/static/swagger.json, version 2.0.0, with 21 GET paths, 37 response models and bodies for 400, 403, 429 and 500. It declares no security definition and lists plain http as a scheme (23 of 25, per the 8 October check, not re-read on 4 November). No llms.txt, which still returned 404 on 4 November, and no Markdown docs found (0). Each endpoint page lists parameters, return fields with types and a quota estimate, and warns against station lookups, but says little on when to pick one endpoint over another (13 of 20). units and lang are enums, 31 enum parameters in all. Location is six optional parameters with none marked required, and include and days carry no constraints in the spec (11 of 15). Request examples in curl, Ruby, Node.js and Python, sample responses and a status table with example bodies. Errors are one free-text string (12 of 15). The path is versioned as /v2.0. The changelog is a blog whose latest API post is still dated 1 August 2025 on its RSS feed on 4 November (8 of 15). 23 + 0 + 13 + 11 + 12 + 8 = 67.