Upgradepath runs on your own machine — the client starts it, so there is no endpoint to ping. 292 installs a week from npm. Last commit 3 Nov 2026.
Plan a safe dependency upgrade path: ordered intermediate versions, breaking changes, verdict.
Today is the operative word: we check Upgradepath every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 upgradepath -- npx -y @reneturcios/upgradepath
{
"mcpServers": {
"upgradepath": {
"command": "npx",
"args": [
"-y",
"@reneturcios/upgradepath"
]
}
}
}
[mcp_servers.upgradepath]
command = "npx"
args = ["-y", "@reneturcios/upgradepath"]
{
"mcpServers": {
"upgradepath": {
"command": "npx",
"args": [
"-y",
"@reneturcios/upgradepath"
]
}
}
}
{
"servers": {
"upgradepath": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/upgradepath"
]
}
}
}
Inspect NuGet package APIs, dependencies, metadata, and breaking changes across versions.
Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go.
Independent verification that a change kept its declared constraints. No model in the verdict path.
Diff two npm/PyPI versions or lockfiles: new install scripts, network/shell/eval calls, new deps.
Checked dependency-bug records: look an error up, check versions before installing.
Deterministic package.json upgrade plans: age gate, aligned peers, reasons per change. No AI.
What breaks when you upgrade a package, and what to use instead - from official docs.
Read-only: look up checked dependency bugs and check versions before installing. No account.
Answers built from our own checks of this server.