Source note · Model Context Protocol transports compared
Per the MCP 2026-07-28 compatibility matrix, a legacy client against a modern-only server fails: on stdio the server rejects initialize with an implementation-defined JSON-RPC error, and on HTTP the request lacks the required headers and is rejected with 400 Bad Request; legacy clients have no fall-forward mechanism.
Checked 2026-09-30
- Vendor
- Model Context Protocol project
- Product
- MCP specification
- Subsystem
- backward compatibility
- Deployment
- local-subprocess, remote-http
- Region
- not restricted
- Release range
- MCP revision 2026-07-28
- Checked
- 2026-09-30
Sources
- Model Context Protocol specification 2026-07-28, Versioning and Compatibility — Model Context Protocol project · tier 1 standards and regulators · subsection Compatibility Matrix, row Legacy client / Modern server
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-legacy-client-modern-srv. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-legacy-client-modern-srv
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-legacy-client-modern-srv,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-legacy-client-modern-srv},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-legacy-client-modern-srv},
note = {Source note mcp-transport-differences-legacy-client-modern-srv, checked 2026-09-30}
}