Skip to content

Breaking Changes & Migration Data

by nigelcox98 · remote · no sign-in to list tools · v0.1.0 · published by GitHub user nigelcox98

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • check_upgrade_safetyGiven 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 co…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • get_breaking_changesGet breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible dependencies, offic…No findings

    Why it is in this group

    • The name "get_breaking_changes" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_packagesList every package with breaking-change data available, including tracked versions and how many breaking changes each has.No findings

    Why it is in this group

    • The name "list_packages" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__breaking-changes__list_packages",
      "mcp__breaking-changes__get_breaking_changes"
    ],
    "ask": [
      "mcp__breaking-changes__check_upgrade_safety"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as breaking-changes. Review it before you use it.