Skip to main content
Glama
KauaLealz

secrets-mcp-server

by KauaLealz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to secrets-mcp-server

No user-submitted related servers found.

    Related Servers

    • Credential Vault MCP

      CipherSatoru
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure credential storage for AI agents by encrypting secrets and providing agent-invisible references, ensuring sensitive data never leaks to the model.
      MIT

    • keyper

      sharziki
      A
      license
      Not graded
      quality
      C
      maintenance
      Encrypts and stores API keys and environment variables locally, providing them to AI agents via MCP with tools for listing, describing, getting secrets, and running commands with secret values redacted.
      2
      MIT

    • Secret MCP

      AKarenin
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to write .env files with secrets stored locally, allowing search by name/description while keeping actual secret values private and never exposed to the AI.
      5
      -

    • enigmagent-mcp

      Agnuxo1
      A
      license
      A
      quality
      D
      maintenance
      Local AES-256-GCM encrypted vault for AI agents. Resolve {{PLACEHOLDER}} secrets in prompts at runtime — LLMs never see real API keys. Argon2id key derivation, zero cloud.
      2
      58 npm
      2
      MIT

    • passkey-mcp

      TheNickSanchez
      A
      license
      A
      quality
      A
      maintenance
      A cross-platform secrets manager that stores named credential sets in the system keychain and injects them as environment variables, enabling secure secret management for AI coding assistants and CLI tools.
      5
      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

    C2.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: individual CRUD, batch creation, file import, and two separate consumption modes (file substitution vs command execution). There is no meaningful overlap or ambiguity between tool responsibilities.

    Naming Consistency4/5

    Core operations follow a consistent verb_noun pattern such as create_secret, update_secret, delete_secret, and list_secrets. The batch, import, and application tools use slightly different phrasal forms, but they remain readable and predictable.

    Tool Count5/5

    Eight tools is well-scoped for a secrets management server. It covers single operations, batch creation, file-based import, and secure usage without unnecessary redundancy or bloat.

    Completeness5/5

    The toolset provides full lifecycle coverage for secrets: create, update, delete, and list, with batch and import variants for efficiency. The absence of a plain get_secret action appears intentional for security and does not create a workflow dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources