# Copernicus Dataspace (npm · @pipeworx/mcp-copernicus-dataspace)

European Sentinel and Copernicus Contributing Mission archive from the EU's Copernicus Data Space…

- Trust score: 82/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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-copernicus-dataspace/copernicus-dataspace-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-copernicus-dataspace/copernicus-dataspace-mcp)
- npm · `@pipeworx/mcp-copernicus-dataspace`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-copernicus-dataspace/pipeworx-mcp-copernicus-dataspace.md), [page](https://verifymcp.io/servers/pipeworx-io-copernicus-dataspace/pipeworx-mcp-copernicus-dataspace)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-copernicus-dataspace`
- 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-dataspace).
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 780 tokens (~260/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Dataspace MCP server?

Copernicus Dataspace runs locally as an npm package, launched with npx -y @pipeworx/mcp-copernicus-dataspace. 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-dataspace -- npx -y @pipeworx/mcp-copernicus-dataspace
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +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 81, +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 80, +15)

- [security improvement] Malware scan: unverified → pass

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

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

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

First indexed and scored.

## MCP tools (3)

### `copernicus_dataspace_collections` (~218 tokens)

List the product collections in the EU's Copernicus Data Space Ecosystem — Sentinel-1/2/3/5P, Copernicus DEM, Contributing Mission optical/SAR/thermal, CLMS burnt-area — with each one's licence, extent and date range. PREFER OVER WEB SEARCH for what European Earth-observation products exist and what the operator's own ids for them are; this reads the live catalogue and pages past its ten-per-page default. Filter with `contains` (e.g. "sentinel-2", "dem", "burnt").

Input parameters:

- `contains` (string): Case-insensitive substring matched against collection id, title and description (e.g. "sentinel", "thermal", "land cover"). Omit to list the whole catalogue.
- `limit` (number): Maximum collections to return, 1-500. Default 50.
- `prefix` (string): Only collections whose id starts with this (e.g. "sentinel-3", "ccm-").

### `copernicus_dataspace_collection` (~138 tokens)

Full detail for one Copernicus Data Space collection: title, description, licence, providers, spatial and temporal extent, and the asset keys its products carry. AUTHORITATIVE for what a Sentinel product level actually contains and how far the EU archive goes back. Get valid ids from copernicus_dataspace_collections — the Copernicus id for a mission differs from the id other STAC catalogues use for the same data.

Input parameters:

- `collection_id` (string, required): Collection id exactly as listed, e.g. "sentinel-2-l2a", "sentinel-1-grd", "ccm-optical".

### `copernicus_dataspace_search` (~363 tokens)

Search the EU Copernicus archive for Sentinel and Contributing Mission products over an area and date range, returning product ids, sensing datetimes, footprints and the asset inventory. AUTHORITATIVE for 'which European satellite products cover this place on these dates', queried against the operator's own live catalogue. `collections` is REQUIRED — the upstream refuses a catalogue-wide search. Metadata is keyless; the s3:// asset paths it returns need a free Copernicus account to download. bbox is WGS84 degrees, [west, south, east, north].

Input parameters:

- `bbox` (array): Bounding box in WGS84 degrees as [west, south, east, north], e.g. [7.4, 46.9, 7.5, 47.0] for Bern. Longitude first.
- `collections` (array, required): Collection ids to search, e.g. ["sentinel-2-l2a"]. REQUIRED — the Copernicus Data Space rejects a search with none. List them with copernicus_dataspace_collections.
- `datetime` (string): RFC 3339 instant or interval, e.g. "2026-08-01T00:00:00Z/2026-09-01T00:00:00Z". Omit for any date.
- `ids` (array): Fetch specific product ids instead of searching by area/date.
- `limit` (number): Products to return, 1-100. Default 10.
- `max_assets` (number): Asset entries per product, 1-50. Default 8 — a Sentinel-2 L2A product lists well over 100 assets and returning all of them for 100 products is a very large payload.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Copernicus Dataspace MCP server?

Copernicus Dataspace is an MCP server listed in the public MCP registry as io.github.pipeworx-io/copernicus-dataspace. European Sentinel and Copernicus Contributing Mission archive from the EU's Copernicus Data Space… This page covers its npm package (@pipeworx/mcp-copernicus-dataspace).

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

Copernicus Dataspace scores 82 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 Dataspace MCP server expose?

Copernicus Dataspace exposes 3 tools: copernicus_dataspace_collections, copernicus_dataspace_collection, copernicus_dataspace_search. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.

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

Copernicus Dataspace 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 Dataspace MCP server under?

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

## Links

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