Source note · Model Context Protocol transports compared
In MCP revision 2026-07-28, clients SHOULD cache the modern-or-legacy era determination for the lifetime of the server process on stdio or of the origin on HTTP, and MAY persist it across restarts of the same server configuration, re-probing if the cached assumption later fails.
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 · section Backward Compatibility with Initialization-Based Versions, paragraph beginning The era determination
Cite this note
APA
WarmTransfer. (2026, September 30). Model Context Protocol transports compared: source note mcp-transport-differences-era-cache-scope. WarmTransfer. https://warmtransfer.net/knowledge/claims/mcp-transport-differences-era-cache-scope
BibTeX
@misc{warmtransfer-claim-mcp-transport-differences-era-cache-scope,
title = {Model Context Protocol transports compared: source note mcp-transport-differences-era-cache-scope},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/mcp-transport-differences-era-cache-scope},
note = {Source note mcp-transport-differences-era-cache-scope, checked 2026-09-30}
}