Latest

MCP Uses Capability Negotiation to Let Clients and Servers Evolve Independently

According to Model Context Protocol, clients and servers explicitly declare supported features at session initialization, and those declared capabilities determine which protocol features and primitives are available—enabling independent evolution while retaining backwards compatibility within the declared feature set.

What MCP actually standardizes

According to the MCP specification, MCP standardizes a client-host-server architecture built on JSON-RPC, providing a stateful session protocol focused on context exchange and sampling coordination between clients and servers. Each host process manages multiple client instances, and each client maintains exactly one connection to one server—so the topology is explicit and bounded.

The specification also defines capability negotiation: both clients and servers explicitly declare their supported features at session initialization, and those declared capabilities determine which protocol features and primitives are available for that session. This is the mechanism that allows servers and clients to evolve independently while retaining backwards compatibility—at least within the declared feature set.

What the specification does not guarantee

MCP's specification describes intended design properties—such as security boundary isolation and composability across servers—as architectural goals. The MCP specification states that the architecture enables integration while "maintaining clear security boundaries and isolating concerns," but this is a vendor design claim, not an independently verified result. Whether any given implementation actually enforces those boundaries depends on the host and remains outside what the protocol text can guarantee.

Performance characteristics, real-world adoption breadth, and regional service availability are not addressed in the specification and have not been independently verified by Chooscope. The practical question to hold in reserve: does the client or host you are evaluating actually implement the full capability negotiation and isolation model the spec describes, or a subset of it? That gap—between protocol text and running implementation—is where evaluation work begins.

Sources

  1. Model Context Protocol — 2026-10-18

Change history

  • rev.1Published

Display language

Related