MCP Protocol News - November 6, 2026

Week of: November 6, 2026

Overview

The Model Context Protocol repository merged a schema fix closing a oneOf validation bypass and rendering SEP-2106 tool examples, while also updating client and Rust server tutorials. The MCP Servers project published v2.3.0 with refreshed npm and PyPI packages, and the spec repository continued tightening its PR and release workflow conventions.

Stories

1. MCP schema fix closes oneOf validation bypass and renders SEP-2106 tool examples

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

The MCP specification repository merged a schema fix for a oneOf type-check bypass in the composition inputSchema example. The find_resource example used branch-local properties, allowing a wrongly typed value in an inactive branch to pass validation and bypass the intended mutual exclusivity. The change also renders SEP-2106 tool examples.

Schema examples are used by implementers as validation patterns, so a composition example that accepts malformed input can propagate into tool definitions. Correct oneOf behavior matters for tool input validation and for keeping SEP-aligned examples consistent.

Impact Analysis: Implementers should review any copied oneOf input-schema examples and prefer the corrected validation pattern.

2. MCP Servers v2.3.0 publishes updated npm and PyPI packages

Source: MCP Servers Link: https://github.com/modelcontextprotocol/servers/releases/tag/v2.3.0

MCP Servers released v2.3.0, publishing updated packages including @modelcontextprotocol/server-everything 2.2.1, server-filesystem 2.2.0, server-memory 2.1.0, and server-sequential-thinking 2.1.1 on npm. The release also lists mcp-server-fetch, mcp-server-git, and mcp-server-time at 2026.11.4 on PyPI, and references a test(everything) change checking that registered tools carry annotation hints.

These reference servers are common starting points for MCP integrations, so package updates can affect builders who depend on them directly or use them as implementation examples. The annotation-related test change also points to continued attention on tool metadata consistency.

Impact Analysis: Teams using MCP reference servers should check the release ledger and update pinned package versions where appropriate.

3. Client tutorial updated to run a full tool loop

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

The specification repository merged PR #3482, updating the client tutorial to run a full tool loop. The change is a documentation update focused on showing the complete client-side tool invocation flow rather than only setup or connection steps.

For builders, a full tool-loop tutorial is a practical reference for wiring model requests to MCP tool calls and handling results. Keeping the client tutorial aligned with real usage helps reduce integration friction for new MCP clients.

Impact Analysis: Client implementers should use the updated tutorial as the current reference for end-to-end tool invocation.

4. Rust server tutorial updated to rmcp 3

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

The specification repository merged PR #3479, updating the Rust server tutorial to rmcp 3. The change is part of the documentation updates merged in the same window.

Rust is one of the supported implementation paths for MCP servers, and tutorial freshness matters when SDK major versions change. Builders following the Rust guide should use the updated rmcp 3 version rather than older tutorial code.

Impact Analysis: Rust server developers should verify their tutorial and dependency versions against the updated rmcp 3 guidance.

5. MCP spec repository adds conventional PR title checks

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

The specification repository merged PR #3507, adding a CI check for conventional PR titles. The same period includes related release-workflow commits around conventional release PR titles, release metadata, authentication, and publishing when release PRs merge.

Standardized PR titles support automated release notes and release tooling, which matters as the MCP specification and related repositories mature. For contributors and maintainers, the change signals stricter enforcement of contribution conventions.

Impact Analysis: Contributors to the MCP specification repository should use conventional PR titles to pass CI and support release automation.

Source Links

• MCP Specification - MCP schema fix closes oneOf validation bypass and renders SEP-2106 tool examples
• MCP Servers - MCP Servers v2.3.0 publishes updated npm and PyPI packages
• MCP Specification - Client tutorial updated to run a full tool loop
• MCP Specification - Rust server tutorial updated to rmcp 3
• MCP Specification - MCP spec repository adds conventional PR title checks