Dockerfile Lint
OCI · GHCR.IO/BASITALISANDHU/MCP-DOCKERFILE-LINT
Lint Dockerfiles for root users, latest tags, secrets in ENV or ARG, missing HEALTHCHECK and more.
Available components
Last scanned (1 hour ago)
Scores higher than 78% of OCI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 633 tokens (~211/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 14 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 83 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 13 Oct 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 12 Oct 26 0
- Package version: 0.1.1 → 0.2.0 functional
- 7 Oct 26 20
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-dockerfile-lint@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | basitalisandhu/dev-mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1 |
| Rekor log index | 3244679586 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:f06de909f9c17281090fae84dbd2ca427e6ea101146077a0a8dab5c05608a1ab |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_rule Explain a lint rule ~144
Describe one lint rule: its default severity, what it detects and how to fix it. Rules: root-user, latest-tag, unpinned-digest, secret-in-env, secret-in-arg, secret-literal, no-healthcheck, apt-no-cleanup, apt-no-recommends, apt-upgrade, apk-no-cache, pip-no-cache, add-for-copy, add-remote, curl-pipe-shell, sudo, workdir-relative, multiple-cmd, shell-form-cmd, expose-ssh, maintainer-deprecated, copy-whole-context, copy-chown-missing, empty-dockerfile, from-missing.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | – |
No output schema declared.
No examples provided.
lint_dockerfile Lint a Dockerfile ~224
Parse a Dockerfile (comments, escape directive, line continuations, heredocs, multi-stage builds) and return findings sorted by severity with line numbers and fixes. Checks: final stage running as root, base images without a tag or with :latest, images without a digest, credential-like names in ENV or ARG, credential literals in RUN, missing HEALTHCHECK, apt-get install without list cleanup or --no-install-recommends, apt-get upgrade, apk add without --no-cache, pip without --no-cache-dir, ADD for plain files or remote URLs, curl piped to a shell, sudo, relative WORKDIR, repeated CMD or ENTRYPOINT, shell-form CMD, EXPOSE 22, MAINTAINER, copying the whole build context, and COPY after USER without --chown. Pass ignore to silence rule ids.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Dockerfile text. Alternative to path. |
| ignore | array | – | Rule ids to skip. |
| path | string | – | Path to a local Dockerfile (up to 1048576 bytes). |
No output schema declared.
No examples provided.
parse_dockerfile Parse a Dockerfile ~93
Return the Dockerfile's instructions in order (instruction keyword, arguments with continuations joined, start and end line, stage index) and its build stages (index, AS name, base image, line), plus the escape character in effect.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Dockerfile text. Alternative to path. |
| path | string | – | Path to a local Dockerfile (up to 1048576 bytes). |
No output schema declared.
No examples provided.
How do I install the Dockerfile Lint MCP server?
Dockerfile Lint runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-dockerfile-lint:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/basitalisandhu/mcp-dockerfile-lint
claude mcp add basitalisandhu-mcp-dockerfile-lint -- docker run --rm -i ghcr.io/basitalisandhu/mcp-dockerfile-lint:0.2.1
What is the Dockerfile Lint MCP server?
Dockerfile Lint is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-dockerfile-lint. Lint Dockerfiles for root users, latest tags, secrets in ENV or ARG, missing HEALTHCHECK and more. This page covers its container image (ghcr.io/basitalisandhu/mcp-dockerfile-lint).
Is the Dockerfile Lint MCP server safe to use?
Dockerfile Lint scores 50 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dockerfile Lint MCP server expose?
Dockerfile Lint exposes 3 tools: lint_dockerfile, parse_dockerfile, explain_rule. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.
Is the Dockerfile Lint MCP server still maintained?
Dockerfile Lint is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Dockerfile Lint MCP server under?
Dockerfile Lint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.