Backportcheck runs on your own machine — the client starts it, so there is no endpoint to ping. 270 installs a week from npm. Last commit 2 Nov 2026.
Decide whether a fix needs a backport, and to which release branches.
Nothing serious here today
Today is the operative word: we check Backportcheck every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add backportcheck -- npx -y @reneturcios/backportcheck{
"mcpServers": {
"backportcheck": {
"command": "npx",
"args": [
"-y",
"@reneturcios/backportcheck"
]
}
}
}[mcp_servers.backportcheck]
command = "npx"
args = ["-y", "@reneturcios/backportcheck"]{
"mcpServers": {
"backportcheck": {
"command": "npx",
"args": [
"-y",
"@reneturcios/backportcheck"
]
}
}
}{
"servers": {
"backportcheck": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/backportcheck"
]
}
}
}Alternatives to Backportcheck
same job, measured the same way13 rules that decide whether a vulnerability report ever reaches you
Scores whether a page reads as AI-generated and names the tells to fix.
19 date-aware checks on the [project] metadata that decides whether your next release uploads
Finds real dead code and proposes a safe, test-gated branch+PR to remove it.
Config-driven branch and release helpers for Git repositories
Review an existing fal video and decide whether to edit, retry once, or change approach.
Ask batchwatch whether to batch a job and get the real measured queue evidence, not a guess.
Wait for production to clear each deploy, and read the evidence when a release fails.
Backportcheck — questions
Answers built from our own checks of this server.