Breaking Changes & Migration Data MCP Server

by nigelcox98

answering

Breaking Changes & Migration Data is answering right now. Last checked 6 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 9 hours of history

9 hours agonow

100.0%

Uptime 24h

31 of 31 checks

Tools

read from the server

529 ms

Response time

average over 24h

open, no key

Access

streamable-http

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add breaking-changes --transport http https://agentdataapi.onrender.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "breaking-changes": {
      "url": "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

{
  "mcpServers": {
    "breaking-changes": {
      "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

URL	Transport	State	Latency	Checked
https://agentdataapi.onrender.com/mcp	streamable-http	answering	511 ms	6 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.

20 installs/wk local only

Miro

by miroapp

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

answering

Layero

by layero

Build a landing page from your IDE chat, publish it, then manage domains and analytics.

27 tools answering

Financial Data API

by financialdatapi

Point-in-time macro, central bank rates and sentiment, COT positioning, from official sources.

answering

China Phone MCP

by bg7iuy

Look up Chinese phone number carrier, province, and city from official MIIT allocation data.

2 tools answering

Hevy (unofficial)

by almostjacked

Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.

44 installs/wk answering

BumpGuard

by appcreationsca

Reports which of your code's API usages break when you upgrade a dependency (Python, .NET, Java).

228 installs/wk local only

Dango

by trydango

Build decks in your own brand, from the AI agent you already use. Then edit them yourself.

answering

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 31 of 31 checks got a reply (100.0%), average response time 529 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 with the file path 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 529 ms on average, which is faster than 22% 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.