MODEL CONTEXT PROTOCOL
MCP: versions and changes
No Hostbip MCP endpoint, callable tool catalogue or verified client configuration is connected in this source release.
Match documentation to the running service.
The MCP protocol revision and the Hostbip service release are separate version identifiers. A backend can support more than one protocol revision, but that compatibility must be tested and documented.
Pin the actual contract
The research baseline for this project is the official MCP documentation consulted on 10 September 2026, including the 2026-07-28 revision. That research does not assert that Hostbip or every client supports that revision. The service must publish its actual supported revisions and tested client versions.
Keep wire examples revision-specific
Do not mix discovery, initialization, request metadata or transport examples from different protocol eras. Existing clients can require earlier revisions. Use the actual backend and SDK behavior as the implementation contract.
Release notes
A release should identify additions, permission changes, breaking changes, migration steps, deprecations and known limitations. Historical documentation must stay associated with its original release.
Guides are editorial. Backend permissions and technical contracts remain authoritative.
Integration support ↗