529 pages for wait.

How to Authenticate When Publishing to the Official MCP Registry Model Context Protocol · in the page registry/authentication …m/login/device 2. Enter code: ABCD-1234 3. Authorize this application Waiting for authorization... ``` Visit the link, follow the prompts, and enter the authorization code that was printed in the ter… Quickstart: Publish an MCP Server to the MCP Registry Model Context Protocol · in the page registry/quickstart …m/login/device 2. Enter code: ABCD-1234 3. Authorize this application Waiting for authorization... ``` Visit the link, follow the prompts, and enter the authorization code that was printed in the ter… 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 …the defaults setup ``` ```typescript theme={null} const response = await client.request("elicitation/create", { message: "Configure email reply", requestedSchema: { type: "object", prope… 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 …ause delivery of the notification is not guaranteed, clients must not wait indefinitely for a notification from the server. ```json theme={null} { "jsonrpc": "2.0", "method": "notifications/elici… SEP-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …ls the tool once before ending its conversation turn, claiming to be "waiting" before calling the tool again. It cannot resume until receiving a new user message. This also complicates expiration time… SEP-1699: Support SSE polling via server-side disconnect Model Context Protocol · in the page seps/1699-support-sse-polling-via-server-side-disconnect …0name%20is%20%22retry%22) field indicating how long the client should wait before reconnecting. Clients MUST respect the `retry` field. ## Rationale Servers may disconnect at will, avoiding long-run… SEP-1850: PR-Based SEP Workflow Model Context Protocol · in the page seps/1850-pr-based-sep-workflow …and update the header (`SEP-{PR-number}` and `PR: #{PR-number}`) 5. **Wait for sponsor assignment**: Once a sponsor agrees, they will assign themselves and update the status to `Draft` ### 3. Sponsor… SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 Model Context Protocol · in the page seps/2106-json-schema-2020-12 …unchanged. Code such as: ```typescript theme={null} const result = await client.callTool({ name: "get_weather", arguments: { ... } }); const temp = result.structuredContent?.temperature; // p… SEP-2127: MCP Server Cards - HTTP Server Discovery Model Context Protocol · in the page seps/2127-mcp-server-cards …it defines how static claims relate to runtime variants. ### Why Not Wait for Primitives? The debate around primitives should not delay server card adoption. Discovery (knowing that a server exists,… 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 …one server push async def background_task(): while True: await asyncio.sleep(60) # Try to initiate sampling without any client request context await session.create_message(… SEP-2322: Multi Round-Trip Requests Model Context Protocol · in the page seps/2322-MRTR …* Server may need to continue processing in the background while waiting for more info from the client, in which case server-side state is needed to track that ongoing processing. * Examp… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …side**: enumerate and fetch skills: ```python theme={null} skills = await client.list_skills() # calls skills/list, paginating; may be empty entry = await client.get_skill( "skill:/… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …kingTask extends Task { status: "working"; } /** * A task that is waiting for input from the client. * Used by tasks/get and notifications/tasks. */ export interface InputRequiredTask extends Ta… Specification Enhancement Proposals (SEPs) Model Context Protocol · in the page seps/index …y for formal review by Core Maintainers | | Accepted | SEP accepted, awaiting reference implementation | | Final | SEP finalized with reference implementation complete | | Rejected | SEP rejected by C… Lifecycle Model Context Protocol · in the page specification/2024-11-05/basic/lifecycle …First, closing the input stream to the child process (the server) 2. Waiting for the server to exit, or sending `SIGTERM` if the server does not exit within a reasonable time 3. Sending `SIGKILL`… Lifecycle Model Context Protocol · in the page specification/2025-03-26/basic/lifecycle …First, closing the input stream to the child process (the server) 2. Waiting for the server to exit, or sending `SIGTERM` if the server does not exit within a reasonable time 3. Sending `SIGKILL`… Lifecycle Model Context Protocol · in the page specification/2025-06-18/basic/lifecycle …First, closing the input stream to the child process (the server) 2. Waiting for the server to exit, or sending `SIGTERM` if the server does not exit within a reasonable time 3. Sending `SIGKILL`… Lifecycle Model Context Protocol · in the page specification/2025-11-25/basic/lifecycle …First, closing the input stream to the child process (the server) 2. Waiting for the server to exit, or sending `SIGTERM` if the server does not exit within a reasonable time 3. Sending `SIGKILL`… Transports Model Context Protocol · in the page specification/2025-11-25/basic/transports …g the connection. The client **MUST** respect the `retry` field, waiting the given number of milliseconds before attempting to reconnect. * The SSE stream **SHOULD** eventually include a JSON-… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …o continue processing other requests or perform additional work while waiting for the task to complete. > > To support this pattern, servers can provide an optional `io.modelcontextprotocol/model-imme… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …notifications referencing unknown or already-completed IDs. * **MAY** wait for this notification to automatically retry requests that received a [URLElicitationRequiredError](#error-handling), update… Cancellation Model Context Protocol · in the page specification/2026-07-28/basic/patterns/cancellation …the timeout period, the sender **SHOULD** cancel the request and stop waiting for a response. As described in [Transport-Specific Cancellation](#transport-specific-cancellation), this means: * **Stre… stdio Model Context Protocol · in the page specification/2026-07-28/basic/transports/stdio …y: 1. Closing the input stream to the child process (the server). 2. Waiting for the server to exit. 3. If the server does not exit within a reasonable time, forcibly terminating the process using… Roots Model Context Protocol · in the page specification/2026-07-28/client/roots …to replay the initial call with an error message as the server is not waiting for a response with the `InputRequiredResult` pattern. ## Security Considerations 1. Clients **MUST**: * Only expose… Sampling Model Context Protocol · in the page specification/2026-07-28/client/sampling …o replay the initial call with an error message, as the server is not waiting for a response with the `InputRequiredResult` pattern. ## Security Considerations 1. Clients **SHOULD** implement user a… Cancellation Model Context Protocol · in the page specification/draft/basic/patterns/cancellation …the timeout period, the sender **SHOULD** cancel the request and stop waiting for a response. As described in [Transport-Specific Cancellation](#transport-specific-cancellation), this means: * **Stre… stdio Model Context Protocol · in the page specification/draft/basic/transports/stdio …y: 1. Closing the input stream to the child process (the server). 2. Waiting for the server to exit. 3. If the server does not exit within a reasonable time, forcibly terminating the process using… Roots Model Context Protocol · in the page specification/draft/client/roots …to replay the initial call with an error message as the server is not waiting for a response with the `InputRequiredResult` pattern. ## Security Considerations 1. Clients **MUST**: * Only expose… Sampling Model Context Protocol · in the page specification/draft/client/sampling …o replay the initial call with an error message, as the server is not waiting for a response with the `InputRequiredResult` pattern. ## Security Considerations 1. Clients **SHOULD** implement user a…