Ext Ops Panel
Open dashboard
Comparison

SkyKick MCP vs Copernicus Dataspace

SkyKick MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Copernicus Dataspace is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSkyKick MCPCopernicus Dataspace
Official MCP Registry Listed
Version: 0.1.10
Forks (GitHub): 17
Stars (GitHub): 74
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

SkyKick MCP vs Copernicus Dataspace
FactSkyKick MCPCopernicus Dataspace
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)74 (better)0 (worse)
Forks (GitHub) (differs)17 (better)0 (worse)
Last release (differs)2026-11-11 (better)2026-10-31 (worse)
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/skykick-v0.1.10/skykick-mcp.mcpb)Remote server (gateway.pipeworx.io/copernicus-dataspace/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 31, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/servosity/msp-skillsgithub.com/pipeworx-io/mcp-copernicus-dataspace
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

SkyKick MCP

In its own words, on Official MCP Registry:

Fleet backup posture, stale snapshots, and coverage gaps for SkyKick Cloud Backup.

Copernicus Dataspace

In its own words, on Official MCP Registry:

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

How to run each

SkyKick MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install skykick@msp-skills

Requires: SKYKICK_CLIENT_ID (secret), SKYKICK_CLIENT_SECRET (secret), SKYKICK_OAUTH_SCOPE (secret)

Copernicus Dataspace As a remote MCP server

Claude Code
claude mcp add --transport http copernicus-dataspace https://gateway.pipeworx.io/copernicus-dataspace/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Copernicus Dataspace has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of SkyKick MCP nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Only SkyKick MCP asks for

  • SKYKICK_BASE_URL
  • SKYKICK_CLIENT_ID (secret)
  • SKYKICK_CLIENT_SECRET (secret)
  • SKYKICK_NO_CONFIG_WRITE
  • SKYKICK_OAUTH_SCOPE (secret)
  • SKYKICK_TOKEN_URL

Only Copernicus Dataspace asks for

  • PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: SkyKick MCP · What it can do: Copernicus Dataspace · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built