Upgrade Brief is answering right now. Last checked 6 min ago. It exposes 12 tools.
Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go.
Uptime history
11 days of history
11 days agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
374 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 7
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 October 2026. No other catalogue keeps this.
29 Oct
4 tools appeared
crates_breaking_changes, go_breaking_changes, helm_breaking_changes and 1 more
29 Oct
a tool changed version
26 Oct
a tool appeared
github_action_breaking_changes
26 Oct
a tool changed version
Nothing serious here today
Today is the operative word: we check Upgrade Brief 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
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add upgrade-brief --transport http https://upgrade-brief.shopttyass-85f.workers.dev/mcpSettings → Connectors → Add custom connector, then paste this address
https://upgrade-brief.shopttyass-85f.workers.dev/mcp~/.codex/config.toml
[mcp_servers.upgrade-brief]
url = "https://upgrade-brief.shopttyass-85f.workers.dev/mcp".cursor/mcp.json
{
"mcpServers": {
"upgrade-brief": {
"url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"upgrade-brief": {
"type": "http",
"url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
npm
npm_breaking_changes
npm breaking changes between two versions of a package, read from its real CHANGELOG and GitHub release notes: documented breaking items per version, major bumps, Node.js engine / ESM-CJS / peer dependency changes, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.
npm_changelog
npm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.json changes. Paid: $0.01 USDC per call via x402.
npm_versions
Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.
pypi
pypi_breaking_changes
PyPI breaking changes between two versions of a Python package, from its CHANGELOG/HISTORY/CHANGES file and GitHub releases: breaking items per version, Requires-Python and dependency changes, yanked versions, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.
pypi_changelog
PyPI changelog between two versions of a Python package: full release notes per version (newest first) with dates, bump type, yanked flags, extracted breaking changes and Requires-Python / dependency changes. Paid: $0.01 USDC per call via x402.
pypi_versions
Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.
breaking
go_breaking_changes
Go module upgrade brief between two versions: go.mod diff (go directive, requirements), major /vN import path change with the rewrite command, retracted and deprecated flags, breaking items from GitHub releases and CHANGELOG, the go get command. Paid: $0.005 USDC per call via x402.
crates
crates_breaking_changes
Rust crate upgrade brief between two versions: removed and changed Cargo features, default feature changes, dependency requirement diff, rust-version (MSRV) and edition changes, yanked releases in the range, breaking items from GitHub releases and CHANGELOG, the Cargo.toml edit. Paid: $0.005 USDC per call via x402.
dependency
dependency_upgrade_plan
Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk score, ordered by risk, plus peer requirements between the listed packages. Paid: $0.02 USDC per call via x402.
github
github_action_breaking_changes
GitHub Actions upgrade brief between two versions of an action (e.g. actions/checkout v3 to v4): breaking changes from release notes and migration docs, action.yml input/output diff (removed, renamed, new required inputs, changed defaults), Node runtime change (node16/node20 removed, node24), deprecations, concrete workflow edits with SHA pin, and sources. Paid: $0.005 USDC per call via x402.
helm
helm_breaking_changes
Helm chart upgrade brief between two chart versions: default values.yaml diff (removed, added, changed keys and possible renames), chart changelog and breaking items from Artifact Hub and the chart repo, README upgrade sections, kubeVersion, subchart and appVersion changes, concrete edits for your values file, sources. Paid: $0.01 USDC per call via x402.
terraform
terraform_breaking_changes
Terraform provider upgrade brief between two versions: BREAKING CHANGES and deprecations per release from the provider CHANGELOG and GitHub releases, the major upgrade guide headings and items, plugin protocol change, the required_providers edit, sources. Paid: $0.01 USDC per call via x402.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://upgrade-brief.shopttyass-85f.workers.dev/mcp | streamable-http | answering | 380 ms | 6 min ago |
Alternatives to Upgrade Brief
same job, measured the same wayDep Diff MCP
by digicatalyst-systems
Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.
landmine
by landmine
Known open GitHub issues in exact npm and PyPI versions, with workarounds, for coding agents.
Versionly
by versionly
Monitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs.
go-tokenless
by continuous-actions
Move npm publishing in GitHub Actions from NPM_TOKEN to trusted publishing (OIDC).
Intercom
by muhammadtalhamt
Relays messages between two Claude Code sessions on different machines using the Channels API
Domain Finder
by sra1phani
Check if a brand name is free across domains, GitHub, npm and PyPI, and suggest available names.
Action Runtime Sunset Lint
by jmshinhwa
Finds the GitHub Actions steps that stop running on 2026-09-23, with the version to move to
Robotbase Dev
by wygogogo19
Agent MCP: 18 tools — GitHub/HF/npm/PyPI/HN trends plus 17 web tools for coding agents.
Upgrade Brief — questions
Answers built from our own checks of this server.
What can Upgrade Brief do?
It exposes 12 tools, read directly from the server on our last check. Among them: crates_breaking_changes, dependency_upgrade_plan, github_action_breaking_changes, go_breaking_changes, helm_breaking_changes, npm_breaking_changes and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Upgrade Brief mostly used for?
Its tools cluster around npm and pypi. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Upgrade Brief working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 374 ms. The bar chart above shows every period we have measured.
How do I connect Upgrade Brief?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Upgrade Brief need an API key?
No. Upgrade Brief completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Upgrade Brief?
It answers our handshake in 374 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.