Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gitignore checker (exact git rules)

OCI · GHCR.IO/LAWATCH/GITIGNORE-CHECK · 2 COMPONENTS

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

42 Trust /100

Last scanned (16 hours ago)

Scores higher than 39% of OCI servers

Category Developer Tools

Trust breakdown (7 categories)

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 & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1
    • Provenance: unverified → fail ▼ security
  • 16 Nov 26 0
    • Provenance: fail → unverified ▼ security
    • Package version: 1.0.0 → 1.0.1 functional
  • 15 Nov 26 39

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed oci/ghcr.io/lawatch/gitignore-check@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 2 exposed · ~416 tokens

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 →

Tool Tokens
check_ignored ~261

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.

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

No examples provided.

explain_gitignore ~155

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.

NameTypeReqDescription
filesobject–Several .gitignore files at once, as { "<path>": "<content>" }, e.g. { ".gitignore": "...", "src/.gitignore": "..." }. Paths are relative to the repository root.
gitignorestring–Content of the root .gitignore file.
NameTypeReqDescription
rulesarrayyes–
warnings_countintegeryes–

No examples provided.

Install

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

Gitignore checker (exact git rules) runs locally as a container image, launched with docker run --rm -i ghcr.io/lawatch/gitignore-check:1.0.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/lawatch/gitignore-check

# add to Claude Code
claude mcp add lawatch-gitignore-check -- docker run --rm -i ghcr.io/lawatch/gitignore-check:1.0.1
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 container image (ghcr.io/lawatch/gitignore-check).

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.

Is the Gitignore checker (exact git rules) MCP server still maintained?

Gitignore checker (exact git rules) is still listed as active in the MCP registry. We last reached this channel on 21 November 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 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 a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.