docs: Remove '(Final)' from protocol revision references

dsp-ant · claude · dsp-ant · commit fb41a1dea6bf · 2024-11-21T18:57:14.000Z
Only keep '(Final)' in the original revision document where its status is now explicitly noted.

🤖 Generated with Claude CLI.

Co-Authored-By: Claude &lt;noreply@anthropic.com&gt;
diff --git a/docs/specification/_index.md b/docs/specification/_index.md
@@ -6,7 +6,7 @@ weight: 10
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need. This specification defines the authoritative protocol requirements based on the TypeScript schema in [schema.ts](https://github.com/modelcontextprotocol/specification/blob/main/schema/schema.ts). For implementation guides and examples, visit [modelcontextprotocol.io](https://modelcontextprotocol.io).
diff --git a/docs/specification/basic/lifecycle.md b/docs/specification/basic/lifecycle.md
@@ -5,7 +5,7 @@ weight: 30
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server connections that ensures proper capability negotiation and state management. This lifecycle consists of four distinct phases:
diff --git a/docs/specification/basic/messages.md b/docs/specification/basic/messages.md
@@ -4,7 +4,7 @@ type: docs
 weight: 20
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 All messages in MCP **MUST** follow the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines three types of messages:
diff --git a/docs/specification/basic/transports.md b/docs/specification/basic/transports.md
@@ -4,7 +4,7 @@ type: docs
 weight: 40
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 MCP supports multiple transport mechanisms for client-server communication. The two standard transport mechanisms are STDIO and HTTP with Server-Sent Events (SSE).  We recommend clients to support at least STDIO.
diff --git a/docs/specification/basic/utilities/cancellation.md b/docs/specification/basic/utilities/cancellation.md
@@ -4,7 +4,7 @@ weight: 10
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports optional cancellation of in-progress requests through notification messages. Either side can send a cancellation notification to indicate that a previously-issued request should be terminated.
diff --git a/docs/specification/basic/utilities/pagination.md b/docs/specification/basic/utilities/pagination.md
@@ -3,7 +3,7 @@ title: Pagination
 weight: 20
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports pagination for list operations that may return large result sets. Pagination allows clients to retrieve results in smaller chunks rather than all at once.
diff --git a/docs/specification/basic/utilities/ping.md b/docs/specification/basic/utilities/ping.md
@@ -4,7 +4,7 @@ weight: 5
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol includes an optional ping mechanism that allows either party to verify that their counterpart is still responsive and the connection is alive.
diff --git a/docs/specification/basic/utilities/progress.md b/docs/specification/basic/utilities/progress.md
@@ -3,7 +3,7 @@ title: Progress
 weight: 30
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) supports optional progress tracking for long-running operations through notification messages. Either side can send progress notifications to provide updates about operation status.
diff --git a/docs/specification/basic/versioning.md b/docs/specification/basic/versioning.md
@@ -4,7 +4,7 @@ type: docs
 weight: 80
 ---
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol uses string-based version identifiers following the format `YYYY-MM-DD` to indicate the last date significant changes were made. The current protocol version is `2024-11-05`.
diff --git a/docs/specification/client/roots.md b/docs/specification/client/roots.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for clients to expose filesystem roots to servers. Roots define the boundaries of where servers can operate within the filesystem, allowing them to understand which directories and files they have access to. Servers can request the list of roots from supporting clients and receive notifications when that list changes.
diff --git a/docs/specification/client/sampling.md b/docs/specification/client/sampling.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to request generations from language models via clients. This unique reverse flow allows clients to maintain control over model access, selection, and permissions while enabling servers to leverage AI capabilities. Servers can request text or image-based interactions and optionally include context from MCP servers in their prompts.
diff --git a/docs/specification/revisions/2024-11-05.md b/docs/specification/revisions/2024-11-05.md
@@ -2,4 +2,4 @@
 title: 2024-11-05 (Final)
 weight: 1
 ---
-This is the initial version of the specification
+This is the initial version of the specification. This revision has been finalized.
diff --git a/docs/specification/server/prompts.md b/docs/specification/server/prompts.md
@@ -4,7 +4,7 @@ weight: 10
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt templates to clients. Prompts allow servers to provide structured messages and instructions for interacting with language models. Clients can discover available prompts, retrieve their contents, and provide arguments to customize them.
diff --git a/docs/specification/server/resources.md b/docs/specification/server/resources.md
@@ -5,7 +5,7 @@ weight: 20
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to expose resources to clients. Resources allow servers to share data that provides context to language models, such as files, database schemas, or application-specific information. Each resource is uniquely identified by a [URI](https://datatracker.ietf.org/doc/html/rfc3986).
diff --git a/docs/specification/server/tools.md b/docs/specification/server/tools.md
@@ -5,7 +5,7 @@ weight: 40
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) allows servers to expose tools that can be invoked by language models through clients. Tools enable models to perform actions or retrieve information beyond their training data, such as querying databases, calling external APIs, or executing commands. Each tool is uniquely identified by a name and includes metadata describing its capabilities and requirements.
diff --git a/docs/specification/server/utilities/completion.md b/docs/specification/server/utilities/completion.md
@@ -3,7 +3,7 @@ title: Completion
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to provide argument completion suggestions for prompts and resource URIs. This enables rich, IDE-like experiences where users receive contextual suggestions while entering argument values.
diff --git a/docs/specification/server/utilities/logging.md b/docs/specification/server/utilities/logging.md
@@ -3,7 +3,7 @@ title: Logging
 ---
 
 {{< callout type="info" >}}
-**Protocol Revision**: 2024-11-05 (Final)
+**Protocol Revision**: 2024-11-05
 {{< /callout >}}
 
 The Model Context Protocol (MCP) provides a standardized way for servers to send structured log messages to clients. Clients can control logging verbosity by setting minimum log levels, with servers sending notifications containing severity levels, optional logger names, and arbitrary JSON-serializable data.
