io.github.vineethwilson15/semamerge
NPM · SEMAMERGE · SCANNED SEP 20
Detects semantic merge conflicts between Git branches using AST-level analysis
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 147 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 358 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_merge_safety" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vineethwilson15/semamerge MCP server?
io.github.vineethwilson15/semamerge runs locally as an npm package, launched with npx -y semamerge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · semamerge
claude mcp add vineethwilson15-semamerge -- npx -y semamerge
{
"mcpServers": {
"vineethwilson15-semamerge": {
"command": "npx",
"args": [
"-y",
"semamerge"
]
}
}
} {
"servers": {
"vineethwilson15-semamerge": {
"command": "npx",
"args": [
"-y",
"semamerge"
]
}
}
} codex mcp add vineethwilson15-semamerge -- npx -y semamerge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vineethwilson15-semamerge": {
"type": "local",
"command": [
"npx",
"-y",
"semamerge"
],
"enabled": true
}
}
} openclaw mcp add vineethwilson15-semamerge --command npx --arg -y --arg semamerge
mcp_servers:
vineethwilson15-semamerge:
command: "npx"
args: ["-y", "semamerge"] {
"McpServers": {
"vineethwilson15-semamerge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"semamerge"
]
}
}
} assistant mcp add vineethwilson15-semamerge -t stdio -c npx -a -y semamerge
{
"mcpServers": {
"vineethwilson15-semamerge": {
"command": "npx",
"args": [
"-y",
"semamerge"
]
}
}
} 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.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/semamerge@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_branches ~91
Deep semantic analysis between two branches. Returns a detailed per-file report of all semantic changes and conflicts, including cross-file dependency issues.
| Name | Type | Req | Description |
|---|---|---|---|
| baseBranch | string | – | Common base branch (auto-detected if not provided) |
| branchA | string | yes | First branch to compare |
| branchB | string | yes | Second branch to compare |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.
analyze_file_pair ~82
Deep-dive semantic diff of a single file between two branches. Shows exactly what each branch changed and where conflicts arise.
| Name | Type | Req | Description |
|---|---|---|---|
| branchA | string | yes | First branch |
| branchB | string | yes | Second branch |
| filePath | string | yes | Path to the file within the repository |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.
check_merge_safety ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repoPath | string | yes | Absolute path to the Git repository |
| sourceBranch | string | yes | The branch being merged (source) |
| targetBranch | string | yes | The branch being merged into (target) |
No output schema declared.
No examples provided.
list_semantic_changes ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| baseBranch | string | – | Base branch to compare against (defaults to merge-base with HEAD) |
| branch | string | yes | Branch to analyze |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.
What is the io.github.vineethwilson15/semamerge MCP server?
io.github.vineethwilson15/semamerge is an MCP server listed in the public MCP registry as io.github.vineethwilson15/semamerge. Detects semantic merge conflicts between Git branches using AST-level analysis. This page covers its npm package (semamerge).
Is the io.github.vineethwilson15/semamerge MCP server safe to use?
io.github.vineethwilson15/semamerge scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.vineethwilson15/semamerge MCP server expose?
io.github.vineethwilson15/semamerge exposes 4 tools: check_merge_safety, analyze_branches, list_semantic_changes, analyze_file_pair. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.
Is the io.github.vineethwilson15/semamerge MCP server still maintained?
io.github.vineethwilson15/semamerge is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.vineethwilson15/semamerge MCP server under?
io.github.vineethwilson15/semamerge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.