MCP tool-contract drift between two versions
mcp_driftWhat moved in an MCP server's tool contract between two versions: tools removed, parameters that became required, types narrowed, and annotation flips. Two findings here have no npm equivalent and are why this exists. SILENT DRIFT is a schema that changed while its description stayed byte-identical, invisible to anyone reading a changelog. PRIVILEGE WIDENING is a tool that stopped being read-only or started being destructive, which does not break anything and is worse than a break. Use before upgrading a server an agent depends on.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"server": "<server>",
"fromVersion": "<fromVersion>",
"toVersion": "<toVersion>"
},
"name": "mcp_drift"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server | Yes | npm package name of the MCP server | |
| toVersion | Yes | Version you are moving to | |
| fromVersion | Yes | Version you are on |