Skip to main content
Glama
Pappa

mcp-oidc-proxy

by Pappa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-oidc-proxy

No user-submitted related servers found.

    Related Servers

    • mcp-keycloak

      ndigrazia
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables secure MCP tool calls (add and multiply numbers) by validating OAuth2 tokens via Keycloak token introspection.
      -

    • MCP OAuth — Convex

      manufacts
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to authenticate through Convex OAuth Provider, verifying access tokens and exposing a whoami tool for retrieving the authenticated user's identity and scopes.
      MIT

    • claude-ia-mcp-tools-auth

      vicboma1
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables an MCP server with OAuth authentication, protecting tools like user CRUD operations behind session tokens obtained through a browser-based authentication flow.
      -

    • mcp-oauth-starter

      specter-systems
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables deploying a remote MCP server with OAuth 2.1 resource-server authorization, protecting tools behind validated bearer tokens and RFC 9728 discovery.
      MIT
    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

    B3.2/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action with clear descriptions that explicitly disambiguate similar pairs (e.g., decode_token vs verify_token, create_user vs create_persona_user). No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, using standard verbs like get, list, create, update, delete, rotate, and save. Minor variations (list_users vs get_user) reflect conventional list-vs-fetch semantics.

    Tool Count2/5

    At 26 tools, the server exceeds the 25-tool threshold for 'too many' defined in the rubric. While the broad scope of an OIDC proxy justifies many operations, the count is above the well-scoped range and may overwhelm an agent with options.

    Completeness4/5

    The tool set provides comprehensive coverage: CRUD for users and clients, token generation and verification, key management, audit logging, and config lifecycle (validate, reload, save). Minor gaps exist (e.g., no granular audit log deletion or token introspection), but they do not create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources