{"issuer":"https://betadomain.de","authorization_endpoint":"https://betadomain.de/oauth/authorize/","token_endpoint":"https://betadomain.de/oauth/token/","registration_endpoint":"https://betadomain.de/oauth/register/","scopes_supported":["mcp:read","mcp:write"],"response_types_supported":["code"],"grant_types_supported":["authorization_code","refresh_token"],"code_challenge_methods_supported":["S256"],"token_endpoint_auth_methods_supported":["none","client_secret_post"],"revocation_endpoint":"https://betadomain.de/oauth/revoke/","revocation_endpoint_auth_methods_supported":["none","client_secret_post"],"poppy_domains":["betadomain.de"],"service_documentation":"https://betadomain.de/.well-known/auth.md","description":"OAuth-2.1-Authorization-Server für den betadomain-MCP-Server (MCP-Authorization-Spec 2025-06-18). PKCE mit S256 ist PFLICHT. Nutzer authentifizieren sich per betadomain-Login (Firebase); Clients registrieren sich dynamisch (RFC 7591) am registration_endpoint. Access-/Refresh-Tokens sind opaque. Alternativ steht weiterhin der Bearer-Personal-Access-Token (Portal /account/profile) zur Verfügung."}