The standard itself is not MCP-specific. As long as the client and the server adopt ID-JAG, they're golden.
RFC draft: https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-a...
RFC draft: https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-a...
So instead, you can run centralized infra to validate a user, device, what scopes their requesting and duration, and enforce policies for all your apps?
Can we get this in other OAuth 2.0 clients?