PulseAugur
EN
LIVE 08:02:07

OAuth adoption lags July 2026 spec: Only 8% of servers comply

A recent analysis of 2,967 servers advertising OAuth found that only 8% fully comply with the July 2026 specification, specifically regarding RFC 9728 and RFC 9207. While older OAuth functionalities are well-implemented, the newer requirements for protected resource metadata and issuer identification show significantly lower adoption rates. The issue appears widespread across many operators rather than concentrated with a few providers, suggesting a broad migration challenge rather than a specific vendor fault. AI

IMPACT Low adoption of new OAuth security standards may impact AI agent connectivity and data access.

RANK_REASON Analysis of technical specification adoption rates. [lever_c_demoted from research: ic=1 ai=0.4]

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

OAuth adoption lags July 2026 spec: Only 8% of servers comply

How we ranked this

Signal score
13 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
Analysis of technical specification adoption rates. [lever_c_demoted from research: ic=1 ai=0.4]
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, policy
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
Standard
On-topic for AI-industry coverage; kept in the public index.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Baramwork ·

    2,967 MCP servers advertise OAuth. 8% meet the July spec.

    <p>I scanned every server in the official MCP registry and checked the ones that advertise OAuth against the <code>2026-07-28</code> authorization requirements.</p> <p>Read-only throughout: one <code>initialize</code> per host to see what it answers, then public metadata document…