mcpbeat Sign in

GribStream Weather MCP Server

by gribstream Your server? Claim it
answering

GribStream Weather MCP is answering right now. Last checked 9 min ago. It exposes 12 tools. Last commit 18 Aug 2026.

NOAA and ECMWF weather forecast MCP for discovery, validation, and GribStream OAuth queries.

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
412 ms
Response time
average over 24h
0
Stars
last commit 18 Aug 2026

What changed 54

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

18 Aug 5 tools changed the parameters they ask for7 times that day gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 2 more
18 Aug 5 tool descriptions were rewritten7 times that day gribstream_get_parameter, gribstream_list_shared_parameters, gribstream_query_runs and 2 more
18 Aug a tool changed version2 times that day
17 Aug 5 tools changed the parameters they ask for gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 2 more
17 Aug 2 tool descriptions were rewritten gribstream_query_runs, gribstream_query_timeseries
16 Aug 4 tools changed the parameters they ask for gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 1 more
16 Aug 2 tool descriptions were rewritten gribstream_query_runs, gribstream_query_timeseries
15 Aug 5 tools changed the parameters they ask for10 times that day gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 2 more
13 Aug 5 tools changed the parameters they ask for gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 2 more
12 Aug 4 tool descriptions were rewritten gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_query_runs and 1 more
and 16 more, back to 11 August 2026

Nothing serious here today

Today is the operative word: we check GribStream Weather MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mcp --transport http https://gribstream.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://gribstream.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://gribstream.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://gribstream.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://gribstream.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

gribstream
gribstream_build_runs_request
NO AUTH / PUBLIC / READ-ONLY. Builds and validates a copy-pasteable authenticated /api/v2/{dataset}/runs HTTP request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use gribstream_query_runs when the user asks for actual model-run forecast data or CSV/JSON/NDJSON/Parquet data. Generated direct API requests include Accept-Encoding: gzip, and generated curl commands use --compressed so large responses can be transferred compressed when the client supports it. The request body must use exact selectors discovered from the catalog or shared-parameter tools, with coordinates in request.coordinates and selectors in request.variables.
gribstream_build_timeseries_request
NO AUTH / PUBLIC / READ-ONLY. Builds and validates a copy-pasteable authenticated /api/v2/{dataset}/timeseries HTTP request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use gribstream_query_timeseries when the user asks for actual weather values or CSV/JSON/NDJSON/Parquet data. Generated direct API requests include Accept-Encoding: gzip, and generated curl commands use --compressed so large responses can be transferred compressed when the client supports it. Do not include request.asOf unless the user explicitly wants backtesting, time travel, or a historical model-run cutoff. The request body must use exact selectors discovered from the catalog or shared-parameter tools, with coordinates in request.coordinates and selectors in request.variables.
gribstream_get_dataset
NO AUTH / PUBLIC / READ-ONLY. Gets full public metadata for one dataset code, including archive coverage, cadence, tags, source links, and members. This tool does not query weather values and cannot return forecast data.
gribstream_get_expression_reference
NO AUTH / PUBLIC / READ-ONLY. Gets the GribStream expression language reference, including github.com/expr-lang/expr syntax guidance, alias rules, examples, and the full exported func.* math function list. This tool does not query weather values and cannot return forecast data.
gribstream_get_parameter
NO AUTH / PUBLIC / READ-ONLY. Gets detailed metadata and exact selector variations for one already-known dataset-native parameter code. Parameter codes are case-sensitive. For a common natural-language concept such as 2 metre temperature, use gribstream_resolve_shared_parameter before guessing a native code. This tool does not query weather values and cannot return forecast data.
gribstream_list_datasets
NO AUTH / PUBLIC / READ-ONLY. Lists public GribStream datasets and metadata. This tool does not query weather values and cannot return forecast data. Supports catalog filters such as code, family, tag, and is_ensemble.
gribstream_list_parameters
NO AUTH / PUBLIC / READ-ONLY. Lists parameter summaries for one dataset. Use this before selecting exact case-sensitive parameter codes. This tool does not query weather values and cannot return forecast data.
gribstream_list_shared_parameters
NO AUTH / PUBLIC / READ-ONLY. Lists normalized shared parameter presets that can map one logical signal across datasets. Use this only when the shared parameter code is uncertain; when a common code such as temperature_2m is already clear, call gribstream_resolve_shared_parameter directly. This tool does not query weather values and cannot return forecast data.
gribstream_query_runs
AUTH REQUIRED / DATA QUERY. Executes an authenticated /api/v2/{dataset}/runs request and returns actual weather/forecast data values across model runs. Use this tool, not the NO AUTH request-building or metadata tools, when the user asks to fetch, retrieve, download, return, or analyze model-run history, forecast aging, changing forecasts, CSV/JSON/NDJSON/Parquet data, plots, or analysis. Defaults to inline CSV for compatibility; use URL delivery for dense grids and large tabular results. Time ranges are half-open: the start is inclusive and the end is exclusive. The start must be earlier than the end; equal bounds select no times. Use timesList for one exact valid time on /timeseries or one exact model run time on /runs. When a live query returns a resource_link, the exact signed HTTPS URL is the result: download it directly once with an available HTTPS or file-download capability, without an API token. This consumes the selected GribStream MCP result; it is not a direct GribStream API call or a connector bypass. Do not look for an MCP resources/read tool, and do not repeat the query merely to obtain the file bytes. If the client reports that network or allowlist policy blocks the returned resource_link, do not retry URL delivery. For CSV, JSON, or NDJSON whose reported size is at most 10000000 bytes, retry the same request at most once with delivery=inline. Parquet cannot use inline delivery. If the artifact is larger, reduce the request using the documented split order before one inline CSV retry. For dense grids or large tabular results, use delivery=url so MCP returns a short-lived signed HTTPS resource link instead of putting the full dataset into tool output. Prefer application/vnd.apache.parquet only when a compatible Parquet reader is already known to be available. If reader availability is unknown, do not spend tool calls probing or installing packages; use text/csv with delivery=url immediately. Use one grid request, process the downloaded file locally, and never print or serialize the full file into chat or tool output. Do not install a dependency or write a Parquet parser solely for one result. When a real API request limit requires splitting, split by time range first, split variables second, and split coordinates/grid/space last; spatial tiling creates the most extra work. Response rows are unsorted; sort by location fields, forecasted_at, and forecasted_time before plotting, building time series, or checking for gaps. The request body must use request.coordinates and request.variables; do not use location, coord, coords, parameters, parameter, or variable as replacement field names.
gribstream_query_timeseries
AUTH REQUIRED / DATA QUERY. Executes an authenticated /api/v2/{dataset}/timeseries request and returns actual weather/forecast data values. Use this tool, not the NO AUTH request-building or metadata tools, when the user asks to fetch, retrieve, download, return, or analyze weather values, CSV/JSON/NDJSON/Parquet data, plots, heatmaps, or best-available values by valid time. Defaults to inline CSV for compatibility; use URL delivery for dense grids and large tabular results. Time ranges are half-open: the start is inclusive and the end is exclusive. The start must be earlier than the end; equal bounds select no times. Use timesList for one exact valid time on /timeseries or one exact model run time on /runs. When a live query returns a resource_link, the exact signed HTTPS URL is the result: download it directly once with an available HTTPS or file-download capability, without an API token. This consumes the selected GribStream MCP result; it is not a direct GribStream API call or a connector bypass. Do not look for an MCP resources/read tool, and do not repeat the query merely to obtain the file bytes. If the client reports that network or allowlist policy blocks the returned resource_link, do not retry URL delivery. For CSV, JSON, or NDJSON whose reported size is at most 10000000 bytes, retry the same request at most once with delivery=inline. Parquet cannot use inline delivery. If the artifact is larger, reduce the request using the documented split order before one inline CSV retry. For dense grids or large tabular results, use delivery=url so MCP returns a short-lived signed HTTPS resource link instead of putting the full dataset into tool output. Prefer application/vnd.apache.parquet only when a compatible Parquet reader is already known to be available. If reader availability is unknown, do not spend tool calls probing or installing packages; use text/csv with delivery=url immediately. Use one grid request, process the downloaded file locally, and never print or serialize the full file into chat or tool output. Do not install a dependency or write a Parquet parser solely for one result. When a real API request limit requires splitting, split by time range first, split variables second, and split coordinates/grid/space last; spatial tiling creates the most extra work. Do not include request.asOf unless the user explicitly wants backtesting, time travel, or a historical model-run cutoff. Response rows are unsorted; sort by location fields and forecasted_time before plotting, building time series, or checking for gaps. The request body must use request.coordinates and request.variables; do not use location, coord, coords, parameters, parameter, or variable as replacement field names.
gribstream_resolve_shared_parameter
NO AUTH / PUBLIC / READ-ONLY. Resolves one shared parameter preset for a dataset, returning native variables and expressions to use in /timeseries or /runs request bodies. Use this first for common natural-language concepts such as 2 metre temperature or 10 metre wind instead of guessing dataset-native codes such as TMP. This tool does not execute the request, query weather values, or return forecast data.
gribstream_validate_request
NO AUTH / PUBLIC / READ-ONLY. Validates the basic shape, exact selector tuples, and expression syntax of a proposed GribStream /timeseries or /runs request without sending it. This tool does not execute the request, query weather values, or return forecast data. Use this before returning any hand-edited curl or when changing a request from one dataset to another.

Endpoints

URLTransportStateLatencyChecked
https://gribstream.com/mcp streamable-http answering 409 ms 9 min ago

Alternatives to GribStream Weather MCP

same job, measured the same way
Weather for Grown Ups
by janhelcl

Operational NWP, ensembles, AI weather models, regional forecasts, history, and verification.

135 installs/wk local only
Weather
by eudoroolivares2016

An MCP server for weather information updating this value now.

38 installs/wk local only
Smarter Weather
by smarterweather

Smarter Weather MCP: forecasts, alerts, outlooks, observations, AQI, grids, and map imagery.

47 installs/wk 31 tools answering
Xweather Weather MCP
by xweather

Hosted MCP server for Xweather weather data: conditions, forecasts, alerts, and more.

answering
AEMET
by mmillan76

MCP server exposing AEMET (Spanish weather agency) forecasts, station data and warnings.

29 installs/wk local only
NordicMCP — Weather
by nordicmcp

Hosted Weather MCP server (Open-Meteo): current, forecast, and historical weather by location.

answering
Weather
by dingw1982

An MCP server for weather information.

54 installs/wk local only
Weather
by alexdemichieli

An MCP server for weather information.

38 installs/wk local only

GribStream Weather MCP — questions

Answers built from our own checks of this server.

What can GribStream Weather MCP do?
It exposes 12 tools, read directly from the server on our last check. Among them: gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_get_dataset, gribstream_get_expression_reference, gribstream_get_parameter, gribstream_list_datasets and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is GribStream Weather MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 412 ms. The bar chart above shows every period we have measured.
How do I connect GribStream Weather MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does GribStream Weather MCP need an API key?
No. GribStream Weather MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GribStream Weather MCP?
It answers our handshake in 412 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is GribStream Weather MCP open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.