878 pages for check.

Authorization Model Context Protocol · in the page specification/2025-03-26/basic/authorization …(not a human) * For instance, an agent calls a secure MCP tool to check inventory at a specific store. No need to impersonate the end user. ### Example: authorization code grant This demons… Roots Model Context Protocol · in the page specification/2025-03-26/client/roots …e exposing * Monitor for root changes 2. Servers **SHOULD**: * Check for roots capability before usage * Handle root list changes gracefully * Respect root boundaries in operations * C… Resources Model Context Protocol · in the page specification/2025-03-26/server/resources …ta **MUST** be properly encoded 4. Resource permissions **SHOULD** be checked before operations Roots Model Context Protocol · in the page specification/2025-06-18/client/roots …e exposing * Monitor for root changes 2. Servers **SHOULD**: * Check for roots capability before usage * Handle root list changes gracefully * Respect root boundaries in operations * C… Schema Reference Model Context Protocol · in the page specification/2025-06-18/schema …-typography"><p>A ping, issued by either the server or the client, to check that the other party is still alive. The receiver must promptly respond, or else may be disconnected.</p> </div> <section cl… Resources Model Context Protocol · in the page specification/2025-06-18/server/resources …ta **MUST** be properly encoded 4. Resource permissions **SHOULD** be checked before operations Authorization Model Context Protocol · in the page specification/2025-11-25/basic/authorization …t_id_metadata_document_supported": true } ``` MCP clients **SHOULD** check for this capability and **MAY** fall back to Dynamic Client Registration or pre-registration if unavailable. ### Preregistr… Tasks Model Context Protocol · in the page specification/2025-11-25/basic/utilities/tasks …leted * `pollInterval`: Suggested time in milliseconds between status checks * `lastUpdatedAt`: ISO 8601 timestamp when the task status was last updated ### Task Status Tasks can be in one of the fo… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …me user who the elicitation was generated for. It would, for example, check that the user has a valid session cookie and that the session cookie is for the same user who was using the MCP client to ge… Roots Model Context Protocol · in the page specification/2025-11-25/client/roots …e exposing * Monitor for root changes 2. Servers **SHOULD**: * Check for roots capability before usage * Handle root list changes gracefully * Respect root boundaries in operations * C… Schema Reference Model Context Protocol · in the page specification/2025-11-25/schema …-typography"><p>A ping, issued by either the server or the client, to check that the other party is still alive. The receiver must promptly respond, or else may be disconnected.</p> </div> <section cl… Resources Model Context Protocol · in the page specification/2025-11-25/server/resources …ta **MUST** be properly encoded 4. Resource permissions **SHOULD** be checked before operations Client Registration Model Context Protocol · in the page specification/2026-07-28/basic/authorization/client-registration …t_id_metadata_document_supported": true } ``` MCP clients **SHOULD** check for this capability and **MAY** fall back to [Dynamic Client Registration](#dynamic-client-registration) or [pre-registratio… Multi Round-Trip Requests Model Context Protocol · in the page specification/2026-07-28/basic/patterns/mrtr …d attempt to modify it to alter server behavior, bypass authorization checks, or corrupt server logic. Servers **MUST** validate request state as described in the [server requirements](#server-require… Subscriptions Model Context Protocol · in the page specification/2026-07-28/basic/patterns/subscriptions …"file:///project/config.json"] } } } ``` The client **SHOULD** check the acknowledged filter against what it requested and handle any unsupported types gracefully. ## Receiving Notifications… Streamable HTTP Model Context Protocol · in the page specification/2026-07-28/basic/transports/streamable-http …or do not match the body, the client **SHOULD** call `tools/list` to check for changes to the tool's `inputSchema`, then retry the original request with the appropriate headers. #### Server Behavior… Elicitation Model Context Protocol · in the page specification/2026-07-28/client/elicitation …e user for whom the elicitation was generated. It would, for example, check that the user has a valid session cookie and that the session cookie is for the same user who was using the MCP client to ge… Roots Model Context Protocol · in the page specification/2026-07-28/client/roots …e exposing * Monitor for root changes 2. Servers **SHOULD**: * Check for roots capability before usage * Respect root boundaries in operations * Cache root information appropriately Resources Model Context Protocol · in the page specification/2026-07-28/server/resources …ta **MUST** be properly encoded 4. Resource permissions **SHOULD** be checked before operations 5. Servers **MUST** sanitize file paths to prevent directory traversal attacks when serving `file://`… Caching Model Context Protocol · in the page specification/2026-07-28/server/utilities/caching …tomatic background refetches. The TTL is a freshness hint: the client checks freshness when it needs the data, and re-fetches only if stale. Implementations that do choose to poll **MUST** apply jitte… Client Registration Model Context Protocol · in the page specification/draft/basic/authorization/client-registration …t_id_metadata_document_supported": true } ``` MCP clients **SHOULD** check for this capability and **MAY** fall back to [Dynamic Client Registration](#dynamic-client-registration) or [pre-registratio… Multi Round-Trip Requests Model Context Protocol · in the page specification/draft/basic/patterns/mrtr …d attempt to modify it to alter server behavior, bypass authorization checks, or corrupt server logic. Servers **MUST** validate request state as described in the [server requirements](#server-require… Subscriptions Model Context Protocol · in the page specification/draft/basic/patterns/subscriptions …"file:///project/config.json"] } } } ``` The client **SHOULD** check the acknowledged filter against what it requested and handle any unsupported types gracefully. ## Receiving Notifications… Streamable HTTP Model Context Protocol · in the page specification/draft/basic/transports/streamable-http …or do not match the body, the client **SHOULD** call `tools/list` to check for changes to the tool's `inputSchema`, then retry the original request with the appropriate headers. #### Server Behavior… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …e user for whom the elicitation was generated. It would, for example, check that the user has a valid session cookie and that the session cookie is for the same user who was using the MCP client to ge… Roots Model Context Protocol · in the page specification/draft/client/roots …e exposing * Monitor for root changes 2. Servers **SHOULD**: * Check for roots capability before usage * Respect root boundaries in operations * Cache root information appropriately Resources Model Context Protocol · in the page specification/draft/server/resources …ta **MUST** be properly encoded 4. Resource permissions **SHOULD** be checked before operations 5. Servers **MUST** sanitize file paths to prevent directory traversal attacks when serving `file://`… Caching Model Context Protocol · in the page specification/draft/server/utilities/caching …tomatic background refetches. The TTL is a freshness hint: the client checks freshness when it needs the data, and re-fetches only if stale. Implementations that do choose to poll **MUST** apply jitte…