mergelock
OCI · GHCR.IO/SADAYAMUTHU/MERGELOCK
Finds merge conflicts git can't see between branches: changed signatures vs new callers.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of OCI servers
Category Testing and QA
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 & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 241 tokens (~120/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 31 Oct 26 0
- Provenance: unverified → fail ▼ security
- 30 Oct 26 0
- Provenance: fail → unverified ▼ security
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
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 4 Nov 2026 · Analysed oci/ghcr.io/sadayamuthu/mergelock@0.1.5
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 →
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 →
check Check branches for merge conflicts ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| against | string | – | branch to compare against; defaults to the configured target |
| branch | string | – | branch to check; defaults to the current branch |
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | – |
| branches | null|array | yes | – |
| coverage | object | yes | – |
| findings | null|array | yes | – |
| notes | null|array | – | – |
| result | string | yes | – |
| stats | object | yes | – |
| version | integer | yes | – |
No examples provided.
claims List live work claims ~90
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | null|array | yes | – |
No examples provided.
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.
oci · ghcr.io/sadayamuthu/mergelock
claude mcp add sadayamuthu-mergelock -- docker run --rm -i ghcr.io/sadayamuthu/mergelock:0.1.5
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.