499 pages for force.

SEP-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …w agents cause cascading delays throughout this system, as agents are forced to wait on their peers to complete their work. ***Current Workaround:*** Not yet determined. ***Impact:*** Communication pa… SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 Model Context Protocol · in the page seps/2106-json-schema-2020-12 …sible** because `structuredContent` must be an object. Developers are forced to wrap arrays in unnecessary container objects: ```json theme={null} { "forecasts": [ { "hour": "09:00", "temp": 68… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …governance structure that allows for the repository maintainers to enforce structure and conformity to extensions. It avoids a failure case of different extensions in an area working in incompatible… SEP-2148: MCP Contributor Ladder Model Context Protocol · in the page seps/2148-contributor-ladder …ion only | | [**Community Moderator**](#community-moderators) | CoC enforcement and community health | Moderation rights on community platforms, incident handling | Parallel track — Member status + ap… SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …return a JSON-RPC error response. > **Note**: Intermediaries that enforce policy based on mirrored headers (e.g., routing or rate-limiting by tenant) SHOULD verify that the `MCP-Protocol-Version` he… SEP-2260: Require Server requests to be associated with a Client request. Model Context Protocol · in the page seps/2260-Require-Server-requests-to-be-associated-with-Client-requests …es outside notifications **MUST NOT** be implemented. Although not enforced in the current MCP Data Layer, logically these requests **MUST** be associated with a valid client-to-server JSON-RPC Reque… SEP-2484: Require Conformance Tests for Standards Track SEPs to Reach Final Status Model Context Protocol · in the page seps/2484-conformance-tests-required-for-final-seps …**Informational SEPs** (guidelines, best practices without normative force) * **Standards Track SEPs with no observable protocol behavior**, for example: * Documentation-only clarifications of exis… SEP-2567: Sessionless MCP via Explicit State Handles Model Context Protocol · in the page seps/2567-sessionless-mcp …lier on the hot path. The possibility that a server is session-scoped forces `O(subagents × servers)` calls to `tools/list`: every subagent, for every server, every time, even if the underlying tool s… SEP-2575: Make MCP Stateless Model Context Protocol · in the page seps/2575-stateless-mcp …none of which would have the correct session state. Operators are forced to implement complex and fragile solutions like sticky sessions, which bind a client to a specific server. This complica… SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …so serves as the historical record. The registry carries no normative force of its own; it is a derived view kept consistent with the per-feature notices and changelog entries, which are the normative… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …`size` lets a host budget a skill before fetching anything: it can enforce the [Limits](#limits) from the entry alone, decide whether a file is worth retrieving, and detect a truncated or padded read… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …`tasks/result` then blocks until the entire operation completes. This forces long-lived persistent connections that many clients and servers do not want to implement, and it conflicts with [SEP-2260](… SEP-986: Specify Format for Tool Names Model Context Protocol · in the page seps/986-specify-format-for-tool-names …implementation can be provided by updating the MCP core library to enforce the new tool name validation rules at registration time. Existing tools can be updated to provide aliases for their new conf… Architecture Model Context Protocol · in the page specification/2024-11-05/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Specification Model Context Protocol · in the page specification/2024-11-05/index …nto prompts ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i… Architecture Model Context Protocol · in the page specification/2025-03-26/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Authorization Model Context Protocol · in the page specification/2025-03-26/basic/authorization …ore tokens following OAuth 2.0 best practices 2. Servers **SHOULD** enforce token expiration and rotation 3. All authorization endpoints **MUST** be served over HTTPS 4. Servers **MUST** validate redi… Lifecycle Model Context Protocol · in the page specification/2025-03-26/basic/lifecycle …k is actually happening. However, implementations **SHOULD** always enforce a maximum timeout, regardless of progress notifications, to limit the impact of a misbehaving client or server. ## Error Ha… Specification Model Context Protocol · in the page specification/2025-03-26/index …nto prompts ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i… Architecture Model Context Protocol · in the page specification/2025-06-18/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Lifecycle Model Context Protocol · in the page specification/2025-06-18/basic/lifecycle …k is actually happening. However, implementations **SHOULD** always enforce a maximum timeout, regardless of progress notifications, to limit the impact of a misbehaving client or server. ## Error Ha… Specification Model Context Protocol · in the page specification/2025-06-18/index …nto prompts ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i… Architecture Model Context Protocol · in the page specification/2025-11-25/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Lifecycle Model Context Protocol · in the page specification/2025-11-25/basic/lifecycle …k is actually happening. However, implementations **SHOULD** always enforce a maximum timeout, regardless of progress notifications, to limit the impact of a misbehaving client or server. ## Error Ha… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …n attacks. ### Resource Management 1. Receivers **SHOULD**: 1. Enforce limits on concurrent tasks per requestor 2. Enforce maximum `ttl` durations to prevent indefinite resource retention 3… Sampling Model Context Protocol · in the page specification/2025-11-25/client/sampling …, and e.g. pass `toolChoice: {mode: "none"}` on the last iteration to force a final result) **Follow-up request (Server -> Client) with tool results:** ```json theme={null} { "jsonrpc": "2.0", "… Specification Model Context Protocol · in the page specification/2025-11-25/index …nto prompts ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i… Architecture Model Context Protocol · in the page specification/2026-07-28/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Client Registration Model Context Protocol · in the page specification/2026-07-28/basic/authorization/client-registration …ort OpenID Connect (OIDC) and Dynamic Client Registration, they may enforce additional constraints on redirect URIs based on the `application_type` parameter as defined in [OpenID Connect Dynamic Clie… Authorization Model Context Protocol · in the page specification/2026-07-28/basic/authorization/index …y (returning one missing scope, then another on the subsequent retry) forces multiple authorization round-trips for a single operation and degrades user experience. The required scopes may be determin… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …local `$ref`s but it **MUST** be disabled by default and **SHOULD** enforce an allowlist of hosts or at minimum reject loopback, link-local, and private network addresses, apply timeouts and size limi… Cancellation Model Context Protocol · in the page specification/2026-07-28/basic/patterns/cancellation …k is actually happening. However, implementations **SHOULD** always enforce a maximum timeout, regardless of progress notifications, to limit the impact of a misbehaving client or server. ## Behavior… Multi Round-Trip Requests Model Context Protocol · in the page specification/2026-07-28/basic/patterns/mrtr …consumed at most once > (e.g., one-time redemptions) **MUST** enforce that invariant server-side. 6. Servers **MUST** include at least one of `inputRequests` or `requestState` in every `InputRe… stdio Model Context Protocol · in the page specification/2026-07-28/basic/transports/stdio …he mechanism appropriate for the operating system. On POSIX systems, forced termination typically escalates from [`SIGTERM`][sigterm] to `SIGKILL`. On Windows, where POSIX signals are not available,… Streamable HTTP Model Context Protocol · in the page specification/2026-07-28/basic/transports/streamable-http …urn > a JSON-RPC error response. > [!NOTE] > > Intermediaries that enforce policy based on mirrored headers (e.g., routing > or rate-limiting by tenant) **SHOULD** verify that the `MCP-Protocol-Versi… Roots Model Context Protocol · in the page specification/2026-07-28/client/roots …ance rather than an access-control mechanism. The protocol does not enforce that servers stay within roots. Servers can request the list of roots from supporting clients. ## User Interaction Model R… Sampling Model Context Protocol · in the page specification/2026-07-28/client/sampling …, and e.g. pass `toolChoice: {mode: "none"}` on the last iteration to force a final result) **Follow-up input request (Server -> Client, delivered inside `InputRequiredResult.inputRequests`) with too… Specification Model Context Protocol · in the page specification/2026-07-28/index …ing its use ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i… Architecture Model Context Protocol · in the page specification/draft/architecture/index …instances * Controls client connection permissions and lifecycle * Enforces security policies and consent requirements * Handles user authorization decisions * Coordinates AI/LLM integration and samp… Client Registration Model Context Protocol · in the page specification/draft/basic/authorization/client-registration …ort OpenID Connect (OIDC) and Dynamic Client Registration, they may enforce additional constraints on redirect URIs based on the `application_type` parameter as defined in [OpenID Connect Dynamic Clie… Authorization Model Context Protocol · in the page specification/draft/basic/authorization/index …y (returning one missing scope, then another on the subsequent retry) forces multiple authorization round-trips for a single operation and degrades user experience. The required scopes may be determin… Overview Model Context Protocol · in the page specification/draft/basic/index …local `$ref`s but it **MUST** be disabled by default and **SHOULD** enforce an allowlist of hosts or at minimum reject loopback, link-local, and private network addresses, apply timeouts and size limi… Cancellation Model Context Protocol · in the page specification/draft/basic/patterns/cancellation …k is actually happening. However, implementations **SHOULD** always enforce a maximum timeout, regardless of progress notifications, to limit the impact of a misbehaving client or server. ## Behavior… Multi Round-Trip Requests Model Context Protocol · in the page specification/draft/basic/patterns/mrtr …consumed at most once > (e.g., one-time redemptions) **MUST** enforce that invariant server-side. 6. Servers **MUST** include at least one of `inputRequests` or `requestState` in every `InputRe… stdio Model Context Protocol · in the page specification/draft/basic/transports/stdio …he mechanism appropriate for the operating system. On POSIX systems, forced termination typically escalates from [`SIGTERM`][sigterm] to `SIGKILL`. On Windows, where POSIX signals are not available,… Streamable HTTP Model Context Protocol · in the page specification/draft/basic/transports/streamable-http …urn > a JSON-RPC error response. > [!NOTE] > > Intermediaries that enforce policy based on mirrored headers (e.g., routing > or rate-limiting by tenant) **SHOULD** verify that the `MCP-Protocol-Versi… Roots Model Context Protocol · in the page specification/draft/client/roots …ance rather than an access-control mechanism. The protocol does not enforce that servers stay within roots. Servers can request the list of roots from supporting clients. ## User Interaction Model R… Sampling Model Context Protocol · in the page specification/draft/client/sampling …, and e.g. pass `toolChoice: {mode: "none"}` on the last iteration to force a final result) **Follow-up input request (Server -> Client, delivered inside `InputRequiredResult.inputRequests`) with too… Specification Model Context Protocol · in the page specification/draft/index …ing its use ### Implementation Guidelines While MCP itself cannot enforce these security principles at the protocol level, implementors **SHOULD**: 1. Build robust consent and authorization flows i…