Skip to main content
Glama
GeniusTechnoMystic

docker-hub-mcp

by GeniusTechnoMystic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to docker-hub-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-dockerhub

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that wraps Docker Hub v2 API to enable querying public Docker Hub data (e.g., repositories, tags) with no authentication required.
      6 npm
      MIT

    • DockerHub MCP Server

      keshavjha123
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol (MCP) server that provides comprehensive DockerHub integration for AI assistants. This server enables AI assistants to search, analyze, and manage Docker images through standardized MCP tools.
      MIT

    • MCP OCI Registry Server

      cloudowski
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for querying OCI container registries. Provides tools and prompts for interacting with registries like Docker Hub, GHCR, and other OCI-compatible registries.
      2
      Apache 2.0

    • docker-helper-ai-mcp

      CSOAI-ORG
      A
      license
      Not graded
      quality
      B
      maintenance
      Docker Helper MCP server that provides tools for automating Docker tasks such as generating Dockerfiles, parsing docker-compose files, and optimizing images.
      11 npm
      MIT

    • npm-search-mcp

      zcag
      A
      license
      A
      quality
      D
      maintenance
      MCP server that searches npm packages and returns live registry data without an API key. Supports package search, detailed info, and side-by-side comparison of packages.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources