Skip to main content
Glama
cgfm

dockhand-readonly-mcp

by cgfm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to dockhand-readonly-mcp

No user-submitted related servers found.

    Related Servers

    • dockhand-mcp

      craibo
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP sidecar server that exposes Dockhand's container, image, volume, network, and stack management as MCP tools over Streamable HTTP, enabling MCP clients to manage Docker resources through Dockhand's REST API.
      1
      MIT

    • dockhand-mcp

      tyler-rich
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to inspect and operate Docker environments managed by DockHand via a security-first, profile-gated subset of DockHand's REST API, with redacted output and human approval for destructive actions.
      Apache 2.0

    • mcp-dockhand

      t1nk333r
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing the Dockhand API as MCP tools. Enables AI assistants to manage Docker infrastructure including containers, stacks, images, networks, and volumes across multiple hosts.
      MIT

    • runtime-inspector-mcp

      ludi-uni
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT

    • mcp-portainer-lite

      Cuti27
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight MCP server for Portainer CE, focused on Docker Swarm environments with read-only tools by default and optional mutations.
      MIT

    • redmine-mcp

      AndreaCadonna
      F
      license
      A
      quality
      B
      maintenance
      Provides read-only MCP tools over stdio for interacting with a Redmine instance, enabling users to list and retrieve projects, issues, queries, wiki pages, and other Redmine resources via the REST API.
      35
      -
    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 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: health check, list environments, list containers, get one container, list networks, get one network, list stacks, and aggregate overview. The list vs. get pairing for containers and networks prevents confusion, and the overview and health tools are uniquely scoped.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_*, get_*, get_*_summary). The outlier is dockhand_health, which reads as a noun phrase rather than a verb-based action, but it is still understandable and does not break the overall pattern significantly.

    Tool Count5/5

    With 8 tools, this server is well-scoped for a read-only Docker inspection and monitoring service. Each tool covers a necessary facet (environments, containers, networks, stacks, health, and overview) without redundancy or bloat.

    Completeness4/5

    The server covers the main read-only monitoring operations: listing and summarizing containers and networks, listing stacks and environments, plus a health check and runtime overview. A get_stack_summary or get_environment_summary could be expected, but their absence seems intentional for security/sanitization reasons, and the core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources