# Gitignore checker (exact git rules) (mcpb · gitignore-check-1.0.1.mcpb)

Is this path ignored by git, and by which .gitignore line? Same answer as git check-ignore.

- Trust score: 42/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

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

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/gitignore-check-v1.0.1/gitignore-check-1.0.1.mcpb`
- Transport: `stdio`
- SHA-256: `0d5c2320a013298a6b560a67ca11352513ac839666eabf6e02bc75f30d8009bf`

## 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-22.

- **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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 477 tokens (~238/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**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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: 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.

## Install

### How do I install the Gitignore checker (exact git rules) MCP server?

Gitignore checker (exact git 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, 0d5c2320a013298a6b560a67ca11352513ac839666eabf6e02bc75f30d8009bf; 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/gitignore-check-v1.0.1/gitignore-check-1.0.1.mcpb`
- SHA-256: `0d5c2320a013298a6b560a67ca11352513ac839666eabf6e02bc75f30d8009bf`

### Verify on macOS / Linux

```bash
echo "0d5c2320a013298a6b560a67ca11352513ac839666eabf6e02bc75f30d8009bf  gitignore-check-1.0.1.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\gitignore-check-1.0.1.mcpb).Hash -eq "0d5c2320a013298a6b560a67ca11352513ac839666eabf6e02bc75f30d8009bf"
```

## 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-21 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 39, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `check_ignored` (~261 tokens)

Is this path ignored by git?

Tells, exactly as git would (`git check-ignore -v`), whether each path is ignored by the given .gitignore rules, and which file and line decides. Handles negation (!), anchoring (/), directory-only rules (dir/), **, character classes, escapes, trailing spaces, nested .gitignore files, and the rule that nothing inside an ignored directory can be re-included. Use it before adding, moving or committing files, or when a .gitignore "does not work". No repository or file access needed: pass the .gitignore content and the paths.

Input parameters:

- `files` (object): Several .gitignore files at once, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "src/.gitignore": "..." }. Paths are relative to the repository root.
- `gitignore` (string): Content of the root .gitignore file.
- `only` (string): Return all paths (default), or only the ignored ones, or only the ones git would keep.
- `paths` (array, required): Paths relative to the repository root, with "/" separators. End a path with "/" if it is a directory (directory-only rules like "build/" only match directories).

Output parameters:

- `results` (array)
- `summary` (object)

### `explain_gitignore` (~155 tokens)

Explain a .gitignore, line by line

Explains every rule of one or more .gitignore files in plain English (what it matches, anchored or not, directories only, re-include) and flags the classic mistakes: a "!" rule that cannot work because its parent directory is already ignored, trailing spaces, "#" not at the start of the line, "**" glued to other characters, unclosed "[", trailing backslash.

Input parameters:

- `files` (object): Several .gitignore files at once, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "src/.gitignore": "..." }. Paths are relative to the repository root.
- `gitignore` (string): Content of the root .gitignore file.

Output parameters:

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

## Diagnostics

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

## Score history

- 2026-11-22: 42
- 2026-11-21: 42
- 2026-11-20: 41
- 2026-11-19: 41
- 2026-11-18: 40
- 2026-11-17: 40
- 2026-11-16: 39
- 2026-11-15: 39

## Common questions

### What is the Gitignore checker (exact git rules) MCP server?

Gitignore checker (exact git rules) is an MCP server listed in the public MCP registry as io.github.Lawatch/gitignore-check. Is this path ignored by git, and by which .gitignore line? Same answer as git check-ignore. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/gitignore-check-v1.0.1/gitignore-check-1.0.1.mcpb).

### Is the Gitignore checker (exact git rules) MCP server safe to use?

Gitignore checker (exact git rules) scores 42 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 Gitignore checker (exact git rules) MCP server expose?

Gitignore checker (exact git rules) exposes 2 tools: check_ignored, explain_gitignore. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.

### What licence is the Gitignore checker (exact git rules) MCP server under?

Gitignore checker (exact git 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 Gitignore checker (exact git rules) MCP server?

VerifyMCP ran 12 checks on Gitignore checker (exact git rules), covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Gitignore checker (exact git rules): Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 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-gitignore-check/gitignore-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-gitignore-check/gitignore-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-gitignore-check/gitignore-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-gitignore-check/gitignore-check
