Add some missing protocol revision banners

Author: jspahrsummers

docs/specification/basic/_index.md

@@ -5,6 +5,10 @@ cascade:
 weight: 2
 ---
 
+{{< callout type="info" >}}
+**Protocol Revision**: {{< param protocolRevision >}}
+{{< /callout >}}
+
 All messages between MCP clients and servers **MUST** follow the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines three fundamental types of messages:
 
 | Type           | Description                            | Requirements                           |

docs/specification/basic/utilities/_index.md

@@ -2,6 +2,10 @@
 title: Utilities
 ---
 
+{{< callout type="info" >}}
+**Protocol Revision**: {{< param protocolRevision >}}
+{{< /callout >}}
+
 The Model Context Protocol includes several optional features that enhance the base protocol functionality. These features can be used independently to add capabilities like request cancellation, paginated results, and progress tracking.
 
 {{< cards >}}

docs/specification/client/_index.md

@@ -4,3 +4,7 @@ cascade:
   type: docs
 weight: 4
 ---
+
+{{< callout type="info" >}}
+**Protocol Revision**: {{< param protocolRevision >}}
+{{< /callout >}}

docs/specification/server/_index.md

@@ -4,6 +4,11 @@ cascade:
   type: docs
 weight: 3
 ---
+
+{{< callout type="info" >}}
+**Protocol Revision**: {{< param protocolRevision >}}
+{{< /callout >}}
+
 Context primitives are the fundamental building blocks for providing context to language models via MCP. These primitives enable rich interactions between clients, servers, and language models. The key primitives are:
 
 - **Prompts**: Pre-defined templates or instructions that guide language model interactions

docs/specification/server/utilities/_index.md

@@ -1,3 +1,7 @@
 ---
 title: Utilities
 ---
+
+{{< callout type="info" >}}
+**Protocol Revision**: {{< param protocolRevision >}}
+{{< /callout >}}