370 pages for prefix.

Versioning Published MCP Servers Model Context Protocol · in the page registry/versioning …ion!⚠️)** | | `2025-06-18` | non-semantic date | Allowed | | `v1.0` | prefixed version | Allowed | | `^1.2.3` | version range | Prohibited | | `~1.2.3` | version range | Prohibited | | `>=1.2.3` | ver… SEP-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …ent for others, unlikely to get approval. * “Whole prompt” / prompt-prefix cache w/ an explicit key [as in the OpenAI API](https://platform.openai.com/docs/api-reference/responses/create#responses-c… 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 …dentSchemas` + `dependentRequired`) * Positional array validation (→ `prefixItems`) **Migration strategy:** Add explicit `$schema: "http://json-schema.org/draft-07/schema#"` during transition, then u… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …ified using a unique *extension identifier* with the format: `{vendor-prefix}/{extension-name}`, e.g. `io.modelcontextprotocol/oauth-client-credentials` or `com.example/websocket-transport`. The names… SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …eme={null} Mcp-Param-{Name}: =?base64?{Base64EncodedValue}?= ``` The prefix `=?base64?` and suffix `?=` indicate that the value is Base64-encoded. These markers are case-sensitive and MUST appear exa… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …ield). Preceding segments, if any, are a server-chosen organizational prefix. Servers MAY organize skills hierarchically by domain, team, version, or any other axis. In `skill://acme/billing/refunds/S… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …*MUST** contain that result. ### Reservations * The `tasks/` method prefix and `notifications/tasks/` notification prefix are reserved for this extension. * The result-discriminator value `"task"` f… SEP-414: Document OpenTelemetry Trace Context Propagation Conventions Model Context Protocol · in the page seps/414-request-meta …mplementations. This specification documents an exception to the DNS prefixing convention for keys in `_meta`. This enables interoperability across existing and new implementations and serves as a fo… Overview Model Context Protocol · in the page specification/2025-06-18/basic/index …me format:** valid `_meta` key names have two segments: an optional **prefix**, and a **name**. **Prefix:** * If specified, MUST be a series of labels separated by dots (`.`), followed by a slash (`… Overview Model Context Protocol · in the page specification/2025-11-25/basic/index …me format:** valid `_meta` key names have two segments: an optional **prefix**, and a **name**. **Prefix:** * If specified, MUST be a series of labels separated by dots (`.`), followed by a slash (`… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …me format:** valid `_meta` key names have two segments: an optional **prefix**, and a **name**. **Prefix:** * If specified, MUST be a series of labels separated by dots (`.`), followed by a slash (`… Streamable HTTP Model Context Protocol · in the page specification/2026-07-28/basic/transports/streamable-http …`text theme={null} Mcp-Name: =?base64?{Base64EncodedValue}?= ``` The prefix `=?base64?` and suffix `?=` indicate that the value is Base64-encoded. These markers are case-sensitive and **MUST** appear… Versioning and Compatibility Model Context Protocol · in the page specification/2026-07-28/basic/versioning …rules](/specification/2026-07-28/basic/index#meta), with a mandatory prefix. The following is an example of a client that advertises the [MCP Apps extension](/extensions/apps/overview.md) identified… Schema Reference Model Context Protocol · in the page specification/2026-07-28/schema …hose definitions.</p> <p>Valid keys have two segments:</p> <p><strong>Prefix:</strong></p> <ul> <li>Optional — if specified, MUST be a series of <em>labels</em> separated by dots (<code>.</code>), fol… Tools Model Context Protocol · in the page specification/2026-07-28/server/tools …h` tool) and **SHOULD** implement a > disambiguation strategy such as prefixing tool names with a server identifier. > > The server `name` (from `serverInfo`) is not guaranteed to be unique across > s… Overview Model Context Protocol · in the page specification/draft/basic/index …me format:** valid `_meta` key names have two segments: an optional **prefix**, and a **name**. **Prefix:** * If specified, MUST be a series of labels separated by dots (`.`), followed by a slash (`… Streamable HTTP Model Context Protocol · in the page specification/draft/basic/transports/streamable-http …`text theme={null} Mcp-Name: =?base64?{Base64EncodedValue}?= ``` The prefix `=?base64?` and suffix `?=` indicate that the value is Base64-encoded. These markers are case-sensitive and **MUST** appear… Versioning and Compatibility Model Context Protocol · in the page specification/draft/basic/versioning …aming rules](/specification/draft/basic/index#meta), with a mandatory prefix. The following is an example of a client that advertises the [MCP Apps extension](/extensions/apps/overview.md) identified… Schema Reference Model Context Protocol · in the page specification/draft/schema …hose definitions.</p> <p>Valid keys have two segments:</p> <p><strong>Prefix:</strong></p> <ul> <li>Optional — if specified, MUST be a series of <em>labels</em> separated by dots (<code>.</code>), fol… Tools Model Context Protocol · in the page specification/draft/server/tools …h` tool) and **SHOULD** implement a > disambiguation strategy such as prefixing tool names with a server identifier. > > The server `name` (from `serverInfo`) is not guaranteed to be unique across > s…