Merge pull request #4799 from OpenLiberty/26.0.0.5-beta-post

Update 26.0.0.5-beta blog

Author: navaneethsnair1

posts/2026-05-05-26.0.0.5-beta.adoc

@@ -6,8 +6,8 @@ categories: blog
 author_picture: https://avatars3.githubusercontent.com/navaneethsnair1
 author_github: https://github.com/navaneethsnair1
 seo-title: "MCP server updates and Transport Security in 26.0.0.5-beta- OpenLiberty.io"
-seo-description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration using JDK defaults and flexible `enabledCiphers` syntax.
-blog_description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration using JDK defaults and flexible `enabledCiphers` syntax.
+seo-description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using JDK defaults and flexible `enabledCiphers` syntax.
+blog_description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using JDK defaults and flexible `enabledCiphers` syntax.
 open-graph-image: https://openliberty.io/img/twitter_card.jpg
 open-graph-image-alt: Open Liberty Logo
 ---
@@ -18,7 +18,7 @@ Navaneeth S Nair <https://github.com/navaneethsnair1>
 :url-about: /
 //Blank line here is necessary before starting the body of the post.
 
-This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration using JDK defaults and flexible `enabledCiphers` syntax.
+This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using JDK defaults and flexible `enabledCiphers` syntax.
 
 // // // // // // // //
 // Change the RELEASE_SUMMARY to an introductory paragraph. This sentence is really
@@ -52,12 +52,12 @@ See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta
 
 The link:https://modelcontextprotocol.io/docs/getting-started/intro[Model Context Protocol (MCP)] is an open standard that enables AI applications to access real-time information from external sources. The Liberty MCP Server feature `mcpServer-1.0` allows developers to expose the business logic of their applications, allowing it to be integrated into agentic AI workflows.
 
-This beta release of Liberty includes important updates to the `mcpServer-1.0` feature including configurable endpoint paths and notable bug fixes.
+This beta release of Liberty includes important updates to the `mcpServer-1.0` feature, including configurable endpoint paths and notable bug fixes.
 
 === Prerequisites
-To use the `mcpServer-1.0` feature, it is required to have `Java 17`` or later installed on your system.
+To use the `mcpServer-1.0` feature, it is required to have `Java 17` or later installed on your system.
 
-=== Configure custom MCP endpoint paths (Currently under review as this is not working as intended after testing with multiple modules)
+=== Configure custom MCP endpoint paths (Currently disabled pending review - testing revealed inconsistent behavior across multiple modules)
 
 Previously, the MCP endpoint was hard-coded to `/mcp` under the web application context root. You can now configure custom endpoint paths to better suit your application architecture and naming conventions.
 
@@ -177,7 +177,7 @@ The MCP specification requires that structured content output schemas must have
 }
 ----
 
-This ensures all structured content responses comply with the link:https://modelcontextprotocol.io/specification/2025-11-25/server/tools#structured-content[MCP structured content specification] and improves compatibility with MCP clients and conformance tests.
+This helps ensure that all structured content responses comply with the link:https://modelcontextprotocol.io/specification/2025-11-25/server/tools#structured-content[MCP structured content specification] and improves compatibility with MCP clients and conformance tests.
 
 ==== 2) Authentication failures now return correct HTTP status code
 
@@ -187,9 +187,9 @@ Now, failed authentication attempts correctly return a `401 Unauthorized` respon
 
 ==== 3) Fixed encoder bean isolation in multi-application deployments
 
-Previously, encoder beans from multiple applications were stored in a static list within `McpCdiExtension`, causing beans from different applications to interfere with each other. This behaviour could result in encoder beans from one application being incorrectly called in another application, unpredictable behavior in multi-application deployments, and potential security issues with cross-application bean access.
+Previously, encoder beans from multiple applications were stored in a static list within `McpCdiExtension`, causing beans from different applications to interfere with each other. This behavior could result in encoder beans from one application being incorrectly called in another application, unpredictable behavior in multi-application deployments, and potential security issues with cross-application bean access.
 
-This has been fixed to ensure proper isolation of encoder beans per application, preventing cross-application interference and ensuring each application uses only its own encoder beans.
+This has been fixed to ensure proper isolation of encoder beans per application, preventing cross-application interference and helping ensure that each application uses only its own encoder beans.
 
 // DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>