What it does
Given a fix's version, its severity and a list of release branches with their version and support status, the tool first keeps only the candidates: supported branches older than the fix version and, if the version that introduced the bug is given, at or after that version. Branches that fail are still reported, each with one reason, checked in a fixed order: unsupported, not older than fix version, then predates bug introduction. Each candidate then receives an action from the severity. Critical fixes are backported to every candidate. Major fixes are backported to candidates on the same major line and considered for older major lines. Minor fixes are considered on the same major line and skipped on older ones. The result states whether any backport is needed, and lists the plan and skipped branches sorted by version, newest first.
Teams use it when they need a repeatable, auditable answer to which supported release lines should receive a fix, rather than deciding by judgement alone. Versions are compared numerically component by component, so 1.10.0 sorts above 1.9.0.
It runs in two ways. As a CLI, it reads a JSON arguments file and prints the result as JSON. As an MCP server, it exposes a check_backport tool that returns needs_backport, fix_version, severity, plan and skipped_branches. The computation is local and pure: it makes no network calls, needs no configuration, and does not read or change any repository. The project is released under the MIT licence.
Limitations and requirements
Versions must be plain x.y.z numbers. Severity must be one of critical, major or minor. fix_version and a non-empty branches array are required, and each branch needs a non-empty name, an x.y.z version and a boolean supported flag. Malformed input is rejected with a validation error naming the offending path, and an unreadable or invalid input file is a runtime error.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/backportcheck
Decide whether a fix needs a backport, and to which release branches.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it