MCP Protocol News - October 9, 2026

Week of: October 9, 2026

Overview

The Model Context Protocol spec repo merged SEP-2127, "MCP Server Cards - HTTP Server Discovery," the most consequential protocol-level change in this window, while also landing a local server security guide and a broad Inspector documentation refresh covering a new security page and the mcpdo client. On the implementation side, the GitHub MCP Server shipped 2.0.0 with structured outputs and output schemas gated on MCP 2026-07-28 spec support, followed by two quick patch releases, and the TypeScript SDK cut 2.3.1 with audience-bound bearer auth in the legacy server package.

Stories

1. SEP-2127 "MCP Server Cards - HTTP Server Discovery" merged into the MCP spec repo

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/0a11bf68c7ec4473526ec15589f592afcd12d1e8

The specification repository merged pull request #2127 from the sep/mcp-server-cards branch, carrying SEP-2127, titled "MCP Server Cards - HTTP Server Discovery." The commit is a merge of that proposal branch into the spec repository's mainline.

HTTP server discovery is the kind of change that shifts how clients find and connect to remote MCP servers, so it is worth tracking for anyone building client-side routing, registries, or server deployment tooling. The snippet provided does not detail the card format or required fields — see source for the full SEP text.

Impact Analysis: Treat SEP-2127 as a spec-level shift in how HTTP MCP servers are advertised and discovered, and review the merged SEP before finalizing client or registry designs.

2. GitHub MCP Server 2.0.0 adds structured outputs and output schemas

Source: GitHub MCP Server Link: https://github.com/github/github-mcp-server/releases/tag/v2.0.0

GitHub MCP Server 2.0.0 was released with support for structured outputs and output schemas, motivated by the release notes' observation that more agents are supporting Code Mode or Programmatic Tool Calling. The schemas are only advertised to clients that advertise MCP 2026-07-28 spec support (or later), and the release notes state that compound tools needed updates to allowed output schemas, so those schemas are not returned to older clients.

This is a concrete example of server behavior being version-gated on the client's advertised spec support — a pattern MCP implementers will need to handle as the ecosystem fragments across spec eras. The release also includes caching of encoded tools/list schemas, pinning GitHub Actions to commit SHAs, and a typed MCP tool inventory feature.

Impact Analysis: If you consume GitHub's MCP server with a Code Mode or programmatic-tool-calling agent, verify your client advertises MCP 2026-07-28 or later to receive the new output schemas.

3. MCP Inspector documentation overhauled: new security page, mcpdo client, and page-by-page audit

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/c518f7a927cff918bce35d3522fcdb046d264d7c

A merge of pull request #3418 brought in inspector documentation work described as "security page, mcpdo client, and bring every Inspector page up to date." Related commits in the window document modelcontextprotocol/inspector changes shipping in v2.10.0 (tracked in inspector#2450) across both the draft and 2026-07-28 doc versions, including a new Security page covering the Inspector's threat model — the web backend's API token and DANGEROUSLY_OMIT_AUTH, Docker port publishing and the data volume, secret storage and its plaintext fallback, stdio servers running as the user, and the mcpdo connection daemon — plus a new mcpdo page.

A separate audit commit notes that all ten Inspector pages were reviewed against the Inspector's current v2/main and the mcpdo PR, with drifted claims fixed in both doc versions covering configuration flags, server seeds, --protocol-era, skill-catalog budget flags, loopback callback hosts, and MCP_DEBUG behavior.

Impact Analysis: Update any Inspector-based internal documentation to the refreshed v2.10.0 pages, particularly around auth omission and secret storage, before debugging server behavior against stale guidance.

4. Local server security guide merged into the MCP spec repo

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/8e12bf3c8f01f374146acfa19b8ece0018bfc86c

Pull request #3072, "docs: add local server security guide," was merged into the spec repository. A review-feedback commit in the same window describes the guide's content: a step-zero section asking whether a server needs to run locally at all, preferring the remote Streamable HTTP version when nothing local is needed and treating an unnecessary stdio-only distribution as a signal; a "Know what the pin covers" section noting that launcher pins fix only the top-level package while an image digest freezes the whole dependency tree; a link to the MCP Inspector as a way to read a server's tool definitions; and seccomp profiles and Linux security modules as container hardening levers.

Local stdio servers run with the privileges of the user invoking them, so this is directly relevant to anyone shipping or deploying MCP servers on developer machines or CI runners.

Impact Analysis: Check whether your MCP server genuinely needs local execution before shipping a stdio-only distribution, and treat remote Streamable HTTP as the default where it suffices.

5. MCP TypeScript SDK 2.3.1 adds audience-bound bearer auth to server-legacy

Source: MCP TypeScript SDK Link: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/v2.3.1

Version 2.3.1 of the MCP TypeScript SDK was published, bumping @modelcontextprotocol/client, server, core, server-legacy, and codemod to 2.3.1, with node, express, hono, and fastify unchanged. The main behavioral change is that requireBearerAuth in @modelcontextprotocol/server-legacy now takes the optional expectedResource that @modelcontextprotocol/server 2.3.0 added, accepting only tokens issued for that server (the token's audience); it is off unless you set it. The release also notes that the npm pages of @modelcontextprotocol/server and @modelcontextprotocol/client now open with updated content.

The companion server-legacy@2.3.1 release notes state that when expectedResource is set, a token is accepted only if the verifier reports that value in AuthInfo.resource, compared as strings while ignoring a fragment and one trailing slash, and a mismatch is answered with 401 invalid_token and the usual WWW-Authenticate challenge.

Impact Analysis: Set expectedResource on legacy TypeScript servers that sit behind multiple audiences, since audience checking is opt-in and otherwise absent.

6. GitHub MCP Server ships 2.0.1 and 2.0.2 patch releases

Source: GitHub MCP Server Link: https://github.com/github/github-mcp-server/releases/tag/v2.0.2

GitHub MCP Server 2.0.1 was published as a bugfix that publishes the proper module path for Go library users, with the change described as using the v2 module path for Go consumers (#3445). Version 2.0.2 followed a day later as a bugfix release restoring typed tool HTTP header validation (#3454).

The rapid patch cadence after the 2.0.0 feature release is a reminder that major-version bumps in MCP servers can carry consumer-facing build and validation regressions. Go consumers in particular should ensure their import paths point at the v2 module.

Impact Analysis: Upgrade to 2.0.2 if you depend on the Go module or on typed tool HTTP header validation, rather than pinning to 2.0.0.

7. Inspector docs show MRTR conversations grouped in the monitoring sidebar

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/cabe6861d4c3cdfd1ef7efc7ad94957c70239617

A docs commit in the spec repository updates the Inspector documentation to show an MRTR conversation grouped in the monitoring sidebar. The commit is a documentation change; the snippet does not expand on the underlying Inspector feature — see source.

For builders debugging multi-step tool exchanges, documenting how conversations are grouped in the monitoring sidebar makes it easier to inspect a single session as a unit rather than as scattered events.

Impact Analysis: Use the updated Inspector monitoring docs as the reference when interpreting grouped conversation traces during MCP debugging.

Source Links

• MCP Specification - Merge pull request #2127 from modelcontextprotocol/sep/mcp-server-cards
• GitHub MCP Server - GitHub MCP Server 2.0.0
• MCP Specification - Merge pull request #3418 from modelcontextprotocol/docs/inspector-2450-security-mcpdo
• MCP Specification - Merge pull request #3072 from rdimitrov/rdimitrov/local-mcp-security-docs
• MCP TypeScript SDK - 2.3.1
• GitHub MCP Server - GitHub MCP Server 2.0.2
• MCP Specification - docs(inspector): show an MRTR conversation grouped in the monitoring sidebar