678 pages for env.

SEP-2322: Multi Round-Trip Requests Model Context Protocol · in the page seps/2322-MRTR …ansport's dependence on SSE streams, which cause problems in a lot of environments that cannot support long-lived connections. This proposed way of handling server-initiated requests will replace the… SEP-2468: Recommend Issuer (iss) Parameter in MCP Auth Responses Model Context Protocol · in the page seps/2468-recommend-issuer-claim-for-auth …ssuer, improving protocol robustness in multi‑identity provider (IdP) environments. This SEP follows the specifications defined in [RFC9207](https://datatracker.ietf.org/doc/rfc9207/). ## Motivation… SEP-2577: Deprecate Roots, Sampling, and Logging Model Context Protocol · in the page seps/2577-deprecate-roots-sampling-and-logging …ed through tool parameters, resource URIs, server configuration, or environment variables — all of which are more explicit. ### Sampling Sampling allows servers to request LLM completions from t… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …ting elevated access on the host, not declaring a property of its own environment. Approval of a skill never extends to the frontmatter of any other `SKILL.md` within its file space: a nested skill's… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …et` for the returned `taskId` would resolve. In eventually-consistent environments, the server **MUST** wait for consistency before responding. This requirement eliminates the need for clients to spec… SEP-414: Document OpenTelemetry Trace Context Propagation Conventions Model Context Protocol · in the page seps/414-request-meta …ns should follow existing data-handling guidance appropriate to their environment. ## Reference Implementation Existing implementations using this pattern: * [C# SDK instrumentation](https://github… SEP-985: Align OAuth 2.0 Protected Resource Metadata with RFC 9728 Model Context Protocol · in the page seps/985-align-oauth-20-protected-resource-metadata-with-rf …FC compliance. ## Rationale Many large-scale, dynamic, multi-tenant environments rely on a centralized authentication service separate from the backend resource servers. In such deployments, injecti… SEP-990: Enable enterprise IdP policy controls during MCP OAuth flows Model Context Protocol · in the page seps/990-enable-enterprise-idp-policy-controls-during-mcp-o …ecure and interoperable authorization of MCP clients within corporate environments, leveraging existing enterprise identity infrastructure. * For end users, this removes the need to manually connect… Ping Model Context Protocol · in the page specification/2024-11-05/basic/utilities/ping …be configurable * Timeouts **SHOULD** be appropriate for the network environment * Excessive pinging **SHOULD** be avoided to reduce network overhead ## Error Handling * Timeouts **SHOULD** be trea… Authorization Model Context Protocol · in the page specification/2025-03-26/basic/authorization …ollow this specification, and instead retrieve credentials from the environment. * Implementations using alternative transports **MUST** follow established security best practices for their protoc… Overview Model Context Protocol · in the page specification/2025-03-26/basic/index …follow this specification, and instead retrieve credentials from the environment. Additionally, clients and servers **MAY** negotiate their own custom authentication and authorization strategies. F… Ping Model Context Protocol · in the page specification/2025-03-26/basic/utilities/ping …be configurable * Timeouts **SHOULD** be appropriate for the network environment * Excessive pinging **SHOULD** be avoided to reduce network overhead ## Error Handling * Timeouts **SHOULD** be trea… Authorization Model Context Protocol · in the page specification/2025-06-18/basic/authorization …ollow this specification, and instead retrieve credentials from the environment. * Implementations using alternative transports **MUST** follow established security best practices for their protoc… Overview Model Context Protocol · in the page specification/2025-06-18/basic/index …follow this specification, and instead retrieve credentials from the environment. Additionally, clients and servers **MAY** negotiate their own custom authentication and authorization strategies. F… Ping Model Context Protocol · in the page specification/2025-06-18/basic/utilities/ping …be configurable * Timeouts **SHOULD** be appropriate for the network environment * Excessive pinging **SHOULD** be avoided to reduce network overhead ## Error Handling * Timeouts **SHOULD** be trea… Authorization Model Context Protocol · in the page specification/2025-11-25/basic/authorization …ollow this specification, and instead retrieve credentials from the environment. * Implementations using alternative transports **MUST** follow established security best practices for their protoc… Overview Model Context Protocol · in the page specification/2025-11-25/basic/index …follow this specification, and instead retrieve credentials from the environment. Additionally, clients and servers **MAY** negotiate their own custom authentication and authorization strategies. F… Ping Model Context Protocol · in the page specification/2025-11-25/basic/utilities/ping …be configurable * Timeouts **SHOULD** be appropriate for the network environment * Excessive pinging **SHOULD** be avoided to reduce network overhead ## Error Handling * Timeouts **SHOULD** be trea… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …ng is not practical for all applications. Some MCP servers operate in environments without authorization, such as single-user tools, or use transports that don't support authorization. In these scenar… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …elicitation request. 4. **SHOULD** use HTTPS URLs for non-development environments. These server requirements ensure that client implementations have clear rules about when to present a URL to the us… Authorization Model Context Protocol · in the page specification/2026-07-28/basic/authorization/index …ollow this specification, and instead retrieve credentials from the environment. * Implementations using alternative transports **MUST** follow established security best practices for their protoc… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …follow this specification, and instead retrieve credentials from the environment. Additionally, clients and servers **MAY** negotiate their own custom authentication and authorization strategies. F… Overview Model Context Protocol · in the page specification/2026-07-28/basic/transports/index …lds. A binding **MAY** additionally mirror selected body fields into envelope metadata. The Streamable HTTP transport mirrors them into [HTTP headers](/specification/2026-07-28/basic/transports/strea… Elicitation Model Context Protocol · in the page specification/2026-07-28/client/elicitation …elicitation request. 4. **SHOULD** use HTTPS URLs for non-development environments. These server requirements ensure that client implementations have clear rules about when to present a URL to the us… Authorization Model Context Protocol · in the page specification/draft/basic/authorization/index …ollow this specification, and instead retrieve credentials from the environment. * Implementations using alternative transports **MUST** follow established security best practices for their protoc… Overview Model Context Protocol · in the page specification/draft/basic/index …follow this specification, and instead retrieve credentials from the environment. Additionally, clients and servers **MAY** negotiate their own custom authentication and authorization strategies. F… Overview Model Context Protocol · in the page specification/draft/basic/transports/index …lds. A binding **MAY** additionally mirror selected body fields into envelope metadata. The Streamable HTTP transport mirrors them into [HTTP headers](/specification/draft/basic/transports/streamable… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …elicitation request. 4. **SHOULD** use HTTPS URLs for non-development environments. These server requirements ensure that client implementations have clear rules about when to present a URL to the us…