enterprise-auth-mcp-server
Provides JWT validation, OIDC claims verification, token introspection, and role/permission extraction for Auth0 tokens.
Provides JWT validation, OIDC claims verification, and token introspection for Google Identity tokens.
Provides JWT validation, OIDC claims verification, token introspection, and role/permission extraction for Keycloak tokens.
Provides JWT validation, OIDC claims verification, token introspection, and role/permission extraction for Okta tokens.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@enterprise-auth-mcp-server check if this JWT token has the admin role"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
enterprise-auth-mcp-server
MCP server for enterprise authentication and authorization — JWT validation, OIDC token inspection, OAuth 2.0 introspection, and role-based access control for AI agents.
Features
JWT Decode — Inspect token header, payload, and metadata without signature verification
JWT Validate — Validate signature, expiry, audience, and issuer
Permission Check — Verify if a token has required OAuth scopes and roles
User Roles — Extract user identity, roles, and groups (supports Keycloak, Azure AD, Auth0, Okta)
OAuth Introspection — RFC 7662 token introspection (remote endpoint or local fallback)
OIDC Claims Verify — OpenID Connect Core 1.0 claims validation
Token Scope List — List all scopes, roles, and permissions with provider auto-detection
OIDC Discovery — Fetch provider endpoints from /.well-known/openid-configuration
Related MCP server: guardrails-mcp-server
Installation
pip install enterprise-auth-mcp-serverClaude Desktop Configuration
Add to claude_desktop_config.json:
{
"mcpServers": {
"enterprise-auth": {
"command": "enterprise-auth-mcp-server"
}
}
}Tools
Tool | Description |
| Decode JWT without signature verification |
| Validate JWT signature, expiry, audience, issuer |
| Check if token has required scopes/roles |
| Extract user identity and roles from token |
| OAuth 2.0 RFC 7662 token introspection |
| Validate OIDC Core 1.0 required claims |
| List all scopes and permissions with provider detection |
| Fetch OIDC provider discovery document |
Usage Examples
Decode a JWT token
decode_jwt(token="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...")Validate a JWT with secret
validate_jwt(token="...", secret="my-secret", algorithms="HS256", audience="my-app")Check if user has admin role
check_permissions(token="...", required_roles="admin,manager")Verify OIDC claims
verify_oidc_claims(token="...", expected_issuer="https://accounts.google.com", expected_audience="my-client-id")Get OIDC provider endpoints
get_oidc_discovery(issuer_url="https://accounts.google.com")Supported Identity Providers
Azure AD / Microsoft Entra ID — Azure roles, app roles, directory roles (wids)
Okta — Groups, custom claims
Auth0 — Permissions, roles via Management API conventions
Keycloak — realm_access, resource_access
Google Identity — Standard OIDC claims
Any OIDC-compliant provider — Standards-based JWT/OIDC support
Use Cases
Enterprise MCP Deployments — Validate agent identity before granting tool access
Zero Trust Architecture — Verify every request has valid, unexpired credentials
API Gateway Integration — Check OAuth scopes for fine-grained authorization
Audit & Compliance — Extract and log user identity from authentication tokens
SSO Integration — Verify tokens from any OIDC-compliant identity provider
License
MIT License — see LICENSE for details.
Available Tools
8 toolscheck_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'.
Inputs: token (required), required_roles, required_scopes.
decode_jwtA
JWT-Token dekodieren (ohne Signaturvalidierung). Gibt Header, Payload und Metadaten zurueck. Nuetzlich fuer schnelle Inspektion von Token-Inhalten.
Inputs: token (required).
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
Inputs: issuer_url (required).
get_user_rolesA
Extrahiert Benutzerrollen und Identitaetsinformationen aus einem JWT. Unterstuetzt Standard-Claims und Keycloak realm_access/resource_access.
Inputs: token (required).
list_token_scopesA
Listet alle Scopes, Rollen und Berechtigungen aus einem JWT-Token auf. Erkennt automatisch den Identity Provider (Azure AD, Okta, Auth0, Keycloak).
Inputs: token (required).
oauth_introspectB
OAuth 2.0 Token-Introspection (RFC 7662). introspection_url: Endpoint des Authorization Servers (optional). Ohne URL: lokale JWT-Dekodierung als Fallback.
Inputs: token (required), client_id, client_secret, introspection_url.
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).
Inputs: token (required), issuer, secret, audience, +1 more.
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.
Inputs: token (required), expected_nonce, expected_issuer, expected_audience.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: decoding, validating, checking permissions, extracting roles, listing scopes, OIDC discovery, token introspection, and OIDC claims verification. Despite some thematic overlap, the descriptions ensure no ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., check_permissions, decode_jwt, get_oidc_discovery). No mixing of conventions or irregular naming.
8 tools is well-scoped for an enterprise auth server. Each tool covers a distinct authentication or authorization operation without unnecessary duplication or gaps.
The set covers core JWT operations, OIDC discovery, token introspection, and permission checking. Minor gaps like userinfo endpoint retrieval or token refresh are not critical for the server's stated purpose, so the surface is reasonably complete.
Maintenance
Related MCP Connectors
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
AI governance MCP server for EU AI Act compliance and jurisdiction verification
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.31 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.72 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseAqualityCmaintenanceMCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access31MIT