mcpbeat Sign in

Breaking Changes & Migration Data MCP Server

by nigelcox98 Your server? Claim it
answering

Breaking Changes & Migration Data is answering right now. Last checked 11 min ago. It exposes 3 tools.

What breaks when you upgrade a package, and what to use instead - from official docs.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
563 ms
Response time
average over 24h
open, no key
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add breaking-changes --transport http https://agentdataapi.onrender.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agentdataapi.onrender.com/mcp
~/.codex/config.toml
[mcp_servers.breaking-changes]
url = "https://agentdataapi.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "breaking-changes": {
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "breaking-changes": {
      "type": "http",
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

breaking
get_breaking_changes
Get breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible dependencies, official source URL, and codemod/automated-fix commands. Omit `version` to get every tracked version. Use this instead of relying on training data, which may predate the release.
packages
list_packages
List every package with breaking-change data available, including tracked versions and how many breaking changes each has. Call this first if you are unsure whether a package is covered.
upgrade
check_upgrade_safety
Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals, whether automated codemods exist, and the recommended upgrade path. Use before performing an upgrade.

Endpoints

URLTransportStateLatencyChecked
https://agentdataapi.onrender.com/mcp streamable-http answering 493 ms 11 min ago

Alternatives to Breaking Changes & Migration Data

same job, measured the same way
Vdiff MCP
by mcurmi05

Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.

61 installs/wk local only
TDE
by danha2048

Before you sign a trade deal: what it does to your cash month by month, and what to ask for instead.

answering
NuGet API Inspector
by dimonsmart

Inspect NuGet package APIs, dependencies, metadata, and breaking changes across versions.

local only
LogPulse
by lovable-release-ripple-roadmap

Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.

9 tools answering
EU vacancies tracker
by montoyer-eujobs

Open vacancies and competitions of the EU institutions, read daily from their official job pages.

4 tools answering
Location & Demand Intelligence
by timzinin-api

Pay-per-call where-and-when-to-operate signals from official local statistics.

7 tools answering
Miro
by miroapp

Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.

answering
toolmenu
by niksa90

Checks MCP tool lists: what agents misread, what breaks clients or caches, breaking changes

2 359 installs/wk local only

Breaking Changes & Migration Data — questions

Answers built from our own checks of this server.

What can Breaking Changes & Migration Data do?
It exposes 3 tools, read directly from the server on our last check. Among them: check_upgrade_safety, get_breaking_changes, list_packages. 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 →
Is Breaking Changes & Migration Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 563 ms. The bar chart above shows every period we have measured.
Is Breaking Changes & Migration Data still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Breaking Changes & Migration Data?
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 Breaking Changes & Migration Data need an API key?
No. Breaking Changes & Migration Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Breaking Changes & Migration Data?
It answers our handshake in 563 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.