Skip to main content
Glama
irrenwill

secret-safe-env

by irrenwill

Related Servers

Alternatives to secret-safe-env

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that brokers access to secrets for coding agents, enabling them to perform operations like database queries and CLI commands without ever reading the underlying values.
      54 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      A local-first secrets vault for MCP clients that lets AI assistants use secrets by injecting them into child processes, without the plaintext ever entering the model's context.
      5
      -
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for creating and managing SOPS-encrypted secret files using age encryption, enabling AI agents to generate and manage secrets without ever seeing plaintext values.
      11
      25 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hostable secrets manager with an MCP server that enables AI agents to securely store, version, and retrieve API keys and tokens, ensuring they are never lost.
      MIT

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: setting a secret and checking for existence. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern (set_env_secret, env_key_exists), making them predictable.

    Tool Count4/5

    With 2 tools, the server is minimal but appropriate for its focused scope of managing .env secrets. However, the count feels slightly low for a full-featured solution.

    Completeness3/5

    The server covers setting and checking existence of secrets but lacks a tool to delete or remove secrets, which is a notable gap for lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues