Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dynamical.org Weather & Climate Catalog

REMOTE · MCP.DYNAMICAL.ORG · SCANNED SEP 27

Search dynamical.org's open STAC catalog of weather & climate datasets (GFS, ECMWF, HRRR).

0 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1001 tokens (~250/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the dynamical.org Weather & Climate Catalog MCP server?

dynamical.org Weather & Climate Catalog is a hosted endpoint at https://mcp.dynamical.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.dynamical.org

# add to Claude Code
claude mcp add --transport http dynamical-org-mcp 'https://mcp.dynamical.org/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dynamical-org-mcp": {
      "url": "https://mcp.dynamical.org/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dynamical-org-mcp": {
      "type": "http",
      "url": "https://mcp.dynamical.org/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dynamical-org-mcp]
url = "https://mcp.dynamical.org/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dynamical-org-mcp": {
      "type": "remote",
      "url": "https://mcp.dynamical.org/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dynamical-org-mcp --url 'https://mcp.dynamical.org/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dynamical-org-mcp:
    url: "https://mcp.dynamical.org/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dynamical-org-mcp": {
      "Transport": "http",
      "Url": "https://mcp.dynamical.org/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dynamical-org-mcp -t streamable-http -u 'https://mcp.dynamical.org/mcp'
// mcp.json
{
  "mcpServers": {
    "dynamical-org-mcp": {
      "type": "http",
      "url": "https://mcp.dynamical.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 27 Sept 2026 · Probed https://mcp.dynamical.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dynamical.org CN=WE1,O=Google Trust Services,C=US 4 Aug 2026 2 Nov 2026 ECDSA 256 ECDSA-SHA256 90a58c4d5a085a7f13026cfc0d08122b
SANs: dynamical.org, *.dynamical.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dynamical.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
dynamical.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'none'; frame-ancestors 'none'

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dynamical.org/mcp Verified 200
http (plaintext) http://mcp.dynamical.org/mcp HTTPS enforced 308 https://mcp.dynamical.org/mcp
MCP tools · 4 exposed · ~935 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_access_pattern ~259

Get the storage URI and working code for opening a dynamical.org dataset's data. dynamical.org publishes a Python package, `dynamical-catalog`, that reads the STAC catalog itself to resolve and open a dataset -- it's the recommended access pattern because it can't go stale even if the underlying storage format or location changes. This tool also returns the dataset's low-level storage details (from the STAC asset, fetched live) and a lower-level xarray/fsspec snippet for callers who need direct access instead of the wrapper package. Args: collection_id: A STAC collection id, e.g. "noaa-gfs-forecast". Use search_catalog to discover ids. Returns: A dict with the recommended `dynamical_catalog.open(...)` snippet, a `worked_example` pulled from the collection's own STAC metadata when one is published, the raw asset URI/type/storage options, and a generated low-level open snippet (icechunk/zarr/geoparquet, chosen from the asset's declared type). Raises ValueError (listing valid ids) if collection_id is unknown.

NameTypeReqDescription
collection_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_dataset_info ~210

Get documentation, spatial/time resolution, domain, and update cadence for one dynamical.org dataset. dynamical.org/catalog is itself rendered from this same STAC catalog, so this tool fetches the collection document live (short TTL cache) rather than relying on anything baked into this server -- it's always as fresh as the STAC catalog itself. Args: collection_id: A STAC collection id, e.g. "noaa-gfs-forecast", "noaa-hrrr-analysis", or "ecmwf-aifs-ens-forecast". Use search_catalog to discover ids. Returns: A dict with title/model name, prose descriptions, spatial and time domain/resolution, forecast range (for forecast datasets), license and attribution, the dataset's variables, and links to its docs page and example notebooks. Raises ValueError (listing valid ids) if collection_id is unknown.

NameTypeReqDescription
collection_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_recent_runs ~227

Check run freshness and arrival status for a dynamical.org forecast dataset, from the same public feed status.dynamical.org's dashboard polls. Only forecast collections are pipeline-monitored today (analysis collections like noaa-gfs-analysis or noaa-mrms-conus-analysis-hourly aren't yet tracked by this feed). Args: collection_id: A STAC collection id, e.g. "noaa-gfs-forecast". limit: Maximum number of recent runs to return, most recent first (default 10). Returns: A dict with the overall pipeline `sla_status`, this product's cadence and next expected init/completion time, typical latency stats, and up to `limit` recent runs (`init_time`, `status`, `completion_pct`, `on_timedness`, arrival/latency timestamps). If collection_id isn't pipeline-monitored, returns `monitored`: False plus the list of collection ids that are.

NameTypeReqDescription
collection_idstringyes–
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

search_catalog ~239

Search dynamical.org's STAC catalog of cloud-optimized weather and climate datasets. Matches against each dataset's model name, description, spatial/time domain and resolution, forecast range, and variable names -- so a query can be a model ("GFS"), a variable ("precipitation", "temperature_2m"), a region ("continental US", "global"), or a resolution ("3km", "0.25 degree"). Results are ranked by number of matching terms. Args: query: Free-text search terms, e.g. "hourly precipitation CONUS" or "ECMWF ensemble forecast". limit: Maximum number of results to return (default 5). Returns: {"query": ..., "results": [{"collection_id", "title", "model_name", "description_summary", "spatial_domain", "spatial_resolution", "matched_variables", "score"}, ...]}, most relevant first. Pass a result's collection_id to get_dataset_info, get_access_pattern, or list_recent_runs.

NameTypeReqDescription
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the dynamical.org Weather & Climate Catalog MCP server?

dynamical.org Weather & Climate Catalog is an MCP server listed in the public MCP registry as io.github.dynamical-org/mcp. Search dynamical.org's open STAC catalog of weather & climate datasets (GFS, ECMWF, HRRR). This page covers its hosted endpoint (https://mcp.dynamical.org/mcp).

Is the dynamical.org Weather & Climate Catalog MCP server safe to use?

dynamical.org Weather & Climate Catalog scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the dynamical.org Weather & Climate Catalog MCP server expose?

dynamical.org Weather & Climate Catalog exposes 4 tools: get_access_pattern, get_dataset_info, list_recent_runs, search_catalog. Their descriptions and schemas cost roughly 935 tokens of context every time the server is loaded.

Does the dynamical.org Weather & Climate Catalog MCP server require authentication?

No. We connected to dynamical.org Weather & Climate Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dynamical.org Weather & Climate Catalog MCP server still maintained?

dynamical.org Weather & Climate Catalog is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.