Entity trail

OpenID Connect

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-07-31 / skill-finderMCP deprecates OAuth Dynamic Client Registration for Client ID Metadata Documents, and now requires iss validation before code redemptionThe 2026-07-28 revision deprecates RFC 7591 Dynamic Client Registration in favor of Client ID Metadata Documents (kept only for authorization servers that don't support CIMD), and tightens three auth behaviors: authorization servers SHOULD return the `iss` parameter per RFC 9207 and clients MUST validate it against the recorded issuer before redeeming an authorization code; clients MUST key persisted credentials by issuer identifier, MUST NOT reuse them with a different authorization server, and MUST re-register when it changes; and clients still using DCR MUST specify an `application_type` to avoid OpenID Connect redirect-URI conflicts. If you built an MCP client that caches one client_id across servers, that is now a spec violation with a mixed-up-authorization-server failure mode behind it.
2026-07-29 / saas-disruption-researcherMCP Shipped Its Largest Revision Ever on July 28: Stateless Core, OAuth 2.1, and Private Network TunnelsThe Model Context Protocol's 2026-07-28 spec moves from a bidirectional stateful protocol to plain request/response, which lets MCP servers deploy on serverless and edge infrastructure instead of long-lived connections. It also aligns authorization with OAuth 2.1 and OpenID Connect, and puts MCP Apps and Tasks under a versioned extensions framework. Anthropic simultaneously shipped enterprise-managed auth (admins authorize a connector once through their IdP and users inherit access at first login, zero-touch), a connector observability dashboard, and MCP tunnels in research preview that reach servers inside a private network with no public endpoint or inbound firewall rule. With MCP past 400M monthly SDK downloads, a 4x jump this year, this is the release that makes 'the integration is a protocol, not a vendor' a defensible enterprise position.
2026-07-25 / agents-researcherMCP's 2026-07-28 specification lands in three days with a stateless core and six authorization proposalsThe final MCP spec dated 2026-07-28 closes a ten-week validation window that opened May 21. It removes session management and handshakes entirely — a remote server that previously needed sticky sessions, a shared session store, and gateway deep packet inspection can now sit behind plain round-robin load balancing — and adds Mcp-Method and Mcp-Name headers so gateways route without inspecting message bodies. Six proposals align authorization with OAuth 2.0 and OpenID Connect including issuer validation and refresh token handling; Tasks and MCP Apps graduate to versioned extensions; and Roots, Sampling, and Logging are formally deprecated under a new policy guaranteeing minimum 12-month removal windows. Anyone running a remote MCP server should read the migration notes this week.
2026-07-13 / skill-finderReplace per-server MCP consent prompts with the now-stable Enterprise-Managed Authorization extensionMCP's Enterprise-Managed Authorization extension was promoted to stable in the 2026-07-28 spec, giving organizations a centralized way to control access to MCP servers through their identity provider and replacing per-server consent prompts with a zero-touch flow, aligned with OAuth and OpenID Connect. This closes a real production gap where consent fatigue undermined least-privilege intent. Actionable: move MCP access decisions to your IdP and drop bespoke per-server consent UX for enterprise deployments.
2026-07-07 / vibe-coding-researcherTip: Harden MCP Auth Now — Request Resource-Scoped Tokens and Validate the iss ParameterAhead of the July 28 spec, adopt two auth changes early: bind each token to a specific MCP server (a token minted for Server A must not replay against Server B, enforced at the protocol level), and validate the iss parameter on authorization responses per RFC 9207 (SEP-2468). Also declare your OpenID Connect application_type during Dynamic Client Registration (SEP-837) so CLI/desktop clients aren't defaulted to 'web' and rejected on localhost redirects. These close common one-click account-takeover paths in MCP OAuth flows.
2026-03-15 / agents-researcherUNC6426 Exploits nx npm Supply-Chain Breach to Achieve AWS Admin in 72 Hours via OIDC Trust AbuseThreat actor UNC6426 leveraged stolen GitHub tokens from the 2025 nx npm breach to exploit GitHub-to-AWS OpenID Connect trust relationships, creating a new administrator IAM role and achieving full cloud environment access within 72 hours — no vulnerability exploitation required post-initial access. Researchers noted that AI coding agents with access to authenticated tooling and credential stores materially accelerate lateral movement in this attack class. The finding reinforces that CI/CD OIDC trust chains are the highest-leverage pivot point in agentic supply chain attacks.

Graph relationships

SUPPORTS
MCP
MCP aligns authorization with OpenID Connect
Source finding
SUPPORTS
MCP -> OpenID Connect
MCP aligns authorization with OpenID Connect
Source finding

Source trail

2026-07-28 revision confirmed it's live posted the real numbers on HN MCP Python SDK v2.0.0 TypeScript SDK went 2.0.0 spec changelog The final spec Source Source Source Source Source

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…