Skip to main content
Glama
ars-system

MCP Credentials Broker

by ars-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Credentials Broker

No user-submitted related servers found.

    Related Servers

    • OAuth MCP Server

      walkerpauldavid
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for OAuth 2.0 authentication supporting Device Code and Client Credentials flows, enabling secure token management for MCP applications.
      -

    • cryptofort

      bradley-t-t
      A
      license
      Not graded
      quality
      A
      maintenance
      Encrypted-at-rest credential vault with MCP server for agent credential lookup and management.
      8 npm
      MIT

    • mcp-gateway

      R0Wi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      MIT

    • Attenza

      maxhillaert
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides OAuth-based MCP integration and client-side tooling for connecting agents to a remote service, with CLI and plugin support.
      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.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: storage, reference issuance, reference resolution, token minting, token revocation, OAuth initiation, and stats. The two-step get_secret/resolve_secret flow is clearly distinguished by their descriptions, and mint_token vs start_oauth_flow differentiate direct minting from interactive OAuth.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_secret, mint_token, revoke_token, start_oauth_flow, get_broker_stats). No mixed conventions.

    Tool Count5/5

    7 tools is well-scoped for a credentials broker, covering core operations without redundancy or bloat.

    Completeness4/5

    The surface covers the full lifecycle of storing, referencing, resolving, minting, and revoking credentials, plus OAuth and stats. Minor gaps include lack of explicit delete/update for secrets or a listing API, but the core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources