Source note · Model Context Protocol transports compared
A Streamable HTTP client written for MCP revisions 2025-03-26 through 2025-11-25 that drops and later resumes a response stream would, against a 2026-07-28-only server, have its in-flight request cancelled rather than preserved, because the newer revision treats stream closure as cancellation and ignores Last-Event-ID.
inferred · Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- cancellation
- Deployment
- remote-http
- Region
- not restricted
- Release range
- MCP revision 2026-07-28 interoperating with 2025-03-26 through 2025-11-25 behaviour
- Status
- inferred
- Checked
- 2026-09-30
Sources
- Model Context Protocol specification 2026-07-28, Streamable HTTP — Model Context Protocol project · tier 1 standards and regulators · section Cancellation; section Backward Compatibility, subsection Earlier Streamable HTTP Revisions
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-disconnect-semantics-flip. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-disconnect-semantics-flip
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-disconnect-semantics-flip,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-disconnect-semantics-flip},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-disconnect-semantics-flip},
note = {Source note mcp-transport-differences-disconnect-semantics-flip, checked 2026-09-30}
}