Docker MCP Server
PYPI · DOCKER-MCP-SERVER · 3 COMPONENTS
Manage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI.
Last scanned (2 hours ago)
Scores higher than 29% of PyPI servers
Deprecated
This server is marked deprecated in the MCP registry.
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. How we score → Why this is hard to score →
Supply Chain Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects cryptography 48.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to GavinLucas/docker-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/docker-mcp-server@2.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GavinLucas/docker-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GavinLucas/docker-mcp/.github/workflows/publish.yaml@refs/tags/v2.1.1 |
| Rekor log index | 2113995176 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fcd54b4536e19d43e81c0c4e708d6764b28a01b0318bb7db54c4923125ed5826 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the Docker MCP Server server?
Docker MCP Server runs locally as a PyPI package, launched with uvx docker-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · docker-mcp-server
claude mcp add gavinlucas-docker-mcp-server -- uvx docker-mcp-server
What is the Docker MCP Server server?
Docker MCP Server is listed in the public MCP registry as io.github.GavinLucas/docker-mcp-server. Manage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI. This page covers its PyPI package (docker-mcp-server).
Is the Docker MCP Server server safe to use?
Docker MCP Server scores 39 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. 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.
Is the Docker MCP Server server still maintained?
Docker MCP Server is marked deprecated 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 Docker MCP Server server under?
Docker MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.