Breaking Changes & Migration Data
REMOTE · AGENTDATAAPI.ONRENDER.COM · SCANNED OCT 4
What breaks when you upgrade a package, and what to use instead - from official docs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 286 tokens (~95/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Breaking Changes & Migration Data MCP server?
Breaking Changes & Migration Data is a hosted endpoint at https://agentdataapi.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentdataapi.onrender.com
claude mcp add --transport http nigelcox98-breaking-changes 'https://agentdataapi.onrender.com/mcp'
{
"mcpServers": {
"nigelcox98-breaking-changes": {
"url": "https://agentdataapi.onrender.com/mcp"
}
}
} {
"servers": {
"nigelcox98-breaking-changes": {
"type": "http",
"url": "https://agentdataapi.onrender.com/mcp"
}
}
} [mcp_servers.nigelcox98-breaking-changes] url = "https://agentdataapi.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nigelcox98-breaking-changes": {
"type": "remote",
"url": "https://agentdataapi.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add nigelcox98-breaking-changes --url 'https://agentdataapi.onrender.com/mcp' --transport streamable-http
mcp_servers:
nigelcox98-breaking-changes:
url: "https://agentdataapi.onrender.com/mcp" {
"McpServers": {
"nigelcox98-breaking-changes": {
"Transport": "http",
"Url": "https://agentdataapi.onrender.com/mcp"
}
}
} assistant mcp add nigelcox98-breaking-changes -t streamable-http -u 'https://agentdataapi.onrender.com/mcp'
{
"mcpServers": {
"nigelcox98-breaking-changes": {
"type": "http",
"url": "https://agentdataapi.onrender.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://agentdataapi.onrender.com/mcp/ · Declared URL https://agentdataapi.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentdataapi.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentdataapi.onrender.com/mcp | Redirected | 307 | https://agentdataapi.onrender.com/mcp/ |
| streamable-http · followed | https://agentdataapi.onrender.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://agentdataapi.onrender.com/mcp | HTTPS enforced | 301 | https://agentdataapi.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_upgrade_safety ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | – |
| target_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_breaking_changes ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | – |
| version | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_packages ~41
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the Breaking Changes & Migration Data MCP server?
Breaking Changes & Migration Data is an MCP server listed in the public MCP registry as io.github.nigelcox98/breaking-changes. What breaks when you upgrade a package, and what to use instead - from official docs. This page covers its hosted endpoint (https://agentdataapi.onrender.com/mcp).
Is the Breaking Changes & Migration Data MCP server safe to use?
Breaking Changes & Migration Data scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Breaking Changes & Migration Data MCP server expose?
Breaking Changes & Migration Data exposes 3 tools: list_packages, get_breaking_changes, check_upgrade_safety. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.
Does the Breaking Changes & Migration Data MCP server require authentication?
No. We connected to Breaking Changes & Migration Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Breaking Changes & Migration Data MCP server still maintained?
Breaking Changes & Migration Data is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.