enterprise-auth-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decode_jwtA | JWT-Token dekodieren (ohne Signaturvalidierung). Gibt Header, Payload und Metadaten zurueck. Nuetzlich fuer schnelle Inspektion von Token-Inhalten. |
| validate_jwtA | JWT-Token validieren — Signatur, Ablauf und Claims pruefen. secret: HMAC-Secret oder leer fuer keine Signaturpruefung. algorithms: kommagetrennte Liste, z.B. 'HS256,RS256'. audience: erwartete Audience (optional). issuer: erwarteter Issuer (optional). |
| check_permissionsA | Prueft ob ein JWT-Token die benoetigten Scopes und Rollen besitzt. required_scopes: kommagetrennte Liste, z.B. 'read:users,write:data'. required_roles: kommagetrennte Liste, z.B. 'admin,manager'. |
| get_user_rolesA | Extrahiert Benutzerrollen und Identitaetsinformationen aus einem JWT. Unterstuetzt Standard-Claims und Keycloak realm_access/resource_access. |
| oauth_introspectB | OAuth 2.0 Token-Introspection (RFC 7662). introspection_url: Endpoint des Authorization Servers (optional). Ohne URL: lokale JWT-Dekodierung als Fallback. |
| verify_oidc_claimsA | OIDC-spezifische Claims validieren (OpenID Connect Core 1.0). Prueft: iss, sub, aud, exp, iat, nonce. Erkennt fehlende Pflicht-Claims und Audience/Issuer-Mismatches. |
| list_token_scopesA | Listet alle Scopes, Rollen und Berechtigungen aus einem JWT-Token auf. Erkennt automatisch den Identity Provider (Azure AD, Okta, Auth0, Keycloak). |
| get_oidc_discoveryA | OIDC Discovery Dokument abrufen (/.well-known/openid-configuration). Gibt alle wichtigen Endpoints (authorization, token, userinfo, jwks_uri) zurueck. Beispiel issuer_url: https://accounts.google.com oder https://login.microsoftonline.com/tenant-id |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AiAgentKarl/enterprise-auth-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server