# EditorConfig checker (exact rules) (oci · ghcr.io/lawatch/editorconfig-check)

Which .editorconfig settings apply to a file (indent, line endings, charset) and which line decides.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/lawatch/editorconfig-check`
- Version: `1.0.0`
- Transport: `stdio`

## 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: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 568 tokens (~284/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**: 17/100
  - Stability observed for 5 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 EditorConfig checker (exact rules) MCP server?

EditorConfig checker (exact rules) runs locally as a container image, launched with docker run --rm -i ghcr.io/lawatch/editorconfig-check:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lawatch-editorconfig-check -- docker run --rm -i ghcr.io/lawatch/editorconfig-check:1.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "lawatch-editorconfig-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/editorconfig-check:1.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lawatch-editorconfig-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/editorconfig-check:1.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lawatch-editorconfig-check -- docker run --rm -i ghcr.io/lawatch/editorconfig-check:1.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lawatch-editorconfig-check": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/editorconfig-check:1.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  lawatch-editorconfig-check:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/lawatch/editorconfig-check:1.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "lawatch-editorconfig-check": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/editorconfig-check:1.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "lawatch-editorconfig-check": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/editorconfig-check:1.0.0"
      ]
    }
  }
}
```

## 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 41, +1)

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

### 2026-11-18 (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-17 (score 39, 0)

- [security regression] Provenance: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `check_editorconfig` (~260 tokens)

Which EditorConfig settings apply to this file?

Tells, exactly as editors and Prettier read it (reference EditorConfig core), which settings apply to each file: indent_style, indent_size, tab_width, end_of_line, charset, insert_final_newline, trim_trailing_whitespace, max_line_length and any custom key, with the file, [section] and line that decides each one, every section that matched, and the values derived automatically (tab_width from indent_size, indent_size = tab). Handles globs exactly (*, **, ?, [a-z], [!x], {a,b}, {1..10}, escapes), nested .editorconfig files, root = true, unset, and the parser trap where one bad line hides the rest of the file. No project needed: pass the .editorconfig content and the paths.

Input parameters:

- `editorconfig` (string): Content of the root .editorconfig file.
- `files` (object): Several .editorconfig files at once, as { "<path>": "<content>" }, e.g. { ".editorconfig": "...", "src/legacy/.editorconfig": "..." }. Paths are relative to the project root.
- `paths` (array, required): File paths relative to the project root, with "/" separators.

Output parameters:

- `problems_count` (integer)
- `results` (array)

### `lint_editorconfig` (~196 tokens)

Find the mistakes in an .editorconfig

Checks one or more .editorconfig files and flags what silently breaks them: a line the parser does not understand (editors then ignore every line below it), comments at the end of a value ("indent_size = 4 # four" is invalid), invalid values (indent_style, end_of_line, charset, booleans, sizes), misspelled property names ("indent_sise"), "root" in the wrong place or missing, keys before any [section], braces with one choice ({js} is literal), ".." in globs, spaces inside brackets, duplicate keys.

Input parameters:

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

Output parameters:

- `problems` (array)
- `sections` (array)

## Diagnostics

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

## Score history

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

## Common questions

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

EditorConfig checker (exact rules) is an MCP server listed in the public MCP registry as io.github.Lawatch/editorconfig-check. Which .editorconfig settings apply to a file (indent, line endings, charset) and which line decides. This page covers its container image (ghcr.io/lawatch/editorconfig-check).

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

EditorConfig checker (exact rules) scores 41 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 EditorConfig checker (exact rules) MCP server expose?

EditorConfig checker (exact rules) exposes 2 tools: check_editorconfig, lint_editorconfig. Their descriptions and schemas cost roughly 456 tokens of context every time the server is loaded.

### Is the EditorConfig checker (exact rules) MCP server still maintained?

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

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

VerifyMCP ran 12 checks on EditorConfig checker (exact 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 EditorConfig checker (exact 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.

## Links

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