Source note · Model Context Protocol transports compared
In MCP revision 2025-11-25, a Streamable HTTP disconnection SHOULD NOT be interpreted as the client cancelling its request, and to cancel the client SHOULD explicitly send an MCP CancelledNotification.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- cancellation
- Deployment
- remote-http
- Region
- not restricted
- Release range
- MCP revisions 2025-03-26 through 2025-11-25 (legacy)
- Checked
- 2026-09-30
Sources
- Transports - MCP specification revision 2025-11-25 — Model Context Protocol project · tier 1 standards and regulators · section Streamable HTTP, subsection Sending Messages to the Server, item 6, Disconnection bullets
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-cancel. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-cancel
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-v2025-11-25-cancel,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-v2025-11-25-cancel},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-v2025-11-25-cancel},
note = {Source note mcp-transport-differences-v2025-11-25-cancel, checked 2026-09-30}
}