Ext Ops Panel
Open dashboard
Comparison

reapx Docker containers - Hub images, tags and pulls vs Dockerhub

reapx Docker containers - Hub images, tags and pulls is an MCP server published by reapx.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-23. 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
Marketplacereapx Docker containers - Hub images, tags and pullsDockerhub
Official MCP Registry Listed, marked deprecated
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.3
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

reapx Docker containers - Hub images, tags and pulls vs Dockerhub
Factreapx Docker containers - Hub images, tags and pullsDockerhub
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-21
Where it runs (differs)Remote server (mcp.apify.com)Remote server (gateway.pipeworx.io/dockerhub/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.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)Responded 5 days ago, requires a keyResponded 5 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

reapx Docker containers - Hub images, tags and pulls

In its own words, on Official MCP Registry:

Scrape Docker Hub container images, tags, pulls and publisher metadata. Pay per row.

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

reapx Docker containers - Hub images, tags and pulls

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

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.

Both endpoints responded at the last daily 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: reapx Docker containers - Hub images, tags and pulls · What it can do: Dockerhub · Compare two other plugins

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