MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

The MCP ecosystem, verified

MCP News catalogs 3 MCP entities (2 servers, 1 clients) with verified facts: 2 verified on the current spec revision (2026-07-28), 2 verified first-party servers.

2 Verified on 2026-07-28 1 Awaiting verification 2 First-party servers 5 Spec revisions tracked 3 Entities cataloged

More news

server release

Vercel's mcp-handler 2.0.0 adopts 2026-07-28, answers /sse with 410 Gone, and drops its Redis dependency

Vercel published mcp-handler 2.0.0, serving the stateless 2026-07-28 protocol natively while keeping a compatibility layer for 2025-era Streamable HTTP clients. The release removes the legacy HTTP+SSE transport outright and turns the Redis dependency and session options into deprecated no-ops. It is a different artifact from the Vercel MCP server.

adoption

MCP server connections for GitHub Copilot code review reach general availability, limited to read-only

GitHub moved MCP server connections and agent skills for Copilot code review from public preview to general availability across its paid Copilot tiers. Tool calls made during a review are constrained to read-only, and the GitHub and Playwright MCP servers are enabled by default.

security

HashiCorp discloses five vulnerabilities across its Terraform and Consul MCP servers, two rated CVSS 10.0 in advisory records

HashiCorp published two security bulletins one day apart covering its Terraform MCP Server and Consul MCP Server. In both products the stateless-mode issue is a cross-tenant credential reuse flaw that the GitHub advisory records score CVSS 10.0. HashiCorp's own bulletins state no CVSS scores or severity labels.

adoption

Amazon Bedrock AgentCore Gateway adds opt-in support for MCP 2026-07-28

AWS shipped same-day support for the stateless MCP revision in AgentCore Gateway: gateways advertise the protocol versions they speak, clients select a version per request, and existing 2025-era clients keep working unchanged.

spec release

MCP goes stateless: the 2026-07-28 specification is released

The Model Context Protocol's 2026-07-28 revision is stable: the protocol core becomes stateless, retiring the initialize handshake and protocol-level sessions, with Multi Round-Trip Requests replacing server-initiated requests and a formal twelve-month deprecation policy. All four Tier 1 SDKs shipped support on release day.

client release

Anthropic says 2026-07-28 support is rolling out across Claude products, without per-product dates

Anthropic published a post on the day of the revision describing the Claude-side capabilities tied to it and stating that support is being rolled out across Claude products. The post names four capabilities and puts the connectors directory above 950 servers, but gives no per-surface availability or completion date.

The MCP 500 Full list →

# Server Index Downloads/wk Stars
1 io.github.microsoft/playwright-mcp 85.84 6.2M 36k
2 Chrome DevTools MCP 82.61 1.5M 49k
3 io.github.firebase/firebase-mcp 80.80 2.6M 4.5k
4 Context7 80.53 656k 60k
5 GitHub MCP Server 77.08 - 32k

Start here

Verified on 2026-07-28

Spec support unverified

What is MCP News?

MCP News is a factual catalog of Model Context Protocol servers and clients plus a primary-sourced news feed for the MCP ecosystem. Every record carries source URLs, a verification date, and a calibrated confidence score, so claims like "first-party server" or "supports the 2026-07-28 stateless revision" can be checked rather than guessed at. Records that fall below the publishing threshold stay in moderation and never appear here.