io.github.vineethwilson15/semamerge

MCPcommunity
v0.1.2io.github.vineethwilson15UnknownUpdated 2mo agonpmGitHub

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

An MCP (Model Context Protocol) server that detects semantic merge conflicts between Git branches using AST-level analysis. When two branches change code in ways that Git merges cleanly but are functionally incompatible, SemaMerge catches it before the merge breaks your app. Conflict Type | Example | ---|---| Type signature change | Branch A changes return type, Branch B calls | Removed/renamed…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.vineethwilson15
LicenseUnknown
Version0.1.2
Sourcemcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/25
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/10
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
CVE scan · clean+30/30
Static analysis · clean+20/20
npm provenance (Sigstore)+0/5
Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.1.2 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

An MCP (Model Context Protocol) server that detects semantic merge conflicts between Git branches using AST-level analysis. When two branches change code in ways that Git merges cleanly but are functionally incompatible, SemaMerge catches it before the merge breaks your app. Conflict Type | Example | ---|---| Type signature change | Branch A changes return type, Branch B calls | Removed/renamed export | Branch A removes , Branch B adds | Parameter change | Branch A adds required param to…

Keywords
mcp