Skip to main content
Glama
Sign In
Dockerfile Check

Dockerfile Check

by arhancanli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Dockerfile Check

No user-submitted related servers found.

    Related Servers

    • Shipshape MCP server

      hybridforgelab
      A
      license
      A
      quality
      B
      maintenance
      Lets a coding agent lint a Dockerfile or Kubernetes manifest through the Shipshape API, returning an A–F grade, score, pass/fail status, and every finding with its line, fix, and reference. Catches issues like root in the final stage, unpinned base images, curl | sh, secrets in ENV/ARG, and Pod Security Standards, resources, and probes violations before handing work over.
      1
      MIT

    • dockerfile-audit-mcp

      tylerscomic-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to audit Dockerfiles for container-security anti-patterns, including missing USER, baked-in secrets, curl | sh / wget | bash, unpinned base images, and ADD with remote URLs. It parses Dockerfile structure to return risk levels and actionable fixes.
      MIT

    • layerlint-mcp

      xuange-hu
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a Dockerfile auditing engine to AI assistants, letting them scan a Dockerfile for the 32 deterministic layer-aware rules, print a stage/layer map showing what each layer adds or deletes, explain any rule's rationale and fix, and list available rules. Findings include file:line evidence so agents can surface and triage image-safety issues directly in Claude Code, Cursor, or Cline.
      MIT

    • Shipshape MCP Server

      Bytestay
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to lint Dockerfiles and Kubernetes manifests through the Shipshape API, returning an A–F grade, score, pass/fail status, and every finding with its line, fix, and reference. Uses the user's own marketplace key, reports remaining plan quota, and explains errors in plain language.
      1
      MIT

    • end-of-life-mcp

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Enables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.
      3
      1
      MIT
    • EVIDIQ Bastion

      EVIDIQ Bastionofficial

      evidiq
      A
      license
      Not graded
      quality
      B
      maintenance
      Audits infrastructure configurations (Dockerfiles, GitHub Actions, Kubernetes, Terraform/Compose) against 14 deterministic security rules, returning BLOCK/REVIEW/PASS verdicts and signing attestations. Helps agents verify deployment configs before applying them.
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation4/5

    check_dockerfile is clearly the Dockerfile linter while image_info is the image-reference inspector, so the core purposes are distinct. However, check_dockerfile also validates each base image against its registry (tag existence, digests, platforms, EOL), which overlaps with what image_info does, creating some potential for misselection on image-related queries.

    Naming Consistency4/5

    Both names use snake_case consistently, which is readable and predictable. The pattern is slightly uneven (verb_noun 'check_dockerfile' vs noun_noun 'image_info'), a minor deviation rather than a real inconsistency.

    Tool Count3/5

    Two tools is defensible for this narrow, focused domain (linting Dockerfiles plus inspecting image references). Still, it sits at the thin end and leaves little redundancy or granularity for users who only want one aspect checked.

    Completeness4/5

    The pair covers the stated purpose well: Dockerfile lint findings with lines and fixes, plus image tag/digest/platform/EOL data across major registries. Minor gaps remain, such as no autofix output or broader compose-file/context checks, but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources