# mergelock (oci · ghcr.io/sadayamuthu/mergelock)

Finds merge conflicts git can't see between branches: changed signatures vs new callers.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/sadayamuthu/mergelock`
- Version: `0.1.5`
- 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-04.

- **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**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 18 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 241 tokens (~120/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 mergelock MCP server?

mergelock runs locally as a container image, launched with docker run --rm -i ghcr.io/sadayamuthu/mergelock:0.1.5. 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 sadayamuthu-mergelock -- docker run --rm -i ghcr.io/sadayamuthu/mergelock:0.1.5
```

### Cursor

```json
{
  "mcpServers": {
    "sadayamuthu-mergelock": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sadayamuthu/mergelock:0.1.5"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sadayamuthu-mergelock": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sadayamuthu/mergelock:0.1.5"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sadayamuthu-mergelock -- docker run --rm -i ghcr.io/sadayamuthu/mergelock:0.1.5
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  sadayamuthu-mergelock:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/sadayamuthu/mergelock:0.1.5"]
```

### Netclaw

```json
{
  "McpServers": {
    "sadayamuthu-mergelock": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sadayamuthu/mergelock:0.1.5"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "sadayamuthu-mergelock": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sadayamuthu/mergelock:0.1.5"
      ]
    }
  }
}
```

## 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-03 (score 49, +1)

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

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

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

### 2026-10-31 (score 47, 0)

- [security regression] Provenance: unverified → fail

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

- [security regression] Provenance: fail → unverified

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

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

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

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

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

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

### 2026-10-23 (score 44, +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 (2)

### `check` (~151 tokens)

Check branches for merge conflicts

Simulate merging two committed branches and report textual and semantic conflicts, including ones git merges cleanly: a changed function signature against new call sites, a deleted symbol that is still used, duplicate definitions. Returns a verdict with result clean, warnings or conflict, and per finding the file, line and a suggested_action to apply. Call it after committing and before reporting work as done; fix every error finding, commit, and call it again. Uncommitted changes are not seen. Use claims instead to see what other agents are working on before you start.

Input parameters:

- `against` (string): branch to compare against; defaults to the configured target
- `branch` (string): branch to check; defaults to the current branch

Output parameters:

- `base` (string)
- `branches` (null|array)
- `coverage` (object)
- `findings` (null|array)
- `notes` (null|array)
- `result` (string)
- `stats` (object)
- `version` (integer)

### `claims` (~90 tokens)

List live work claims

List live claims (work scopes other agents have declared: branch, paths, symbols, intent) from refs/mergelock/claims, newest first; expired claims are left out. Call it before starting a task to pick files and symbols no other agent is changing. It reports intent only; to find actual conflicts between branches, use check. Read-only in v0.1: claims cannot be created here.

Output parameters:

- `claims` (null|array)

## Diagnostics

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

## Score history

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

## Common questions

### What is the mergelock MCP server?

mergelock is an MCP server listed in the public MCP registry as io.github.sadayamuthu/mergelock. Finds merge conflicts git can't see between branches: changed signatures vs new callers. This page covers its container image (ghcr.io/sadayamuthu/mergelock).

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

mergelock 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 mergelock MCP server expose?

mergelock exposes 2 tools: check, claims. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

### Is the mergelock MCP server still maintained?

mergelock is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/sadayamuthu/mergelock
- Repository: https://github.com/sadayamuthu/mergelock
- Changelog RSS feed: https://verifymcp.io/servers/sadayamuthu-mergelock/ghcr-io-sadayamuthu-mergelock.xml
- Changelog JSON feed: https://verifymcp.io/servers/sadayamuthu-mergelock/ghcr-io-sadayamuthu-mergelock.json
- HTML version of this page: https://verifymcp.io/servers/sadayamuthu-mergelock/ghcr-io-sadayamuthu-mergelock