Source note · Model Context Protocol transports compared
The MCP 2026-07-28 Cancellation page says a server MUST send notifications/cancelled referencing a subscriptions/listen request ID when it tears down that subscription stream, and MUST NOT send notifications/cancelled for any other purpose.
disputed · Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- cancellation
- Deployment
- local-subprocess, remote-http
- Region
- not restricted
- Release range
- MCP revision 2026-07-28
- Status
- disputed
- Checked
- 2026-09-30
Sources
- Cancellation - MCP specification revision 2026-07-28 — Model Context Protocol project · tier 1 standards and regulators · introduction, second paragraph; section Behavior Requirements item 2
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-teardown-via-cancelled. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-teardown-via-cancelled
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-teardown-via-cancelled,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-teardown-via-cancelled},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-teardown-via-cancelled},
note = {Source note mcp-transport-differences-teardown-via-cancelled, checked 2026-09-30}
}