# Dockerignore checker (exact Docker rules) (mcpb · dockerignore-check-1.0.0.mcpb)

Which files does docker build send, and which .dockerignore line decides? Exact BuildKit rules.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `dockerignore-check-1.0.0.mcpb`: 40/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check.md), [page](https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check)
- oci · `ghcr.io/lawatch/dockerignore-check`: 42/100, [markdown](https://verifymcp.io/servers/lawatch-dockerignore-check/ghcr-io-lawatch-dockerignore-check.md), [page](https://verifymcp.io/servers/lawatch-dockerignore-check/ghcr-io-lawatch-dockerignore-check)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/dockerignore-check-v1.0.0/dockerignore-check-1.0.0.mcpb`
- Transport: `stdio`
- SHA-256: `d68d78ce67cdd69e65adce5b60b4959caa8ebce4cd207efb1df655a75c51cb33`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 455 tokens (~227/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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.

## Install

### How do I install the Dockerignore checker (exact Docker rules) MCP server?

Dockerignore checker (exact Docker rules) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, d68d78ce67cdd69e65adce5b60b4959caa8ebce4cd207efb1df655a75c51cb33; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Lawatch/10aday/releases/download/dockerignore-check-v1.0.0/dockerignore-check-1.0.0.mcpb`
- SHA-256: `d68d78ce67cdd69e65adce5b60b4959caa8ebce4cd207efb1df655a75c51cb33`

### Verify on macOS / Linux

```bash
echo "d68d78ce67cdd69e65adce5b60b4959caa8ebce4cd207efb1df655a75c51cb33  dockerignore-check-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\dockerignore-check-1.0.0.mcpb).Hash -eq "d68d78ce67cdd69e65adce5b60b4959caa8ebce4cd207efb1df655a75c51cb33"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-15 (score 40)

First indexed and scored.

## MCP tools (2)

### `check_dockerignore` (~263 tokens)

Which files go into the Docker build context?

Tells, exactly as Docker BuildKit does, whether each path is sent to the build context (so COPY/ADD can see it) or excluded by .dockerignore, and which line decides. .dockerignore is NOT .gitignore: "*.log" only matches at the root (use "**/*.log"), "node_modules" does not exclude packages/app/node_modules, a trailing "/" is ignored, "#" must be at column 1, and the last matching line wins. Use it before writing a .dockerignore, when COPY fails with "not found", when the context is huge or when secrets (.env, .git) might leak into the image. Pass the .dockerignore content and the project paths; no Docker or file access needed.

Input parameters:

- `dockerignore` (string, required): Content of the .dockerignore file (or of <Dockerfile name>.dockerignore, which takes precedence when it exists).
- `only` (string): Return all paths (default), only the ones sent, or only the excluded ones.
- `paths` (array, required): Paths relative to the build context root, with "/" separators (e.g. the output of `git ls-files` or `find . -type f`). End a path with "/" for an empty directory.

Output parameters:

- `context` (array): Everything Docker sends (files, and directories ending with "/"), sorted.
- `results` (array)
- `summary` (object)
- `warnings` (array)

### `explain_dockerignore` (~125 tokens)

Explain a .dockerignore, line by line

Explains every rule of a .dockerignore in plain English, as Docker reads it (after its own clean-up: leading "/" removed, trailing "/" dropped, "./" and ".." resolved), and flags the classic mistakes: root-only patterns meant for any depth (*.log, node_modules), "#" not at column 1, "!" rules with nothing to re-include, invalid patterns that make the build fail.

Input parameters:

- `dockerignore` (string, required): Content of the .dockerignore file (or of <Dockerfile name>.dockerignore, which takes precedence when it exists).

Output parameters:

- `rules` (array)
- `warnings_count` (integer)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check#diagnostics

## Score history

- 2026-11-21: 40
- 2026-11-20: 40
- 2026-11-19: 40
- 2026-11-18: 40
- 2026-11-17: 40
- 2026-11-16: 40
- 2026-11-15: 40

## Common questions

### What is the Dockerignore checker (exact Docker rules) MCP server?

Dockerignore checker (exact Docker rules) is an MCP server listed in the public MCP registry as io.github.Lawatch/dockerignore-check. Which files does docker build send, and which .dockerignore line decides? Exact BuildKit rules. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/dockerignore-check-v1.0.0/dockerignore-check-1.0.0.mcpb).

### Is the Dockerignore checker (exact Docker rules) MCP server safe to use?

Dockerignore checker (exact Docker rules) scores 40 out of 100 on VerifyMCP. 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 Dockerignore checker (exact Docker rules) MCP server expose?

Dockerignore checker (exact Docker rules) exposes 2 tools: check_dockerignore, explain_dockerignore. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.

### What licence is the Dockerignore checker (exact Docker rules) MCP server under?

Dockerignore checker (exact Docker rules) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Dockerignore checker (exact Docker rules) MCP server?

VerifyMCP ran 11 checks on Dockerignore checker (exact Docker rules), covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about Dockerignore checker (exact Docker rules): Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-dockerignore-check/dockerignore-check
