Docker MCP Server vs io.github.mshegolev/harbor-registry-mcp
Docker MCP Server is an MCP server published by hypnosis. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.mshegolev/harbor-registry-mcp is an MCP server published by mshegolev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.1 Downloads/month (npm): 987 Downloads/week (npm): 265 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 238 Downloads/week (PyPI): 166 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 2.0.1 Downloads/month (npm): 987 Downloads/week (npm): 265 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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
| Fact | Docker MCP Server | io.github.mshegolev/harbor-registry-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@hypnosis/docker-mcp-server) | On your machine (harbor-registry-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | 4, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hypnosis/docker-mcp-server | github.com/mshegolev/harbor-registry-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Docker MCP Server
Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.
io.github.mshegolev/harbor-registry-mcp
Harbor Registry MCP — projects, repos, artifacts, storage reports, cleanup (with dry-run).
How to run each
Docker MCP Server As a local MCP server: npm package
claude mcp add --transport stdio docker-mcp-server -- npx -y @hypnosis/docker-mcp-server
io.github.mshegolev/harbor-registry-mcp As a local MCP server: PyPI package
claude mcp add --env "HARBOR_PASSWORD=<YOUR_HARBOR_PASSWORD>" --env "HARBOR_URL=<YOUR_HARBOR_URL>" --env "HARBOR_USERNAME=<YOUR_HARBOR_USERNAME>" --transport stdio harbor-registry-mcp -- uvx harbor-registry-mcp
Requires: HARBOR_PASSWORD (secret), HARBOR_URL, HARBOR_USERNAME
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Docker MCP Server asks for
DOCKER_MCP_ALLOW_SSH_FALLBACKDOCKER_MCP_PROFILES_FILEDOCKER_PROFILESLOG_LEVEL
Only io.github.mshegolev/harbor-registry-mcp asks for
HARBOR_PASSWORD (secret)HARBOR_SSL_VERIFYHARBOR_URLHARBOR_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Docker MCP Server · What it can do: io.github.mshegolev/harbor-registry-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.