Is the Gribstream MCP server down?

mcp-registry/com.gribstream/mcp · v1.2.0

Also listed as glama/gribstream/gribstream-mcp

healthy
Last checked 2026-10-22 03:37 UTC · handshake 253ms

As of 2026-10-22 03:37 UTC, the Gribstream MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
4,231
outages (90d)
3
tools
12

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

Install Gribstream MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http gribstream-mcp-server https://gribstream.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "gribstream-mcp-server": {
      "type": "http",
      "url": "https://gribstream.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (88/100)

B (88/100): 0 error(s), 3 warning(s) across 12 tool(s); ~12,228 tokens of tool definitions.
Scores higher than 66% of 15,538 MCP servers Glimind has audited.
Its tool list costs an agent ~12,228 tokens per session — more than 85% of servers.
88 → 88 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions84
Safety hints83
Token cost69
Client compatibility100
Protocol100
Reliability100
Stability76

What to fix (4)

5 tool definition(s) exceed ~1,200 tokens each (largest: gribstream_query_timeseries, ~2,476).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~7,556 tokens every session. How to fix →

Tools: gribstream_query_timeseries, gribstream_query_runs, gribstream_build_timeseries_request, gribstream_build_runs_request, gribstream_validate_request · saves ~7,556 tokens/session

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: gribstream_list_datasets

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: gribstream_build_runs_request

In the last 30 days: 0 tool(s) removed and 6 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.gribstream/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.gribstream/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gribstream%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.gribstream%2Fmcp?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.gribstream%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gribstream%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gribstream%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.gribstream%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dd5e22cf1221c689…, first seen 2026-10-17, included at leaf 14575 of 43,310. Version history · verify what your client received.

Tools (12)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Gribstream MCP server down right now?

As of 2026-10-22 03:37 UTC, the Gribstream MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Gribstream MCP server provide?

Gribstream MCP server advertises 12 tools, including gribstream_build_runs_request, gribstream_build_timeseries_request, gribstream_get_dataset, gribstream_get_expression_reference, gribstream_get_parameter.

How do I install Gribstream MCP server?

Point your MCP client at this streamable-http endpoint: https://gribstream.com/mcp

Is the Gribstream MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Gribstream MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve