Ext Ops Panel
Open dashboard
Comparison

docker-image-scan vs Dockerhub

docker-image-scan is a plugin bundle for AI coding tools published by igor-koricanac. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Dockerhub 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-10-28. 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
Marketplacedocker-image-scanDockerhub
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
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

docker-image-scan vs Dockerhub
Factdocker-image-scanDockerhub
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-25
Where it runs (differs)Installs as a plugin bundleRemote server (gateway.pipeworx.io/dockerhub/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/igor-koricanac/claude-image-scangithub.com/pipeworx-io/mcp-dockerhub
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days 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

docker-image-scan

In its own words, on Claude Code: claude-plugins-community:

Build a container image from a Dockerfile, scan it for security vulnerabilities with Trivy, and auto-clean up. Uses Docker or Podman. No local Trivy install needed - runs Trivy as a container.

Dockerhub

In its own words, on Official MCP Registry:

Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)

How to run each

docker-image-scan As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install docker-image-scan@claude-community

Dockerhub As a remote MCP server

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

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

Only Dockerhub has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: docker-image-scan · What it can do: Dockerhub · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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