Breaking Changes & Migration Data
by @fastdrop
What breaks when you upgrade a package, and what to use instead - from official docs.
What breaks when you upgrade a package, and what to use instead - from official docs. Official MCP Registry: io.github.nigelcox98/breaking-changes@0.1.0. Remote endpoint: https://agentdataapi.onrender.com/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as io.github.nigelcox98/breaking-changes and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 5 Aug 2026. Not supplied by the maker.
list_packagesList 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_changesGet 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
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 codemods exist, and th
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingRelated Products
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.