# Copernicus Cds

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

- name: io.github.pipeworx-io/copernicus-cds
- version: 0.1.1
- connection class: R0 (autonomous)
- trust: 97/100
- quality: –/100 (not scored)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fcopernicus-cds
- tools: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fcopernicus-cds/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "copernicus-cds": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/copernicus-cds/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-25d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality –/100 (not scored)

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: n/a (weight 30)

- n/a `tools.descriptions`, `tools.description_length`, `tools.schemas`, `tools.annotations`, `tools.directory_hints`, `tools.token_cost`, `tools.api_dump`: tool list unknown (behind auth, not probed, or empty)

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool list unknown

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: unknown
- tools last changed: 2026-10-19T06:54:31.453Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.pipeworx-io/copernicus-cds.svg)](https://protogrid.dev/servers/io.github.pipeworx-io/copernicus-cds)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `cds_submit_request` removed
  - 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 you poll on cds.climate.copernicus.eu.
- 2026-10-19 `cds_collection` removed
  - 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.
- 2026-10-19 `cds_collections` removed
  - 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.
- 2026-10-19 `forget` removed
  - Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
- 2026-10-19 `recall` removed
  - Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.
- 2026-10-19 `remember` removed
  - Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.
- 2026-10-19 `pipeworx_feedback` removed
  - Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
- 2026-10-19 `scan_competitor_ai_presence` removed
  - Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.
- 2026-10-19 `generate_llms_txt` removed
  - Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.
- 2026-10-19 `suggest_questions` removed
  - What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Full history: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fcopernicus-cds/changes

## Remotes

- https://gateway.pipeworx.io/copernicus-cds/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (0)

_none observed_