# Copernicus Cds (npm · @pipeworx/mcp-copernicus-cds)

The Copernicus Climate Data Store (C3S/ECMWF) catalogue — browse or search the ~140 published…

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 80/100, [markdown](https://verifymcp.io/servers/pipeworx-io-copernicus-cds/copernicus-cds-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-copernicus-cds/copernicus-cds-mcp)
- npm · `@pipeworx/mcp-copernicus-cds`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds.md), [page](https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-copernicus-cds`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-copernicus-cds).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 994 tokens (~198/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Copernicus Cds MCP server?

Copernicus Cds runs locally as an npm package, launched with npx -y @pipeworx/mcp-copernicus-cds. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-copernicus-cds -- npx -y @pipeworx/mcp-copernicus-cds
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-copernicus-cds": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-copernicus-cds"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-copernicus-cds": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-copernicus-cds"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-copernicus-cds -- npx -y @pipeworx/mcp-copernicus-cds
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-copernicus-cds": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-copernicus-cds"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-copernicus-cds --command npx --arg -y --arg @pipeworx/mcp-copernicus-cds
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-copernicus-cds:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-copernicus-cds"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-copernicus-cds": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-copernicus-cds"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-copernicus-cds -t stdio -c npx -a -y @pipeworx/mcp-copernicus-cds
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-copernicus-cds": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-copernicus-cds"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (5)

### `cds_collections` (~185 tokens)

List or keyword-search the Copernicus Climate Data Store catalogue — the ~140 published climate datasets (ERA5 reanalysis, CMIP6/CORDEX projections, satellite ECVs, seasonal forecasts, in-situ networks). Returns each collection id (pass it to cds_collection or cds_submit_request), title, and the temporal/spatial extent it covers. Keyless. AUTHORITATIVE for "which Copernicus/C3S dataset covers X" — the catalogue itself, not a description of it.

Input parameters:

- `limit` (number): Max collections to return (1-200, default 25).
- `offset` (number): Skip this many matches (default 0).
- `query` (string): Optional keyword filter, matched against collection id, title and description (e.g. "sea ice", "ERA5", "wildfire"). Omit to list everything.

### `cds_collection` (~145 tokens)

Full detail for ONE Copernicus Climate Data Store collection by id (e.g. "reanalysis-era5-single-levels"). Returns the STAC record — title, abstract, keywords, licence, temporal and bounding-box extent, documentation links — AND the request form: the variables, years, months, pressure levels, area and output formats the retrieval job will accept. Keyless. Call this before cds_submit_request to learn what the dataset actually accepts.

Input parameters:

- `collection_id` (string, required): Collection id from cds_collections, e.g. "reanalysis-era5-single-levels".
- `include_form` (boolean): Include the retrieval request form (the accepted inputs). Default true.

### `cds_submit_request` (~239 tokens)

Submit a data-retrieval job to the Copernicus Climate Data Store and return the job id and status. Requires your own free CDS Personal Access Token, passed as _apiKey. Use cds_collection first to learn the accepted inputs; CDS jobs are asynchronous — this returns immediately with a job id. Poll it with cds_job_status (same _apiKey) until it reads "successful", then collect the download link with cds_job_result.

Input parameters:

- `_apiKey` (string, required): Your own Copernicus CDS Personal Access Token (BYO). Get one free at cds.climate.copernicus.eu: create an ECMWF account, accept the dataset licences, then copy the Personal Access Token from your pro…
- `collection_id` (string, required): Collection id to retrieve from, e.g. "reanalysis-era5-single-levels".
- `inputs` (object, required): The request body inputs, exactly as the collection form declares them, e.g. {"variable":["2m_temperature"],"year":["2024"],"month":["01"],"day":["01"],"time":["12:00"],"data_format":"netcdf"}.

### `cds_job_status` (~176 tokens)

Check a Copernicus Climate Data Store retrieval job submitted with cds_submit_request. Returns its status (accepted, running, successful, failed or dismissed), timestamps and ready (true only when the data can be collected). Unknown or other-account job id returns found:false. Poll until ready is true, then call cds_job_result. Requires the same _apiKey (your own CDS Personal Access Token) that submitted the job.

Input parameters:

- `_apiKey` (string, required): Your own Copernicus CDS Personal Access Token (BYO), the one that submitted the job. Get one free at cds.climate.copernicus.eu: create an ECMWF account, accept the dataset licences, then copy the Per…
- `job_id` (string, required): The job id returned by cds_submit_request (job.jobID).

### `cds_job_result` (~190 tokens)

Collect the output of a Copernicus Climate Data Store retrieval job: when the job is successful returns the download URL (href) with file type, size in bytes and expiry where the service states them. If the job is not finished it does NOT return an empty result: it returns ready:false with the current status and tells you to poll cds_job_status. A failed job returns its failure reason. Unknown job id returns found:false. Requires the same _apiKey that submitted the job.

Input parameters:

- `_apiKey` (string, required): Your own Copernicus CDS Personal Access Token (BYO), the one that submitted the job. Get one free at cds.climate.copernicus.eu: create an ECMWF account, accept the dataset licences, then copy the Per…
- `job_id` (string, required): The job id returned by cds_submit_request (job.jobID).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 66
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Copernicus Cds MCP server?

Copernicus Cds is an MCP server listed in the public MCP registry as io.github.pipeworx-io/copernicus-cds. The Copernicus Climate Data Store (C3S/ECMWF) catalogue, browse or search the ~140 published… This page covers its npm package (@pipeworx/mcp-copernicus-cds).

### Is the Copernicus Cds MCP server safe to use?

Copernicus Cds scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Copernicus Cds MCP server expose?

Copernicus Cds exposes 5 tools: cds_collections, cds_collection, cds_submit_request, cds_job_status, cds_job_result. Their descriptions and schemas cost roughly 935 tokens of context every time the server is loaded.

### Is the Copernicus Cds MCP server still maintained?

Copernicus Cds is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Copernicus Cds MCP server under?

Copernicus Cds declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Copernicus Cds MCP server?

VerifyMCP ran 16 checks on Copernicus Cds, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-copernicus-cds
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-copernicus-cds
- Repository: https://github.com/pipeworx-io/mcp-copernicus-cds
- Website: https://pipeworx.io/packs/copernicus-cds
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-copernicus-cds/pipeworx-mcp-copernicus-cds