Address feedback

🏠 Remote-Dev: homespace

Author: localden

blog/content/posts/2026-01-22-core-maintainer-update.md

@@ -1,6 +1,6 @@
 ---
-date: "2026-01-22T00:00:00+00:00"
-publishDate: "2026-01-22T00:00:00+00:00"
+date: "2026-01-23T00:00:00+00:00"
+publishDate: "2026-01-23T00:00:00+00:00"
 title: "January MCP Core Maintainer Update"
 author: "David Soria Parra (Lead Maintainer)"
 tags: ["mcp", "update", "maintainers"]
@@ -57,6 +57,6 @@ Welcome to the team, Peter, Caitie, and Kurtis.
 
 If there is one thing I can guarantee it's that 2026 will be a busy year for MCP. There are multiple active SEPs working through the process right now, including ones like the [DPoP extension](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1932) for authentication, [multi-turn SSE](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1858) for transport, and [Server Cards](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127) for discovery. This is just a sneak peek of the _many_ improvements we're currently iterating on. The ecosystem keeps expanding, with more clients, servers, and SDK releases shipping every week.
 
-MCP as a protocol has also matured. What started as an open-source experiment is now running in production at companies of all sizes. That changes what we need to focus on. With this team in place, we're working on the pieces of the puzzle that matter for the next phase of MCP growth: hardening the spec for enterprise scenarios, improving security and authentication patterns, and making sure MCP can scale to meet the demands of organizations deploying it in critical systems. At the same time, we're keeping the contributor experience welcoming and the protocol responsive to what developers actually need.
+MCP as a protocol has also matured. What started as an open-source experiment is now running in production at companies of all sizes. That changes what we need to focus on. With this team in place, we're working on the pieces of the puzzle that matter for the next phase of MCP growth: hardening the spec for enterprise scenarios, improving security and authentication patterns, providing better SDK implementation guidance, and making sure MCP can scale to meet the demands of organizations deploying it in critical systems. At the same time, we're keeping the contributor experience welcoming and the protocol responsive to what developers actually need.
 
 If you want to be part of it, check out our [governance docs](https://modelcontextprotocol.io/community/governance) or see how to [get started with MCP contributions](https://modelcontextprotocol.io/community/communication). Come build with us.