Skip to main content
Glama
Wolstapp

stillvault-mcp

by Wolstapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to stillvault-mcp

No user-submitted related servers found.

    Related Servers

    • keyward

      arturayupov
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely use API keys by storing them in an encrypted vault and injecting them on demand with user approval, without exposing the key values to the model.
      1
      MIT

    • keywarden

      DINAKAR-S
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make authenticated API calls and run commands with secrets injected, while keeping credentials completely hidden from the model, with policy enforcement, grants, and audit logging.
      2
      6
      MIT

    • sandbox

      Boredem125
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to safely execute privileged commands by routing them to a human approver, who runs them outside the agent's context and returns the output to the model.
      5
      MIT

    • Agent Vault

      loonshoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Human-in-the-loop secret access for AI coding agents, enabling approval workflow for password manager secrets via MCP.
      1
      MIT

    • bw-proxy

      KpihX
      A
      license
      D
      quality
      D
      maintenance
      Enables secure Bitwarden organization vault control with AI agents, featuring human-in-the-loop approval, ACID-compliant transactions, and redacted access to keep secrets hidden from LLMs.
      10
      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

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    Both tools handle secrets but have clearly distinct purposes: stillvault_reveal returns the secret value to the conversation, while stillvault_run uses it in a command without revealing it. Their descriptions explicitly differentiate them and provide guidance on when to use each, leaving no ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent 'stillvault_verb' pattern in snake_case. The verb choice ('reveal' and 'run') clearly indicates their action, and the naming is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the server feels minimal but appropriately focused on its purpose: using secrets with human approval. However, it lacks any administrative tools (e.g., list, create, delete secrets), which might be expected from a secrets management server, making the count borderline.

    Completeness3/5

    The tools cover the two primary use cases (revealing and running secrets), but there is no way to discover available secrets or manage them. Agents must know the secret path in advance, which is a notable gap that could cause failures when the path is unknown.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources