Source note · Model Context Protocol transports compared
The MCP 2026-07-28 Subscriptions page says that a server ending a subscription on its own initiative SHOULD send a successful subscriptions/listen response (resultType complete) before closing the stream, and describes no server-sent notifications/cancelled.
disputed · Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- subscriptions
- Deployment
- local-subprocess, remote-http
- Region
- not restricted
- Release range
- MCP revision 2026-07-28
- Status
- disputed
- Checked
- 2026-09-30
Sources
- Model Context Protocol specification 2026-07-28, Subscriptions — Model Context Protocol project · tier 1 standards and regulators · section Cancellation, second bullet, and subsection Graceful Closure
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-teardown-via-response. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-teardown-via-response
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-teardown-via-response,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-teardown-via-response},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-teardown-via-response},
note = {Source note mcp-transport-differences-teardown-via-response, checked 2026-09-30}
}