380 pages for shared.

SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …icy permits deprecation on adoption grounds, but the project has no shared telemetry today. Until one exists, this criterion relies on SDK maintainer attestation. * **Feature maturity tiers.** Thi… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …t will fail, and the same refresh applies. This extension defines no shared version or cache token that would let a host determine whether a directory result and an entry describe the same snapshot o… SEP-414: Document OpenTelemetry Trace Context Propagation Conventions Model Context Protocol · in the page seps/414-request-meta …github.com/stacklok/toolhive/issues/3399). If we don't document this shared concern, differing interpretations could materialize, such as namespacing traceparent like `io.modelcontextprotocol.tracepa… Specification Enhancement Proposals (SEPs) Model Context Protocol · in the page seps/index …k | 2025-07-22 | | [SEP-994](https://modelcontextprotocol.io/seps/994-shared-communication-practicesguidelines.md) | Shared Communication Practices/Guidelines | Final | Process | 2025-07-17 | | [SEP-9… Architecture Model Context Protocol · in the page specification/2024-11-05/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Specification Model Context Protocol · in the page specification/2024-11-05/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/2024-11-05/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Architecture Model Context Protocol · in the page specification/2025-03-26/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Specification Model Context Protocol · in the page specification/2025-03-26/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/2025-03-26/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Architecture Model Context Protocol · in the page specification/2025-06-18/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Specification Model Context Protocol · in the page specification/2025-06-18/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/2025-06-18/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Architecture Model Context Protocol · in the page specification/2025-11-25/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Key Changes Model Context Protocol · in the page specification/2025-11-25/changelog …/modelcontextprotocol/modelcontextprotocol/issues/932)). 2. Establish shared communication practices and guidelines for the MCP community ([SEP-994](https://github.com/modelcontextprotocol/modelcontex… Specification Model Context Protocol · in the page specification/2025-11-25/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/2025-11-25/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Architecture Model Context Protocol · in the page specification/2026-07-28/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Multi Round-Trip Requests Model Context Protocol · in the page specification/2026-07-28/basic/patterns/mrtr …standardized way to handle these server-requests without requiring a shared storage layer across server instances or requiring stateful load balancing. The high level flow functions as follows: 1.… stdio Model Context Protocol · in the page specification/2026-07-28/basic/transports/stdio …notification referencing the request's ID. Because stdio is a single shared bidirectional channel, there is no per-request stream to close. Servers **SHOULD** stop work on a cancelled request as soon… Key Changes Model Context Protocol · in the page specification/2026-07-28/changelog …ce polling; `cacheScope` (`"public"` or `"private"`) controls whether shared intermediaries may cache the response. Both fields complement existing `listChanged` notifications ([SEP-2549](https://gith… Specification Model Context Protocol · in the page specification/2026-07-28/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/2026-07-28/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Caching Model Context Protocol · in the page specification/2026-07-28/server/utilities/caching …lic"` | The response does not contain user-specific data. Any client, shared gateway, or caching proxy **MAY** store and serve the cached response to any user. | | `"private"` | The response contains… Architecture Model Context Protocol · in the page specification/draft/architecture/index …ty in isolation * Multiple servers can be combined seamlessly * Shared protocol enables interoperability * Modular design supports extensibility 3. **Servers should not be able to read the w… Multi Round-Trip Requests Model Context Protocol · in the page specification/draft/basic/patterns/mrtr …standardized way to handle these server-requests without requiring a shared storage layer across server instances or requiring stateful load balancing. The high level flow functions as follows: 1.… stdio Model Context Protocol · in the page specification/draft/basic/transports/stdio …notification referencing the request's ID. Because stdio is a single shared bidirectional channel, there is no per-request stream to close. Servers **SHOULD** stop work on a cancelled request as soon… Specification Model Context Protocol · in the page specification/draft/index …ccess and operations * Users must retain control over what data is shared and what actions are taken * Implementors should provide clear UIs for reviewing and authorizing activities 2. **Data P… Resources Model Context Protocol · in the page specification/draft/server/resources …ources with an [XDG MIME type](https://specifications.freedesktop.org/shared-mime-info-spec/0.14/ar01s02.html#id-1.3.14), like `inode/directory`, to represent non-regular files (such as directories) t… Caching Model Context Protocol · in the page specification/draft/server/utilities/caching …lic"` | The response does not contain user-specific data. Any client, shared gateway, or caching proxy **MAY** store and serve the cached response to any user. | | `"private"` | The response contains…