Source note · Model Context Protocol transports compared
MCP revision 2026-07-28 defines no client-to-server notifications over Streamable HTTP: the only client-sent core notification, notifications/cancelled, is used only on stdio, and header requirements for notification POSTs are not defined by the revision.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- Streamable HTTP transport
- Deployment
- remote-http
- Region
- not restricted
- Release range
- MCP revision 2026-07-28
- Checked
- 2026-09-30
Sources
- Model Context Protocol specification 2026-07-28, Streamable HTTP — Model Context Protocol project · tier 1 standards and regulators · section Sending Messages, Note box after the numbered list
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-http-no-client-notifs. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-http-no-client-notifs
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-http-no-client-notifs,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-http-no-client-notifs},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-http-no-client-notifs},
note = {Source note mcp-transport-differences-http-no-client-notifs, checked 2026-09-30}
}