678 pages for status.

Extensions Overview Model Context Protocol · in the page extensions/overview …es and published packages need to clearly indicate their experimental status (e.g., in the README and package name) * [Core Maintainers](/community/contributor-ladder.md#core-maintainer) retain oversi… Tasks Model Context Protocol · in the page extensions/tasks/overview …sume polling with the same ID. * **Progress visibility.** Tasks carry status metadata (`working`, `input_required`, `completed`, `failed`, `cancelled`) and optional status messages, giving clients… The MCP Registry Moderation Policy Model Context Protocol · in the page registry/moderation-policy …## How Removal Works When we remove a server, we set the server's `status` to `"deleted"`, but the server's metadata remains accessible via the MCP Registry API. Aggregators may then remove the ser… MCP Registry Aggregators Model Context Protocol · in the page registry/registry-aggregators …o/v0.1/servers?updated_since=2025-10-23T00:00:00.000Z" ``` ## Server Status Server metadata is generally immutable, except for the `status` field which may be updated to, e.g., `"deprecated"` or `"d… SEP-1024: MCP Client Security Requirements for Local Server Installation Model Context Protocol · in the page seps/1024-mcp-client-security-requirements-for-local-server- …ion Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1034: Support default values for all primitive types in elicitation schemas Model Context Protocol · in the page seps/1034--support-default-values-for-all-primitive-types-in …mas Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1036: URL Mode Elicitation for secure out-of-band interactions Model Context Protocol · in the page seps/1036-url-mode-elicitation-for-secure-out-of-band-intera …ons Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1046: Support OAuth client credentials flow in authorization Model Context Protocol · in the page seps/1046-support-oauth-client-credentials-flow-in-authoriza …ion Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance Model Context Protocol · in the page seps/1302-formalize-working-groups-and-interest-groups-in-mc …nce Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1303: Input Validation Errors as Tool Execution Errors Model Context Protocol · in the page seps/1303-input-validation-errors-as-tool-execution-errors …ors Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1319: Decouple Request Payload from RPC Methods Definition Model Context Protocol · in the page seps/1319-decouple-request-payload-from-rpc-methods-definiti …ion Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1330: Elicitation Enum Schema Improvements and Standards Compliance Model Context Protocol · in the page seps/1330-elicitation-enum-schema-improvements-and-standards …nce Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …ols Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1613: Establish JSON Schema 2020-12 as Default Dialect for MCP Model Context Protocol · in the page seps/1613-establish-json-schema-2020-12-as-default-dialect-f …MCP Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …sks Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1699: Support SSE polling via server-side disconnect Model Context Protocol · in the page seps/1699-support-sse-polling-via-server-side-disconnect …ect Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1730: SDKs Tiering System Model Context Protocol · in the page seps/1730-sdks-tiering-system …tem Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1850: PR-Based SEP Workflow Model Context Protocol · in the page seps/1850-pr-based-sep-workflow …EP Workflow Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-1865: MCP Apps - Interactive User Interfaces for MCP Model Context Protocol · in the page seps/1865-mcp-apps-interactive-user-interfaces-for-mcp …CP Final Extensions Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2085: Governance Succession and Amendment Procedures Model Context Protocol · in the page seps/2085-governance-succession-and-amendment …Procedures Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 Model Context Protocol · in the page seps/2106-json-schema-2020-12 …-12 Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2127: MCP Server Cards - HTTP Server Discovery Model Context Protocol · in the page seps/2127-mcp-server-cards …ry Final Extensions Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …ons Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2148: MCP Contributor Ladder Model Context Protocol · in the page seps/2148-contributor-ladder …utor Ladder Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2149: MCP Group Governance and Charter Template Model Context Protocol · in the page seps/2149-working-group-charter-template …er Template Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2164: Standardize Resource Not Found Error Code Model Context Protocol · in the page seps/2164-resource-not-found-error …ode Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2207: OIDC-Flavored Refresh Token Guidance Model Context Protocol · in the page seps/2207-oidc-refresh-token-guidance …nce Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …ort Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… 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 …st. Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2322: Multi Round-Trip Requests Model Context Protocol · in the page seps/2322-MRTR …sts Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2468: Recommend Issuer (iss) Parameter in MCP Auth Responses Model Context Protocol · in the page seps/2468-recommend-issuer-claim-for-auth …ses Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2549: TTL for List Results Model Context Protocol · in the page seps/2549-TTL-for-list-results …lts Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2567: Sessionless MCP via Explicit State Handles Model Context Protocol · in the page seps/2567-sessionless-mcp …les Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2575: Make MCP Stateless Model Context Protocol · in the page seps/2575-stateless-mcp …ess Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2577: Deprecate Roots, Sampling, and Logging Model Context Protocol · in the page seps/2577-deprecate-roots-sampling-and-logging …ing Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …tion Policy Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …on Final Extensions Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …on Final Extensions Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-414: Document OpenTelemetry Trace Context Propagation Conventions Model Context Protocol · in the page seps/414-request-meta …ons Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-932: Model Context Protocol Governance Model Context Protocol · in the page seps/932-model-context-protocol-governance …Governance Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts Model Context Protocol · in the page seps/973-expose-additional-metadata-for-implementations-res …pts Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… 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 …728 Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-986: Specify Format for Tool Names Model Context Protocol · in the page seps/986-specify-format-for-tool-names …mes Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… 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 …ows Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents Model Context Protocol · in the page seps/991-enable-url-based-client-registration-using-oauth-c …nts Final Standards Track > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… SEP-994: Shared Communication Practices/Guidelines Model Context Protocol · in the page seps/994-shared-communication-practicesguidelines …/Guidelines Final Process > [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are >… Specification Enhancement Proposals (SEPs) Model Context Protocol · in the page seps/index …t Proposal ## Summary * **Final**: 43 ## All SEPs | SEP | Title | Status | Type | Created | | - | - | - | - | - | | [SEP-2663](/seps/2663-tasks-extension.md) | Tasks Extension | Final | Extensions… Architecture Model Context Protocol · in the page specification/2024-11-05/architecture/index …ns Server--)Client: Resource updates Client--)Server: Status changes end Host->>Client: Terminate Client->>-Server: End session deactivate Server ``` Each capability… Progress Model Context Protocol · in the page specification/2024-11-05/basic/utilities/progress …de can send progress notifications to provide updates about operation status. ## Progress Flow When a party wants to *receive* progress updates for a request, it includes a `progressToken` in the re… Architecture Model Context Protocol · in the page specification/2025-03-26/architecture/index …ns Server--)Client: Resource updates Client--)Server: Status changes end Host->>Client: Terminate Client->>-Server: End session deactivate Server ``` Each capability…