GenPark Git Semantic Cherry-Pick Conflict Resolver MCP Server

by alphaparkinc Your server? Claim it

local only

GenPark Git Semantic Cherry-Pick Conflict Resolver runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 19 Oct 2026.

Three-way AST hunk alignment and non-overlapping block conflict resolution for Git cherry-picks

—

Installs / week

not published

Stars

0 open issues

19 Oct 2026

Last commit

from GitHub

—

License

Python

Nothing serious here today

Today is the operative word: we check GenPark Git Semantic Cherry-Pick Conflict Resolver every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Alternatives to GenPark Git Semantic Cherry-Pick Conflict Resolver

same job, measured the same way

GenPark SemVer Dependency Resolver Agent

by alphaparkinc

Semantic Versioning 2.0.0 range matcher and dependency tree resolver for multi-agent toolkits and pl

local only

GenPark Circuit Breaker Fault Sentinel

by alphaparkinc

Three-state circuit breaker with failure rate tripping and automatic half-open probe recovery

local only

Stompy – AI Memory for Claude & MCP Agents

by stompy

Persistent AI memory with semantic search, conflict detection, and ticketing.

answering

GenPark Git Commit Conventional Semantic Linter

by alphaparkinc

Conventional Commits 1.0.0 semantic linter and changelog grouping engine parsing breaking changes an

local only

GenPark Bloom Filter URL Dedup Crawler

by alphaparkinc

In-memory Bloom filter for URL and document hash deduplication preventing redundant web crawler inge

local only

three.ws Naming

by nirholas

On-chain identity for AI agents: resolve .sol names, reverse-lookup wallets, check handles.

59 installs/wk local only

Cortex

by filippopilo

Patent-pending semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial.

7 tools answering

GenPark RAG Semantic Boundary Chunker

by alphaparkinc

Semantic boundary preserving text chunker maintaining markdown headers, code fences, and paragraphs

local only

GenPark Git Semantic Cherry-Pick Conflict Resolver — questions

Answers built from our own checks of this server.

Why is there no uptime for GenPark Git Semantic Cherry-Pick Conflict Resolver?

GenPark Git Semantic Cherry-Pick Conflict Resolver runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.

Is GenPark Git Semantic Cherry-Pick Conflict Resolver open source?

We cannot say either way: written in Python and 7 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.