Skip to main content
Glama
AiAgentKarl

enterprise-auth-mcp-server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to enterprise-auth-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-opa-authz

      kanywst
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enforces authorization by evaluating Rego policies or querying an OpenID AuthZEN-compliant PDP, providing accurate access decisions for AI agents. It includes tools for policy evaluation, AuthZEN evaluation, batch evaluation, and PDP discovery.
      MIT

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      1
      MIT

    • guardrails-mcp-server

      ExpertVagabond
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.
      42 npm
      1
      MIT

    • identity-aware-mcp-server

      pravin-khandke
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that authenticates agents via OAuth 2.1 Bearer tokens, validates JWTs with JWKS, enforces tool-level scopes and roles, and logs the full delegation chain.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    8 tools is well-scoped for an enterprise auth server. Each tool covers a distinct authentication or authorization operation without unnecessary duplication or gaps.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources