MCP Credentials Broker
Related Servers
Alternatives to MCP Credentials Broker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceIt enables MCP clients to authenticate with short-lived SPIFFE JWT-SVIDs as OAuth client credentials, obtaining audience-bound access tokens for scoped tool calls without static API keys.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents and services to perform on-behalf-of token exchange across enterprise systems, with scoped permission delegation, automatic token lifetime refresh, and zero-leakage ephemeral credentials. It runs as a zero-dependency MCP server over JSON-RPC stdio or as an importable Python module.7MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for OAuth 2.0 authentication supporting Device Code and Client Credentials flows, enabling secure token management for MCP applications.-
- AlicenseNot gradedqualityAmaintenanceEncrypted-at-rest credential vault with MCP server for agent credential lookup and management.11 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables secure cross-system identity and token exchange for autonomous agents, including on-behalf-of token exchange, scoped permission delegation, token lifetime refresh, and zero-leakage ephemeral credentials. It integrates with MCP-compatible clients via standard JSON-RPC stdio without external runtime dependencies.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.1MIT
TDQS
Scored across 7 tools
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.
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.
7 tools is well-scoped for a credentials broker, covering core operations without redundancy or bloat.
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.