---
title: Expected change for MCP tool drift, plus release markers
description: Shipping a release that adds or rewords MCP tools opened a Tool Inventory Changed incident every time, with no way to say it was yours. Now owners and admins…
canonical: https://watchfor.io/changelog/2026-10-18-mcp-expected-change
---

[All updates](/changelog#2026-10-18-mcp-expected-change) ✨ New MCP API Oct 18, 2026 · v 11.4.2

# Expected change for MCP tool drift, plus release markers

Shipping a release that adds or rewords MCP tools opened a Tool Inventory Changed incident every time, with no way to say it was yours. Now owners and admins can mark the incident as an Expected change: it resolves, and the change shows as accepted in the drift timeline with who and why. Before a deploy, a release marker (POST /v1/monitors/{id}/expected-change) keeps drift quiet for up to an hour — downtime still alerts.

## In the API, MCP and A2A

- REST : POST /v1/incidents/{id}/expected-change accepts a drift incident; POST /v1/monitors/{id}/expected-change?window=N (1–60 minutes, default 15) sets a release marker.

- MCP : accept_expected_change and set_expected_change_window . A2A : the manage-incident skill takes action: "expected-change" .

- SDKs 0.18.0 (TypeScript, Python, Ruby): monitors.setExpectedChangeWindow() / set_expected_change_window and incidents.acceptExpectedChange() / accept_expected_change .

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-10-18-mcp-expected-change · Site guide: https://watchfor.io/llms.txt