Skip to main content
Glama
Gonzih

agent-keys

by Gonzih
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to agent-keys

No user-submitted related servers found.

    Related Servers

    • ServeMyAPI

      Jktfe
      F
      license
      Not graded
      quality
      D
      maintenance
      A personal MCP server for securely storing and accessing API keys across projects using the macOS Keychain, letting AI assistants and applications retrieve credentials through natural language.
      25
      -

    • Agentic Vault

      AliProgrammin
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0

    • AgentVault

      bch1212
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI-native credential management, enabling agents to securely store, retrieve, and manage API keys with encryption, spending budgets, and audit logging.
      MIT

    • credential-broker-mcp

      SarutobiSasuke8
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.
      2
      Apache 2.0

    • safe-key-mcp

      Yormede
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling AI agents to use secrets (API keys, tokens) via encrypted vault, executing HTTP/shell/SSH actions server-side while never exposing secret values to the AI.
      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

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing services, getting/storing/checking/provisioning/removing keys, and exporting. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., list_services, get_api_key, store_api_key). The use of 'env' in export_env is a different noun but still fits the pattern.

    Tool Count5/5

    7 tools is well-scoped for managing API keys, covering all essential operations without being excessive or insufficient.

    Completeness5/5

    The tool surface covers the full lifecycle: discovery, storage, retrieval, verification, provisioning guidance, deletion, and export. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources