# Gitattributes checker (exact git rules) (mcpb · gitattributes-check-1.0.0.mcpb)

Which git attributes apply to a file (line endings, binary, LFS, linguist) and which line decides.

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

## Components

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

## Channel facts

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

## 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**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 587 tokens (~293/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 Gitattributes checker (exact git rules) MCP server?

Gitattributes 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, f5b6ae467b262e32ea3b1646fff9fc175ddd89b2c8cf568ee1a067c3763cc146; 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/gitattributes-check-v1.0.0/gitattributes-check-1.0.0.mcpb`
- SHA-256: `f5b6ae467b262e32ea3b1646fff9fc175ddd89b2c8cf568ee1a067c3763cc146`

### Verify on macOS / Linux

```bash
echo "f5b6ae467b262e32ea3b1646fff9fc175ddd89b2c8cf568ee1a067c3763cc146  gitattributes-check-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

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

## 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-16 (score 38)

First indexed and scored.

## MCP tools (2)

### `check_attributes` (~328 tokens)

Which git attributes apply to this path?

Tells, exactly as `git check-attr -a` would, which attributes apply to each path (text, eol, binary, diff, merge, filter=lfs, export-ignore, linguist-*, any custom attribute), with the file and line that decides each one, and what that means in practice: line-ending conversion, binary diffs, Git LFS storage, files left out of release archives, GitHub language stats and collapsed generated files. Handles macros ([attr], built-in "binary"), set / -unset / !unspecified / value, nested .gitattributes files, .git/info/attributes, quoted patterns, and the trap that "dir/" never applies to the files inside. No repository needed: pass the .gitattributes content and the paths.

Input parameters:

- `attributes` (array): Only report these attributes (like `git check-attr text eol -- path`), including "unspecified" ones. Default: every attribute that is set, unset or has a value (like `git check-attr -a`).
- `files` (object): Several attribute files at once, as { "<path>": "<content>" }, e.g. { ".gitattributes": "...", "docs/.gitattributes": "...", ".git/info/attributes": "..." }. Paths are relative to the repository root.
- `gitattributes` (string): Content of the root .gitattributes file.
- `paths` (array, required): Paths relative to the repository root, with "/" separators. End a path with "/" if it is a directory.

Output parameters:

- `ignored_lines` (array)
- `results` (array)

### `explain_gitattributes` (~173 tokens)

Explain a .gitattributes, line by line

Explains every line of one or more .gitattributes files in plain English and flags the classic mistakes: "dir/" patterns that never reach the files inside, negative "!" patterns (ignored by git), macros outside the root file, invalid attribute names that make git drop the whole line, unquoted patterns with spaces, Git LFS rules without -text, bad eol / text values, the old crlf attribute.

Input parameters:

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

Output parameters:

- `lines` (array)
- `warnings_count` (integer)

## Diagnostics

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

## Score history

- 2026-11-21: 38
- 2026-11-20: 38
- 2026-11-19: 38
- 2026-11-18: 38
- 2026-11-17: 38
- 2026-11-16: 38

## Common questions

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

Gitattributes checker (exact git rules) is an MCP server listed in the public MCP registry as io.github.Lawatch/gitattributes-check. Which git attributes apply to a file (line endings, binary, LFS, linguist) and which line decides. This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/gitattributes-check-v1.0.0/gitattributes-check-1.0.0.mcpb).

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

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

Gitattributes checker (exact git rules) exposes 2 tools: check_attributes, explain_gitattributes. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.

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

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

VerifyMCP ran 11 checks on Gitattributes checker (exact git 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 Gitattributes checker (exact git 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-gitattributes-check/gitattributes-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-gitattributes-check/gitattributes-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-gitattributes-check/gitattributes-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-gitattributes-check/gitattributes-check
