678 pages for status.

Authorization Model Context Protocol · in the page specification/2025-03-26/basic/authorization …PS URLs ### Error Handling Servers **MUST** return appropriate HTTP status codes for authorization errors: | Status Code | Description | Usage | | - | - | - | | 401 | Unauthorized | Authorization r… Transports Model Context Protocol · in the page specification/2025-03-26/basic/transports …* If the server accepts the input, the server **MUST** return HTTP status code 202 Accepted with no body. * If the server cannot accept the input, it **MUST** return an HTTP error status co… Progress Model Context Protocol · in the page specification/2025-03-26/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… Key Changes Model Context Protocol · in the page specification/2025-03-26/changelog …dded `message` field to `ProgressNotification` to provide descriptive status updates * Added support for audio data, joining the existing text and image content types * Added `completions` capability… Architecture Model Context Protocol · in the page specification/2025-06-18/architecture/index …ns Server--)Client: Resource updates Client--)Server: Status changes end Host->>Client: Terminate Client->>-Server: End session deactivate Server ``` Each capability… Authorization Model Context Protocol · in the page specification/2025-06-18/basic/authorization …tokens. ### Error Handling Servers **MUST** return appropriate HTTP status codes for authorization errors: | Status Code | Description | Usage | | - | - | - | | 401 | Unauthorized | Authorization r… Transports Model Context Protocol · in the page specification/2025-06-18/basic/transports …* If the server accepts the input, the server **MUST** return HTTP status code 202 Accepted with no body. * If the server cannot accept the input, it **MUST** return an HTTP error status co… Progress Model Context Protocol · in the page specification/2025-06-18/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-11-25/architecture/index …ns Server--)Client: Resource updates Client--)Server: Status changes end Host->>Client: Terminate Client->>-Server: End session deactivate Server ``` Each capability… Authorization Model Context Protocol · in the page specification/2025-11-25/basic/authorization …tokens. ## Error Handling Servers **MUST** return appropriate HTTP status codes for authorization errors: | Status Code | Description | Usage | | - | - | - | | 401 | Unauthorized | Authorization r… Transports Model Context Protocol · in the page specification/2025-11-25/basic/transports …* If the server accepts the input, the server **MUST** return HTTP status code 202 Accepted with no body. * If the server cannot accept the input, it **MUST** return an HTTP error status co… Progress Model Context Protocol · in the page specification/2025-11-25/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… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …sk": { "taskId": "786512e2-9e0d-44bd-8f29-789f320fe840", "status": "working", "statusMessage": "The operation is now in progress.", "createdAt": "2025-11-25T10:30:00Z", "… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …collected (e.g., the user's display name via form mode elicitation) * Status of resource access (e.g., API keys or a payment flow via URL mode elicitation) Servers implementing elicitation **MUST** s… Schema Reference Model Context Protocol · in the page specification/2025-11-25/schema …ams">params</a></p></aside></section> </div> ## `notifications/tasks/status` <div class="type"> ### `TaskStatusNotification` <div class="tsd-signature"><span class="tsd-signature-keyword">inter… Authorization Model Context Protocol · in the page specification/2026-07-28/basic/authorization/index …irement. ## Error Handling Servers **MUST** return appropriate HTTP status codes for authorization errors: | Status Code | Description | Usage | | - | - | - | | 401 | Unauthorized | Authorization r… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …JSON-RPC error code `-32602` (Invalid params). On HTTP, the response status **MUST** be `400 Bad Request`. Clients **SHOULD** include `io.modelcontextprotocol/clientInfo` on every request unless spe… Progress Model Context Protocol · in the page specification/2026-07-28/basic/patterns/progress …essages. The server **MAY** send progress notifications to report the status of requests the client has issued. ## Progress Flow When a client wants to *receive* progress updates for a request, it i… Streamable HTTP Model Context Protocol · in the page specification/2026-07-28/basic/transports/streamable-http …tion*: * If the server accepts it, the server **MUST** return HTTP status code `202 Accepted` with no body. * If the server cannot accept it, it **MUST** return an HTTP error status co… Key Changes Model Context Protocol · in the page specification/2026-07-28/changelog …seps/` directory, PR-derived numbering, sponsor responsibilities, and status management via PR labels ([SEP-1850](https://github.com/modelcontextprotocol/specification/pull/1850)). ## Full changelog… Schema Reference Model Context Protocol · in the page specification/2026-07-28/schema …e required headers are missing or malformed. For HTTP, the response status code MUST be <code>400 Bad Request</code>.</p> </div> <div class="tsd-comment tsd-typography"> <details class="tsd-tag-exam… Discovery Model Context Protocol · in the page specification/2026-07-28/server/discover …kward-compatibility probe.** On stdio, there is no per-request HTTP status code to drive fallback. A client that supports both modern (per-request `_meta`) and legacy (`initialize` handshake) serv… Authorization Model Context Protocol · in the page specification/draft/basic/authorization/index …irement. ## Error Handling Servers **MUST** return appropriate HTTP status codes for authorization errors: | Status Code | Description | Usage | | - | - | - | | 401 | Unauthorized | Authorization r… Overview Model Context Protocol · in the page specification/draft/basic/index …JSON-RPC error code `-32602` (Invalid params). On HTTP, the response status **MUST** be `400 Bad Request`. Clients **SHOULD** include `io.modelcontextprotocol/clientInfo` on every request unless spe… Progress Model Context Protocol · in the page specification/draft/basic/patterns/progress …essages. The server **MAY** send progress notifications to report the status of requests the client has issued. ## Progress Flow When a client wants to *receive* progress updates for a request, it i… Streamable HTTP Model Context Protocol · in the page specification/draft/basic/transports/streamable-http …tion*: * If the server accepts it, the server **MUST** return HTTP status code `202 Accepted` with no body. * If the server cannot accept it, it **MUST** return an HTTP error status co… Schema Reference Model Context Protocol · in the page specification/draft/schema …e required headers are missing or malformed. For HTTP, the response status code MUST be <code>400 Bad Request</code>.</p> </div> <div class="tsd-comment tsd-typography"> <details class="tsd-tag-exam… Discovery Model Context Protocol · in the page specification/draft/server/discover …kward-compatibility probe.** On stdio, there is no per-request HTTP status code to drive fallback. A client that supports both modern (per-request `_meta`) and legacy (`initialize` handshake) serv…