Meteosource Weather MCP vs Stormglass 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.

Stormglass API 15

The latest dated announcement is the ERA5 blog post of 26 February 2026, 225 days before this check. The docs files carry a Last-Modified header of 29 June 2026, 102 days before, and the terms are dated 17 March 2026, so we scored the last visible change as within 180 days (10 of 30). No dated entry falls in the last 90 days (0 of 20). The blog announced new sources in May and September 2025 and twice in February 2026. Support is by email and comes with the Medium plan and higher, which we did not test (5 of 15). No official SDK was found (0 of 15). There is no public package or repository to assess (0 of 10).

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.

Stormglass API 40

No OpenAPI file or other machine-readable contract was found in the docs (0 of 25). llms.txt returns 404. The docs site is Docsify, so each of its eleven pages is also a plain Markdown file, which is how we read them (5 of 10). Each endpoint page states its purpose, and the weather page points to the historical endpoint for past data and explains the sg source. The sources page gives resolution, update frequency and forecast span per model (12 of 20). Parameter tables mark required fields and defaults, and datum lists its seven values, but no types or ranges are given (7 of 15). Examples in Python, curl and JavaScript with sample responses, and a table of seven error codes. The sample JSON has trailing commas, and the descriptions of the three secondary swell fields are swapped (10 of 15). The path is versioned as /v2 and 410 marks legacy resources. No changelog was found, only blog posts about new sources (6 of 15).

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.

Stormglass API 46

Closed service with one short terms page, dated 17 March 2026. The FAQ limits commercial use to Medium and higher. The terms set no rules on storing, caching or redistributing data and do not say what licence the customer receives (10 of 30). The privacy text is a few paragraphs inside the terms. It says data is kept as long as necessary and account data until deletion, with no period for request data, and no DPA was found (8 of 30). No deprecation policy was found. The terms let the company modify or terminate any service at any time and change content without notice, and the docs list 410 for retired resources (1 of 20). HubSpot is the only third party named, and no hosting location is given (3 of 20).

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.

Stormglass API 65

This is an API with no MCP server. params chooses the fields returned, source the models, and start and end the hours. The default on /weather/point is every source, so each field comes back once per model unless source is set (20 of 25). Time ranges, a bounding box for tide stations and a 10-day cap per historical call. Nothing is paginated (14 of 20). Seven status codes are documented, and the 403 body we saw was {"errors":{"key":"API key is invalid"}}. 402 for a spent quota is unusual, the FAQ names a different code, and no body is documented for any error (11 of 20). All ten endpoints are read-only GETs, safe to retry (15 of 20). lat, lng and params are the only required inputs and times default to today in UTC. No official SDK was found (5 of 15).

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.

Stormglass API 25

No x402, MPP or L402. The API's 402 means a spent quota (0). Plan prices are public without a login, in euros, with daily quotas and no per-call or overage price, 19, 49 and 129 euros a month (10 of 20). A free plan at 10 requests a day. The site says signup is always free. The signup form is drawn by script and we did not read it, so whether a card is asked for is not established, and the terms call the plan an evaluation not meant for indefinite use (15 of 20). A person signs up in a browser to get a key (0).