735 pages for term.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Authorization Security Considerations
Model Context Protocol · in the page
specification/2026-07-28/basic/authorization/security-considerations
…onfused Deputy Problem Attackers can exploit MCP servers acting as intermediaries to third-party APIs, leading to [confused deputy vulnerabilities](/docs/2026-07-28/tutorials/security/security_best_p…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…request. The `resultType` field is a string that clients can use to determine how to parse and handle the `result` object. * A `resultType` of `"complete"` indicates the request completed successfull…
Cancellation
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/cancellation
…otification to indicate that a request it previously issued should be terminated. A server **MUST** send `notifications/cancelled` referencing a `subscriptions/listen` request ID when it tears down t…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/index
…patterns without changes, because patterns are expressed entirely in terms of requests, responses, and notifications.
Multi Round-Trip Requests
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/mrtr
…rver with the parameters needed to perform the operation. 2. Server determines that additional information is required to fulfill the request and responds requesting more information. 3. Client gather…
Subscriptions
Model Context Protocol · in the page
specification/2026-07-28/basic/patterns/subscriptions
…treat as a trigger to reconnect. On **stdio**, if the connection is terminated and then re-established, the client **MUST** re-send `subscriptions/listen` to re-establish its subscriptions — the ser…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/index
…delivered, how request metadata is carried, and how cancellation and termination are signaled. It does not define what the messages mean: the [message patterns](/specification/2026-07-28/basic/patter…
stdio
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/stdio
…it. 3. If the server does not exit within a reasonable time, forcibly terminating the process using the mechanism appropriate for the operating system. On POSIX systems, forced termination typical…
Streamable HTTP
Model Context Protocol · in the page
specification/2026-07-28/basic/transports/streamable-http
…requests on SSE streams. * The final JSON-RPC *response* **SHOULD** terminate the stream. Long-lived notification streams are obtained by sending a [`subscriptions/listen`][subscriptions-listen] re…
Versioning and Compatibility
Model Context Protocol · in the page
specification/2026-07-28/basic/versioning
…ver: Client retries with a mutually supported version end ``` ## Terminology This page uses the following terms for interoperability across protocol revisions: * **Modern**: protocol versions t…
Key Changes
Model Context Protocol · in the page
specification/2026-07-28/changelog
…ll/414)). 3. Servers **SHOULD** return tools from `tools/list` in a deterministic order to enable client-side caching and improve LLM prompt cache hit rates. 4. Require standard MCP request headers (`…
Elicitation
Model Context Protocol · in the page
specification/2026-07-28/client/elicitation
…e outcome. When the client retries the original request, the server determines from the echoed `requestState` (or its own stored state) whether the out-of-band interaction has completed, and either re…
Sampling
Model Context Protocol · in the page
specification/2026-07-28/client/sampling
…thout communicating this to the server. For example, a client could determine that respecting this field in a particular request would require sharing sensitive information with a server, and constrai…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…hy"><p>Indicates the type of the result, which allows the client to determine how to parse the result object.</p> <p>Servers implementing this protocol version MUST include this field. For backwar…
Resources
Model Context Protocol · in the page
specification/2026-07-28/server/resources
…P are designed to be **application-driven**, with host applications determining how to incorporate context based on their needs. For example, applications could: * Expose resources through UI elemen…
Tools
Model Context Protocol · in the page
specification/2026-07-28/server/tools
…input, not connection state. Servers **SHOULD** return tools in a deterministic order (i.e., the same ordering across requests when the underlying set of tools has not changed). Deterministic orderi…
Pagination
Model Context Protocol · in the page
specification/2026-07-28/server/utilities/pagination
…token, representing a position in the result set * **Page size** is determined by the server, and clients **MUST NOT** assume a fixed page size ## Response Format Pagination starts when the server…
Authorization Server Discovery
Model Context Protocol · in the page
specification/draft/basic/authorization/authorization-server-discovery
…nts, as well as the discovery process through which MCP clients can determine authorization server endpoints and supported capabilities. ## Authorization Server Location MCP servers **MUST** impleme…
Authorization
Model Context Protocol · in the page
specification/draft/basic/authorization/index
…vers through OAuth 2.0 Protected Resource Metadata, and MCP clients determine authorization server endpoints and supported capabilities through authorization server metadata discovery. Implementations…
Authorization Security Considerations
Model Context Protocol · in the page
specification/draft/basic/authorization/security-considerations
…onfused Deputy Problem Attackers can exploit MCP servers acting as intermediaries to third-party APIs, leading to [confused deputy vulnerabilities](/docs/draft/tutorials/security/security_best_practi…
Overview
Model Context Protocol · in the page
specification/draft/basic/index
…request. The `resultType` field is a string that clients can use to determine how to parse and handle the `result` object. * A `resultType` of `"complete"` indicates the request completed successfull…
Cancellation
Model Context Protocol · in the page
specification/draft/basic/patterns/cancellation
…otification to indicate that a request it previously issued should be terminated. A server **MUST** send `notifications/cancelled` referencing a `subscriptions/listen` request ID when it tears down t…
Overview
Model Context Protocol · in the page
specification/draft/basic/patterns/index
…patterns without changes, because patterns are expressed entirely in terms of requests, responses, and notifications.
Multi Round-Trip Requests
Model Context Protocol · in the page
specification/draft/basic/patterns/mrtr
…rver with the parameters needed to perform the operation. 2. Server determines that additional information is required to fulfill the request and responds requesting more information. 3. Client gather…
Subscriptions
Model Context Protocol · in the page
specification/draft/basic/patterns/subscriptions
…treat as a trigger to reconnect. On **stdio**, if the connection is terminated and then re-established, the client **MUST** re-send `subscriptions/listen` to re-establish its subscriptions — the ser…
Overview
Model Context Protocol · in the page
specification/draft/basic/transports/index
…delivered, how request metadata is carried, and how cancellation and termination are signaled. It does not define what the messages mean: the [message patterns](/specification/draft/basic/patterns.md…
stdio
Model Context Protocol · in the page
specification/draft/basic/transports/stdio
…it. 3. If the server does not exit within a reasonable time, forcibly terminating the process using the mechanism appropriate for the operating system. On POSIX systems, forced termination typical…
Streamable HTTP
Model Context Protocol · in the page
specification/draft/basic/transports/streamable-http
…requests on SSE streams. * The final JSON-RPC *response* **SHOULD** terminate the stream. Long-lived notification streams are obtained by sending a [`subscriptions/listen`][subscriptions-listen] re…
Versioning and Compatibility
Model Context Protocol · in the page
specification/draft/basic/versioning
…ver: Client retries with a mutually supported version end ``` ## Terminology This page uses the following terms for interoperability across protocol revisions: * **Modern**: protocol versions t…
Elicitation
Model Context Protocol · in the page
specification/draft/client/elicitation
…e outcome. When the client retries the original request, the server determines from the echoed `requestState` (or its own stored state) whether the out-of-band interaction has completed, and either re…
Sampling
Model Context Protocol · in the page
specification/draft/client/sampling
…thout communicating this to the server. For example, a client could determine that respecting this field in a particular request would require sharing sensitive information with a server, and constrai…
Schema Reference
Model Context Protocol · in the page
specification/draft/schema
…hy"><p>Indicates the type of the result, which allows the client to determine how to parse the result object.</p> <p>Servers implementing this protocol version MUST include this field. For backwar…
Resources
Model Context Protocol · in the page
specification/draft/server/resources
…P are designed to be **application-driven**, with host applications determining how to incorporate context based on their needs. For example, applications could: * Expose resources through UI elemen…
Tools
Model Context Protocol · in the page
specification/draft/server/tools
…input, not connection state. Servers **SHOULD** return tools in a deterministic order (i.e., the same ordering across requests when the underlying set of tools has not changed). Deterministic orderi…
Pagination
Model Context Protocol · in the page
specification/draft/server/utilities/pagination
…token, representing a position in the result set * **Page size** is determined by the server, and clients **MUST NOT** assume a fixed page size ## Response Format Pagination starts when the server…