Docker Hub MCP for image search, tags, manifests, repositories, and container supply-chain context.
Looking for more MCP servers? Browse the full MCP tools directory or explore more tools in DevOps.
Docker Hub MCP sits at the first link of the container supply chain, where an image name becomes a runtime artifact. An agent can search repositories, inspect tags and manifests, compare architectures, read metadata, and identify whether a deployment references a mutable tag or a digest-pinned image. The architectural truth is that latest is not a version — it is a moving pointer — and a successful pull says nothing about provenance, vulnerability status, or whether the image changed since yesterday. The server becomes valuable when it turns image discovery into evidence: repository owner, digest, platform, creation time, signature or attestation metadata, and scan state. The silent danger is tag confusion and namespace ambiguity; a public repository with a familiar name can be a typosquat, while a multi-architecture manifest can select a different digest on ARM and x86. Use read-only registry credentials, digest pinning, trusted namespaces, rate-limit awareness, and a policy gate before promoting any image to production. Docker Hub MCP is a supply-chain inspection layer, not an authorization to run arbitrary images.
Choose Docker Hub MCP when you want an MCP server focused on DevOps and need tighter integration with your existing tools.
Good fit
Use the following configuration as a starting point for Claude Desktop or any compatible MCP client, then replace placeholder credentials with your own values.
{
"mcpServers": {
"docker-hub": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/dockerhub"]
}
}
}These setup steps cover the typical installation flow for this MCP server.
Install or enable the Docker Hub MCP server through the Docker MCP Catalog, and authenticate only if private repositories or higher registry limits are required.
Configure trusted namespaces and use read-only registry access for search, manifest, and metadata inspection.
Pro-Tip: The fatal flaw 90% of developers commit is approving an image by tag alone, especially latest. Tags move, namespaces collide, and architecture-specific manifests resolve to different digests. Require repository owner, immutable digest, platform, scan status, and provenance metadata before allowing an image into a deployment or Dockerfile.
Check multi-architecture manifests separately for linux/amd64 and linux/arm64; the digest selected at runtime may differ.
Use registry rate limits and local caching deliberately; anonymous searches and autonomous loops can hit pull or API limits.
Verify with: inspect a trusted image tag, resolve its digest for two platforms, and compare creation and scan metadata before accepting it.
Common questions for Docker Hub MCP.
The silent failure is mutable-tag drift or platform resolution. The tag still exists and pulls successfully, but it now points to a different manifest or resolves to an architecture-specific digest. The engineering fix is to resolve and store the immutable digest per target platform, verify provenance and scan status, and deploy by digest rather than tag.
Docker Hub MCP inspects and discovers registry artifacts; Docker MCP Gateway runs MCP servers with container isolation and secret brokering. Use Hub for supply-chain evidence and Gateway for runtime containment — they solve different stages of the lifecycle.
Available scan metadata depends on the repository, plan, and server capabilities. Treat registry scan results as one signal and enforce your own image-scanning and signing policy in CI before deployment.
Anonymous and authenticated registry rate limits, regional connectivity, or manifest architecture mismatches can all cause failures. Authenticate where appropriate, cache approved images, and inspect the exact registry response and platform.
| Feature | Docker Hub MCP | Competitor |
|---|---|---|
| Artifact discovery | ✅ Repositories, tags, manifests, digests, and registry metadata | ❌ Runtime-only container tools see images after selection |
| Supply-chain evidence | ✅ Can ground image choices in owner, digest, platform, and scan metadata | ❌ Tag-based deployment hides artifact drift |
| Runtime isolation | ❌ Does not sandbox or run selected images | ✅ Docker Gateway isolates MCP server execution |
| Deployment authority | ❌ Inspection only by default | ✅ CI/CD systems can enforce promotion policies |