Connect-MCP

Breaking Changes & Migration Data

io.github.nigelcox98/breaking-changes · v0.1.0

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

MCPremoteno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 84/100

What it does: 3 tools · 3 read, 0 write

Test call list_packages: worked (1,036 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +6
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +3
  • Read/write annotations: 0
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://agentdataapi.onrender.com/mcp

Tools

3 tools listed at last check
  • 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.
  • 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 rel
  • 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.

Badge

Connect-MCP badge for io.github.nigelcox98/breaking-changes

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.nigelcox98/breaking-changes.svg)](https://clawy.uk/mcp/s/io.github.nigelcox98/breaking-changes)

Repository