Unverified50% confidenceFactExact time
The MCP authorization specification in the 2025-06-18 revision requires implementing OAuth 2.1 (draft-ietf-oauth-v2-1-13), RFC 9728 protected resource metadata, and RFC 8414 authorization server metadata, and achieves audience binding through RFC 8707.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedMCP's permission model draws on the OAuth 2.0 authorization code flow, requiring explicit user authorization for tool invocation.74% similarUnverifiedOAuth is one of the most common authentication mechanisms in the MCP ecosystem; after a user completes identity verification on the authorization server, they receive a time-limited access token and a refreshable refresh token.70% similarPartially VerifiedMCP对外公网服务支持基于OAuth 2.1授权框架和JWT的Token认证机制69% similarUnverifiedThe authentication scheme recommended by the official MCP specification is OAuth 2.1 with PKCE.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1034594API
curl https://kongchang.com/api/v1/knowledge/claims/1034594MCP
get_claim(id=1034594)