Hyperlint Automation Fix

Author: hyperlint-ai[bot]

src/content/docs/agents/model-context-protocol/transport.mdx

@@ -12,7 +12,7 @@ The Model Context Protocol (MCP) specification defines three standard [transport
 
 1. **stdio, communication over standard in and standard out** — designed for local MCP connections.
 2. **Server-Sent Events (SSE)** — Currently supported by most remote MCP clients, but is expected to be replaced by Streamable HTTP over time. It requires two endpoints: one for sending requests, another for receiving streamed responses.
-3. **Streamable HTTP** — New transport method [introduced](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http) in March 2025. It simplifies the communication by using a single HTTP endpoint for bidirectional messaging. It is currently gaining adoption among remote MCP clients, but is expected to become the standard transport in the future.
+3. **Streamable HTTP** — New transport method [introduced](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http) in March 2025. It simplifies the communication by using a single HTTP endpoint for bidirectional messaging. It is currently gaining adoption among remote MCP clients, but it is expected to become the standard transport in the future.
 
 MCP servers built with the [Agents SDK](/agents) can support both remote transport methods (SSE and Streamable HTTP), with the [`McpAgent` class](https://github.com/cloudflare/agents/blob/2f82f51784f4e27292249747b5fbeeef94305552/packages/agents/src/mcp.ts) automatically handling the transport configuration. 
 
@@ -89,7 +89,7 @@ export default new OAuthProvider({
   },
   // ... other OAuth configuration
 })
-```
+}
 
 ### Upgrading an Existing Remote MCP Server
 If you've already built a remote MCP server using the Cloudflare Agents SDK, make the following changes to support the new Streamable HTTP transport while maintaining compatibility with remote MCP clients using SSE: