Breaking Changes & Migration Data
by agentdataapi.onrender.com in Other
What breaks when you upgrade a package, and what to use instead - from official docs.
https://agentdataapi.onrender.com/mcp- Tools
- 3
- open to any client
- Uptime
- 75.0%
- last 30 days
- Response time
- 437 ms
- 825 ms slowest 5%
- Last check
- Passed
- 2 h ago, next in 4 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"breaking-changes-migration-data": {
"type": "http",
"url": "https://agentdataapi.onrender.com/mcp"
}
}
}3 tools
- 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…
- 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.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 2 h ago | Passed | 200 | 431 ms |
| 11 h ago | Passed | 200 | 394 ms |
| 22 h ago | Passed | 200 | 442 ms |
| 32 h ago | Passed | 200 | 469 ms |
| 43 h ago | Passed | 200 | 442 ms |
Show 10 older checks
| 2 days ago | Passed | 200 | 437 ms |
| 3 days ago | Passed | 200 | 825 ms |
| 3 days ago | Passed | 200 | 394 ms |
| 4 days ago | Passed | 200 | 420 ms |
| 4 days ago | Passed | 200 | 415 ms |
| 4 days ago | Passed | 200 | 819 ms |
| 5 days ago | Passed | 200 | 458 ms |
| 6 days ago | initialize returned HTTP 307 | 307 | 213 ms |
| 7 days ago | initialize returned HTTP 307 | 307 | 317 ms |
| 7 days ago | initialize returned HTTP 307 | 307 | 244 ms |