# io.github.vineethwilson15/semamerge (npm · semamerge)

Detects semantic merge conflicts between Git branches using AST-level analysis

- Trust score: 68/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `semamerge`: 68/100 (this document), [markdown](https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge.md), [page](https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge)

## Channel facts

- Registry: `npm`
- Package: `semamerge`
- Version: `0.1.2`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.
- **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 99 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 358 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add vineethwilson15-semamerge -- npx -y semamerge
```

### Codex

```bash
codex mcp add vineethwilson15-semamerge -- npx -y semamerge
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vineethwilson15-semamerge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "semamerge"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vineethwilson15-semamerge --command npx --arg -y --arg semamerge
```

### Hermes

```yaml
mcp_servers:
  vineethwilson15-semamerge:
    command: "npx"
    args: ["-y", "semamerge"]
```

### Other

```json
{
  "mcpServers": {
    "vineethwilson15-semamerge": {
      "command": "npx",
      "args": [
        "-y",
        "semamerge"
      ]
    }
  }
}
```

## 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-08-03 (score 68, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 65, +44)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional] Licence: MIT

### 2026-08-01 (score 21, +15)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 6, −40)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-30 (score 46, +22)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (4)

### `check_merge_safety` (~96 tokens)

Quick pre-merge safety check. Analyzes two branches for semantic conflicts that Git would miss (signature changes, removed exports, parameter mismatches, etc.). Returns a risk score: safe/warning/danger.

Input parameters:

- `repoPath` (string, required): Absolute path to the Git repository
- `sourceBranch` (string, required): The branch being merged (source)
- `targetBranch` (string, required): The branch being merged into (target)

### `analyze_branches` (~91 tokens)

Deep semantic analysis between two branches. Returns a detailed per-file report of all semantic changes and conflicts, including cross-file dependency issues.

Input parameters:

- `baseBranch` (string): Common base branch (auto-detected if not provided)
- `branchA` (string, required): First branch to compare
- `branchB` (string, required): Second branch to compare
- `repoPath` (string, required): Absolute path to the Git repository

### `list_semantic_changes` (~89 tokens)

Lists all semantic changes on a branch (function additions/removals, export changes, type changes, etc.) relative to a base. Useful for understanding what semantically changed.

Input parameters:

- `baseBranch` (string): Base branch to compare against (defaults to merge-base with HEAD)
- `branch` (string, required): Branch to analyze
- `repoPath` (string, required): Absolute path to the Git repository

### `analyze_file_pair` (~82 tokens)

Deep-dive semantic diff of a single file between two branches. Shows exactly what each branch changed and where conflicts arise.

Input parameters:

- `branchA` (string, required): First branch
- `branchB` (string, required): Second branch
- `filePath` (string, required): Path to the file within the repository
- `repoPath` (string, required): Absolute path to the Git repository

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 65
- 2026-08-01: 21
- 2026-07-31: 6
- 2026-07-30: 46
- 2026-07-28: 24
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/semamerge
- Socket report: https://socket.dev/npm/package/semamerge
- Repository: https://github.com/vineethwilson15/semamerge
- Changelog RSS feed: https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vineethwilson15-semamerge/semamerge