DROPGoogle launches Gemini 3.8 Flash TTS and Flash-Lite TTS///DROPGemini Omni brings 1080p generation to Google Vids///BREAKClaude Opus 5.5 is here: 1M context, $4 input / $20 output///BREAKOpenAI adds GPT-6 Sol and Luna to the GPT-6 family///PAPEROpus 5.5's system card documents gains—and evaluation limits///BREAKGrok 4.7 launches at $2 input / $6 output per million tokens///DROPGrok Voice Transcribe 2.0 targets difficult real-world audio///TRENDGoogle steers new Gemini API projects to 3.8 Flash or 3.5 Flash-Lite///DROPGoogle launches Gemini 3.8 Flash TTS and Flash-Lite TTS///DROPGemini Omni brings 1080p generation to Google Vids///BREAKClaude Opus 5.5 is here: 1M context, $4 input / $20 output///BREAKOpenAI adds GPT-6 Sol and Luna to the GPT-6 family///PAPEROpus 5.5's system card documents gains—and evaluation limits///BREAKGrok 4.7 launches at $2 input / $6 output per million tokens///DROPGrok Voice Transcribe 2.0 targets difficult real-world audio///TRENDGoogle steers new Gemini API projects to 3.8 Flash or 3.5 Flash-Lite///
DARC.DEV

[ SIGNAL — PAPER · published 28 Jul 2026 ]

The current MCP specification changes protocol and authorization assumptions

The 2026-07-28 release introduces a stateless protocol core, multi-round-trip requests, routing headers, cacheable list results and authorization hardening. It retains compatibility paths while moving toward Client ID Metadata Documents for client registration.

← Back to the newsroom
Source-checked Sources & corrections

The practical read

This is a July specification, not a new September launch. Pin your SDK and protocol versions before adapting an older integration tutorial.

Editorial interpretation, separate from the provider announcement

Who should pay attention

Developers maintaining MCP integrations

One useful next step

Compare the actual client/server SDK versions with the 2026-07-28 specification before changing authorization code.

Before you act on the headline

  • Distinguish HTTP authorization from STDIO environment credentials.
  • Validate token audience and issuer according to the specification.
  • Test rejected scopes and cross-user resource access.

Original source

Read Model Context Protocol

The date above belongs to the original announcement, not this site's build time. Prices, rollout status and provider claims should be read with the source's conditions. This briefing does not claim an independent product test.