# closure_drift (oci · ghcr.io/luizfnsilva/closure_drift)

Before an agent tags a release: does that version label already name different code in the git tags?

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

## Components

- oci · `ghcr.io/luizfnsilva/closure_drift`: 49/100 (this document), [markdown](https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift.md), [page](https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/luizfnsilva/closure_drift`
- Version: `1.5.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-05.

- **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**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 640 tokens (~160/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 closure_drift MCP server?

closure_drift runs locally as a container image, launched with docker run --rm -i ghcr.io/luizfnsilva/closure_drift:1.5.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 luizfnsilva-closure-drift -- docker run --rm -i ghcr.io/luizfnsilva/closure_drift:1.5.0
```

### Cursor

```json
{
  "mcpServers": {
    "luizfnsilva-closure-drift": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/luizfnsilva/closure_drift:1.5.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "luizfnsilva-closure-drift": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/luizfnsilva/closure_drift:1.5.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add luizfnsilva-closure-drift -- docker run --rm -i ghcr.io/luizfnsilva/closure_drift:1.5.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "luizfnsilva-closure-drift": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/luizfnsilva/closure_drift:1.5.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  luizfnsilva-closure-drift:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/luizfnsilva/closure_drift:1.5.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "luizfnsilva-closure-drift": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/luizfnsilva/closure_drift:1.5.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "luizfnsilva-closure-drift": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/luizfnsilva/closure_drift:1.5.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-04 (score 49, +1)

- [security regression] Stability: 0.53 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.3.3 → 1.5.0
- [functional] Package version: 1.3.3 → 1.4.0

### 2026-11-03 (score 48, 0)

- [functional] Package version: 1.3.1 → 1.3.3
- [functional] Package version: 1.3.1 → 1.3.2

### 2026-11-02 (score 48, +1)

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

### 2026-10-31 (score 47, +1)

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

### 2026-10-30 (score 46, 0)

- [functional] Package version: 1.2.2 → 1.3.1
- [functional] Package version: 1.2.2 → 1.3.0

### 2026-10-29 (score 46, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.33 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.2.1 → 1.2.2

### 2026-10-28 (score 45, 0)

- [functional] Package version: 1.2.0 → 1.2.1

### 2026-10-26 (score 45, +1)

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

## MCP tools (4)

### `would_tag` (~127 tokens)

Check before tagging

Use BEFORE creating a release tag: would the version that HEAD declares reuse a label that already names other code in the tags? Exit 1 means do not tag; bump the version first. Returns exit 0, 1 or 2 and the JSON report. Exit 2 is not a pass: nothing was decided, and output says why (no label found, a file not read, a tag not compared). Read-only: it runs git reads only, on the local repository, with no network.

Input parameters:

- `repo` (string, required): path to a local git repository with its tags fetched

Output parameters:

- `exit` (integer): 0 clean, 1 drift, 2 not decided (the reason is in output)
- `meaning` (string): the exit code in words
- `output`: the JSON report (docs/REPORT.md), or the refusal as text

### `check_versions` (~184 tokens)

Measure all version labels

Use to audit the whole tag history: does each version label name exactly one code state? For a single release about to be tagged, use would_tag. With one release only, the answer is not decided (exit 2). Returns exit 0, 1 or 2 and the JSON report. Exit 2 is not a pass: nothing was decided, and output says why (no label found, a file not read, a tag not compared). Read-only: it runs git reads only, on the local repository, with no network.

Input parameters:

- `published_file` (string): a local file with the versions actually released, one per line; tags not on it are not counted as publications
- `repo` (string, required): path to a local git repository with its tags fetched
- `strict` (boolean): answer clean only if every tag scanned was compared (default false)

Output parameters:

- `exit` (integer): 0 clean, 1 drift, 2 not decided (the reason is in output)
- `meaning` (string): the exit code in words
- `output`: the JSON report (docs/REPORT.md), or the refusal as text

### `explain_label` (~158 tokens)

Explain a label in drift

Use after check_versions reports drift: lists, for one label, the paths that differ between the first tag that used it and each other tag that did. For two references you choose, use compare. Returns exit 0, 1 or 2 and the JSON report. Exit 2 is not a pass: nothing was decided, and output says why (no label found, a file not read, a tag not compared). Read-only: it runs git reads only, on the local repository, with no network.

Input parameters:

- `label` (string, required): a version label reported in drift, as written in the report (e.g. 1.0.0)
- `repo` (string, required): path to a local git repository with its tags fetched

Output parameters:

- `exit` (integer): 0 clean, 1 drift, 2 not decided (the reason is in output)
- `meaning` (string): the exit code in words
- `output`: the JSON report (docs/REPORT.md), or the refusal as text

### `compare` (~171 tokens)

Compare two references

Use to compare any two tags or commits you name: their version labels, closures and the paths that differ. Publication points play no part. Exit 1 when both declare one label and the code differs. Returns exit 0, 1 or 2 and the JSON report. Exit 2 is not a pass: nothing was decided, and output says why (no label found, a file not read, a tag not compared). Read-only: it runs git reads only, on the local repository, with no network.

Input parameters:

- `a` (string, required): the first tag or commit (the reference side)
- `b` (string, required): the second tag or commit; paths are listed as changed, only in a, only in b
- `repo` (string, required): path to a local git repository with its tags fetched

Output parameters:

- `exit` (integer): 0 clean, 1 drift, 2 not decided (the reason is in output)
- `meaning` (string): the exit code in words
- `output`: the JSON report (docs/REPORT.md), or the refusal as text

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift#diagnostics

## Score history

- 2026-11-05: 49
- 2026-11-04: 49
- 2026-11-03: 48
- 2026-11-02: 48
- 2026-11-01: 47
- 2026-10-31: 47
- 2026-10-30: 46
- 2026-10-29: 46
- 2026-10-28: 45
- 2026-10-27: 45
- 2026-10-26: 45
- 2026-10-25: 44
- 2026-10-24: 44
- 2026-10-23: 43
- 2026-10-22: 43
- 2026-10-21: 41
- 2026-10-20: 40
- 2026-10-19: 40
- 2026-10-18: 39

## Common questions

### What is the closure_drift MCP server?

closure_drift is an MCP server listed in the public MCP registry as io.github.luizfnsilva/closure_drift. Before an agent tags a release: does that version label already name different code in the git tags? This page covers its container image (ghcr.io/luizfnsilva/closure_drift).

### Is the closure_drift MCP server safe to use?

closure_drift scores 49 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 closure_drift MCP server expose?

closure_drift exposes 4 tools: would_tag, check_versions, explain_label, compare. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

### Is the closure_drift MCP server still maintained?

closure_drift is still listed as active in the MCP registry. We last reached this channel on 5 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 closure_drift MCP server under?

closure_drift declares the Apache-2.0 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 closure_drift MCP server?

VerifyMCP ran 12 checks on closure_drift, 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 closure_drift: 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/luizfnsilva/closure_drift
- Repository: https://github.com/luizfnsilva/closure_drift
- Changelog RSS feed: https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift.xml
- Changelog JSON feed: https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift.json
- HTML version of this page: https://verifymcp.io/servers/luizfnsilva-closure-drift/ghcr-io-luizfnsilva-closure-drift