Remote MCP · Endpoint

Copernicus Dataspace MCP server

No. Copernicus Dataspace answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://gateway.pipeworx.io/copernicus-dataspace/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/copernicus-dataspace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
European Sentinel and Copernicus Contributing Mission archive from the EU's Copernicus Data Space…
Listing
From the official MCP registry (active).
Recent checks of Copernicus Dataspace
CheckedResultHandshake
52 minutes agoHandshake completed49 ms
3 days agoHandshake completed59 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed72 ms
15 days agoHandshake completed145 ms
15 days agoHandshake completed69 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed115 ms
18 days agoHandshake completed95 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed104 ms
25 days agoHandshake completed276 ms
27 days agoHandshake completed251 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Copernicus Dataspace and makes no claim about it beyond what these checks measured.