docker-hub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_image_statsA | Fetch metadata for a single Docker Hub image. Accepts both 'library/nginx' and 'nginx' (auto-prepends 'library/') formats. Returns pulls, stars, description, official/verified status, last updated. |
| search_imagesA | Search Docker Hub images by keyword. Returns results with name, namespace, description, pull_count, star_count, is_official, is_automated, and last_updated. |
| batch_image_statsA | Batch lookup metadata for up to 100 Docker Hub images in parallel. Pass a list of image names (e.g. ['nginx', 'python', 'grafana/grafana']). Returns a summary table with pulls, stars, and status for each. |
| get_publisher_imagesA | List all images for a given publisher/namespace on Docker Hub. Useful for auditing an organisation's image catalog. Defaults to 100 results, max 500. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: search by keyword, fetch metadata for a single image, fetch metadata for multiple images in batch, and list images by publisher. There is no practical overlap that would confuse an agent.
Three tools follow a verb_noun pattern (search_images, get_image_stats, get_publisher_images), but batch_image_stats deviates by starting with an adjective rather than a verb. The naming is mostly consistent and readable, with one minor irregularity.
With 4 tools covering search, single lookup, batch lookup, and publisher listing, the count falls well within the ideal 3-15 range. Each tool serves a practical need without redundancy.
The tool set covers core image read operations, but lacks common features like listing image tags or getting detailed manifest information. Agents can work around these gaps, but they are notable for a Docker Hub service.