One read of Model Context Protocolmcp-20261024T110706Z
303 pages moved out of 357 read.
Pages moved
303
significant first
Pages read
357
in this capture
Captured
11:07 UTC
Corpus hash
0c1129ea4604
full-sweep
What this read moved
276-300 of 303, page 12 of 13This capture is too large to show at once. Changes 276-300 of 303 are below, significant first; the rest are on the following screens.
specification/2025-03-26/architecture/index Changed · +2 / -2 lines
from line 158
158158Each capability unlocks specific protocol features for use during the session. For
159159example:
160160
161* Implemented [server features](/specification/2025-03-26/server.md) must be advertised in the
161* Implemented [server features](https://modelcontextprotocol.io/specification/2025-03-26/server.md) must be advertised in the
162162 server's capabilities
163163* Emitting resource subscription notifications requires the server to declare
164164 subscription support
165165* Tool invocation requires the server to declare tool capabilities
166* [Sampling](/specification/2025-03-26/client/sampling.md) requires the client to declare support in its
166* [Sampling](https://modelcontextprotocol.io/specification/2025-03-26/client/sampling.md) requires the client to declare support in its
167167 capabilities
168168
169169This capability negotiation ensures clients and servers have a clear understanding of
specification/2025-03-26/basic/index Changed · +1 / -1 lines
from line 96
9696
9797## Auth
9898
99MCP provides an [Authorization](/specification/2025-03-26/basic/authorization.md) framework for use with HTTP.
99MCP provides an [Authorization](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization.md) framework for use with HTTP.
100100Implementations using an HTTP-based transport **SHOULD** conform to this specification,
101101whereas implementations using STDIO transport **SHOULD NOT** follow this specification,
102102and instead retrieve credentials from the environment.
specification/2025-03-26/client/roots Changed · +1 / -1 lines
from line 21
2121## Capabilities
2222
2323Clients that support roots **MUST** declare the `roots` capability during
24[initialization](/specification/2025-03-26/basic/lifecycle.md#initialization):
24[initialization](https://modelcontextprotocol.io/specification/2025-03-26/basic/lifecycle.md#initialization):
2525
2626```json theme={null}
2727{
specification/2025-03-26/client/sampling Changed · +1 / -1 lines
from line 30
3030## Capabilities
3131
3232Clients that support sampling **MUST** declare the `sampling` capability during
33[initialization](/specification/2025-03-26/basic/lifecycle.md#initialization):
33[initialization](https://modelcontextprotocol.io/specification/2025-03-26/basic/lifecycle.md#initialization):
3434
3535```json theme={null}
3636{
specification/2025-03-26/server/tools Changed · +2 / -2 lines
from line 49
4949### Listing Tools
5050
5151To discover available tools, clients send a `tools/list` request. This operation supports
52[pagination](/specification/2025-03-26/server/utilities/pagination.md).
52[pagination](https://modelcontextprotocol.io/specification/2025-03-26/server/utilities/pagination.md).
5353
5454**Request:**
5555
from line 219
219219
220220#### Embedded Resources
221221
222[Resources](/specification/2025-03-26/server/resources.md) **MAY** be embedded, to provide additional context
222[Resources](https://modelcontextprotocol.io/specification/2025-03-26/server/resources.md) **MAY** be embedded, to provide additional context
223223or data, behind a URI that can be subscribed to or fetched again by the client later:
224224
225225```json theme={null}
specification/2025-06-18/architecture/index Changed · +2 / -2 lines
from line 158
158158Each capability unlocks specific protocol features for use during the session. For
159159example:
160160
161* Implemented [server features](/specification/2025-06-18/server.md) must be advertised in the
161* Implemented [server features](https://modelcontextprotocol.io/specification/2025-06-18/server.md) must be advertised in the
162162 server's capabilities
163163* Emitting resource subscription notifications requires the server to declare
164164 subscription support
165165* Tool invocation requires the server to declare tool capabilities
166* [Sampling](/specification/2025-06-18/client/sampling.md) requires the client to declare support in its
166* [Sampling](https://modelcontextprotocol.io/specification/2025-06-18/client/sampling.md) requires the client to declare support in its
167167 capabilities
168168
169169This capability negotiation ensures clients and servers have a clear understanding of
specification/2025-06-18/basic/index Changed · +1 / -1 lines
from line 90
9090
9191## Auth
9292
93MCP provides an [Authorization](/specification/2025-06-18/basic/authorization.md) framework for use with HTTP.
93MCP provides an [Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization.md) framework for use with HTTP.
9494Implementations using an HTTP-based transport **SHOULD** conform to this specification,
9595whereas implementations using STDIO transport **SHOULD NOT** follow this specification,
9696and instead retrieve credentials from the environment.
specification/2025-06-18/client/elicitation Changed · +1 / -1 lines
from line 34
3434## Capabilities
3535
3636Clients that support elicitation **MUST** declare the `elicitation` capability during
37[initialization](/specification/2025-06-18/basic/lifecycle.md#initialization):
37[initialization](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle.md#initialization):
3838
3939```json theme={null}
4040{
specification/2025-06-18/client/roots Changed · +1 / -1 lines
from line 21
2121## Capabilities
2222
2323Clients that support roots **MUST** declare the `roots` capability during
24[initialization](/specification/2025-06-18/basic/lifecycle.md#initialization):
24[initialization](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle.md#initialization):
2525
2626```json theme={null}
2727{
specification/2025-06-18/client/sampling Changed · +1 / -1 lines
from line 30
3030## Capabilities
3131
3232Clients that support sampling **MUST** declare the `sampling` capability during
33[initialization](/specification/2025-06-18/basic/lifecycle.md#initialization):
33[initialization](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle.md#initialization):
3434
3535```json theme={null}
3636{
specification/2025-11-25/architecture/index Changed · +2 / -2 lines
from line 158
158158Each capability unlocks specific protocol features for use during the session. For
159159example:
160160
161* Implemented [server features](/specification/2025-11-25/server.md) must be advertised in the
161* Implemented [server features](https://modelcontextprotocol.io/specification/2025-11-25/server.md) must be advertised in the
162162 server's capabilities
163163* Emitting resource subscription notifications requires the server to declare
164164 subscription support
165165* Tool invocation requires the server to declare tool capabilities
166* [Sampling](/specification/2025-11-25/client/sampling.md) requires the client to declare support in its
166* [Sampling](https://modelcontextprotocol.io/specification/2025-11-25/client/sampling.md) requires the client to declare support in its
167167 capabilities
168168
169169This capability negotiation ensures clients and servers have a clear understanding of
specification/2025-11-25/basic/utilities/cancellation Changed · +1 / -1 lines
from line 29
2929 * Were previously issued in the same direction
3030 * Are believed to still be in-progress
31312. The `initialize` request **MUST NOT** be cancelled by clients
323. For [task-augmented requests](/specification/2025-11-25/basic/utilities/tasks.md), the `tasks/cancel` request **MUST** be used instead of the `notifications/cancelled` notification. Tasks have their own dedicated cancellation mechanism that returns the final task state.
323. For [task-augmented requests](https://modelcontextprotocol.io/specification/2025-11-25/basic/utilities/tasks.md), the `tasks/cancel` request **MUST** be used instead of the `notifications/cancelled` notification. Tasks have their own dedicated cancellation mechanism that returns the final task state.
33334. Receivers of cancellation notifications **SHOULD**:
3434 * Stop processing the cancelled request
3535 * Free associated resources
specification/2025-11-25/basic/utilities/progress Changed · +1 / -1 lines
from line 62
6262 * Send notifications at whatever frequency they deem appropriate
6363 * Omit the total value if unknown
6464
653. For [task-augmented requests](/specification/2025-11-25/basic/utilities/tasks.md), the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
653. For [task-augmented requests](https://modelcontextprotocol.io/specification/2025-11-25/basic/utilities/tasks.md), the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
6666 * Progress notifications for tasks **MUST** use the same `progressToken` that was provided in the initial task-augmented request
6767 * Progress notifications for tasks **MUST** stop after the task reaches a terminal status (`completed`, `failed`, or `cancelled`)
6868
specification/2025-11-25/client/roots Changed · +1 / -1 lines
from line 21
2121## Capabilities
2222
2323Clients that support roots **MUST** declare the `roots` capability during
24[initialization](/specification/2025-11-25/basic/lifecycle.md#initialization):
24[initialization](https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle.md#initialization):
2525
2626```json theme={null}
2727{
specification/2025-11-25/client/sampling Changed · +1 / -1 lines
from line 36
3636## Capabilities
3737
3838Clients that support sampling **MUST** declare the `sampling` capability during
39[initialization](/specification/2025-11-25/basic/lifecycle.md#initialization):
39[initialization](https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle.md#initialization):
4040
4141**Basic sampling:**
4242
specification/2025-11-25/server/resources Changed · +2 / -2 lines
from line 81
8181### Listing Resources
8282
8383To discover available resources, clients send a `resources/list` request. This operation
84supports [pagination](/specification/2025-11-25/server/utilities/pagination.md).
84supports [pagination](https://modelcontextprotocol.io/specification/2025-11-25/server/utilities/pagination.md).
8585
8686**Request:**
8787
from line 163
163163
164164Resource templates allow servers to expose parameterized resources using
165165[URI templates](https://datatracker.ietf.org/doc/html/rfc6570). Arguments may be
166auto-completed through [the completion API](/specification/2025-11-25/server/utilities/completion.md).
166auto-completed through [the completion API](https://modelcontextprotocol.io/specification/2025-11-25/server/utilities/completion.md).
167167
168168**Request:**
169169
specification/2026-07-28/basic/authorization/authorization-server-discovery Changed · +2 / -2 lines
from line 27
2727separate registration state (client credentials, tokens) per authorization server and
2828**MUST NOT** assume that credentials valid for one authorization server will be accepted by
2929another. See
30[Authorization Server Binding](/specification/2026-07-28/basic/authorization/client-registration.md#authorization-server-binding)
30[Authorization Server Binding](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/client-registration.md#authorization-server-binding)
3131for the requirements on associating client credentials with the authorization server that issued them.
3232
3333## Protected Resource Metadata Discovery Requirements
from line 46
4646
4747Servers can also include a `scope` parameter in the `WWW-Authenticate` challenge to indicate the
4848scopes required for accessing the resource; the scope semantics and the associated client behavior
49are defined in the [Scope Selection Strategy](/specification/2026-07-28/basic/authorization.md#scope-selection-strategy) section.
49are defined in the [Scope Selection Strategy](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization.md#scope-selection-strategy) section.
5050
5151## Authorization Server Metadata Discovery
5252
specification/2026-07-28/basic/authorization/client-registration Changed · +2 / -2 lines
from line 44
4444* **SHOULD** cache metadata respecting HTTP cache headers
4545* **MUST** validate redirect URIs presented in an authorization request against those in the metadata document
4646* **MUST** validate the document structure is valid JSON and contains required fields
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](/specification/2026-07-28/basic/authorization/security-considerations.md#client-id-metadata-document-security)
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/security-considerations.md#client-id-metadata-document-security)
4848
4949### Example Metadata Document
5050
from line 181
181181credentials with the specific authorization server that issued them,
182182keyed by the authorization server's `issuer` identifier. When the
183183authorization server changes (detected via updated
184[protected resource metadata](/specification/2026-07-28/basic/authorization/authorization-server-discovery.md#authorization-server-location)),
184[protected resource metadata](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/authorization-server-discovery.md#authorization-server-location)),
185185clients **MUST NOT** reuse client credentials
186186from a different authorization server and **MUST** re-register
187187with the new authorization server.
specification/2026-07-28/basic/patterns/cancellation Changed · +2 / -2 lines
from line 54
5454per-request basis.
5555
5656Implementations **MAY** choose to reset the timeout clock when receiving a
57[progress notification](/specification/2026-07-28/basic/patterns/progress.md) corresponding to
57[progress notification](https://modelcontextprotocol.io/specification/2026-07-28/basic/patterns/progress.md) corresponding to
5858the request, as this implies that work is actually happening. However, implementations
5959**SHOULD** always enforce a maximum timeout, regardless of progress notifications, to
6060limit the impact of a misbehaving client or server.
from line 115
115115This maintains the "fire and forget" nature of notifications while allowing for race
116116conditions in asynchronous communication.
117117
118[subscriptions]: /specification/2026-07-28/basic/patterns/subscriptions.md
118[subscriptions]: https://modelcontextprotocol.io/specification/2026-07-28/basic/patterns/subscriptions.md
119119
specification/2026-07-28/basic/patterns/subscriptions Changed · +1 / -1 lines
from line 159
159159
160160See [Cancellation][cancellation] for the full rules.
161161
162[cancellation]: /specification/2026-07-28/basic/patterns/cancellation.md
162[cancellation]: https://modelcontextprotocol.io/specification/2026-07-28/basic/patterns/cancellation.md
163163
specification/2026-07-28/server/utilities/completion Changed · +1 / -1 lines
from line 12
1212> `io.modelcontextprotocol/clientInfo`, and
1313> `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include
1414> the required `_meta` fields; see
15> [`_meta`](/specification/2026-07-28/basic/index#meta).
15> [`_meta`](https://modelcontextprotocol.io/specification/2026-07-28/basic/index#meta).
1616
1717## User Interaction Model
1818
specification/2026-07-28/server/utilities/pagination Changed · +1 / -1 lines
from line 15
1515> `io.modelcontextprotocol/clientInfo`, and
1616> `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include
1717> the required `_meta` fields; see
18> [`_meta`](/specification/2026-07-28/basic/index#meta).
18> [`_meta`](https://modelcontextprotocol.io/specification/2026-07-28/basic/index#meta).
1919
2020## Pagination Model
2121
specification/draft/basic/authorization/authorization-server-discovery Changed · +2 / -2 lines
from line 27
2727separate registration state (client credentials, tokens) per authorization server and
2828**MUST NOT** assume that credentials valid for one authorization server will be accepted by
2929another. See
30[Authorization Server Binding](/specification/draft/basic/authorization/client-registration.md#authorization-server-binding)
30[Authorization Server Binding](https://modelcontextprotocol.io/specification/draft/basic/authorization/client-registration.md#authorization-server-binding)
3131for the requirements on associating client credentials with the authorization server that issued them.
3232
3333## Protected Resource Metadata Discovery Requirements
from line 46
4646
4747Servers can also include a `scope` parameter in the `WWW-Authenticate` challenge to indicate the
4848scopes required for accessing the resource; the scope semantics and the associated client behavior
49are defined in the [Scope Selection Strategy](/specification/draft/basic/authorization.md#scope-selection-strategy) section.
49are defined in the [Scope Selection Strategy](https://modelcontextprotocol.io/specification/draft/basic/authorization.md#scope-selection-strategy) section.
5050
5151## Authorization Server Metadata Discovery
5252
specification/draft/basic/authorization/client-registration Changed · +2 / -2 lines
from line 44
4444* **SHOULD** cache metadata respecting HTTP cache headers
4545* **MUST** validate redirect URIs presented in an authorization request against those in the metadata document
4646* **MUST** validate the document structure is valid JSON and contains required fields
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](/specification/draft/basic/authorization/security-considerations.md#client-id-metadata-document-security)
47* **SHOULD** follow the security considerations in [Section 6 of Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-00.html#section-6) and in [Client ID Metadata Document Security](https://modelcontextprotocol.io/specification/draft/basic/authorization/security-considerations.md#client-id-metadata-document-security)
4848
4949### Example Metadata Document
5050
from line 181
181181credentials with the specific authorization server that issued them,
182182keyed by the authorization server's `issuer` identifier. When the
183183authorization server changes (detected via updated
184[protected resource metadata](/specification/draft/basic/authorization/authorization-server-discovery.md#authorization-server-location)),
184[protected resource metadata](https://modelcontextprotocol.io/specification/draft/basic/authorization/authorization-server-discovery.md#authorization-server-location)),
185185clients **MUST NOT** reuse client credentials
186186from a different authorization server and **MUST** re-register
187187with the new authorization server.
specification/draft/basic/patterns/cancellation Changed · +2 / -2 lines
from line 54
5454per-request basis.
5555
5656Implementations **MAY** choose to reset the timeout clock when receiving a
57[progress notification](/specification/draft/basic/patterns/progress.md) corresponding to
57[progress notification](https://modelcontextprotocol.io/specification/draft/basic/patterns/progress.md) corresponding to
5858the request, as this implies that work is actually happening. However, implementations
5959**SHOULD** always enforce a maximum timeout, regardless of progress notifications, to
6060limit the impact of a misbehaving client or server.
from line 115
115115This maintains the "fire and forget" nature of notifications while allowing for race
116116conditions in asynchronous communication.
117117
118[subscriptions]: /specification/draft/basic/patterns/subscriptions.md
118[subscriptions]: https://modelcontextprotocol.io/specification/draft/basic/patterns/subscriptions.md
119119