Skip to main content
Glama
KhushalB25

encrypted-vault-mcp

by KhushalB25

Related Servers

Alternatives to encrypted-vault-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
      57 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local, encrypted password vault with AES-256-GCM and PBKDF2, exposing MCP tools for secure credential management, password generation, and search.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      AES-256-GCM encrypted local secret storage exposed as MCP tools, with secrets captured via native OS dialogs and never passing through the LLM API.
      -
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to securely store and manage encrypted secrets locally while using them indirectly through environment-variable injection or file writes, so plaintext values never enter the agent's context.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to fetch API keys and tokens on demand from an encrypted local vault instead of pasting them into chats, and to scan project folders for plaintext secrets. It also manages credential entries with templates, rotation tracking, usage logs, backups, and .env export.
      MIT

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool addresses a unique action: init, unlock/lock for session management, store/fetch/remove for CRUD, list for key enumeration, status for vault info, and change_pin for rotation. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names use consistent lowercase snake_case with a verb_noun pattern (e.g., change_pin, list, store). No mixing of conventions or vague verbs like 'process' or 'do'.

    Tool Count5/5

    9 tools is ideal for an encrypted vault: covering initialization, authentication, CRUD, listing, status, and PIN rotation. No unnecessary tools and no critical gaps.

    Completeness5/5

    The tool surface covers the complete vault lifecycle: init (create), unlock/lock (session), store/fetch/remove (data management), list (inventory), status (health), and change_pin (maintenance). Missing a 'delete vault' tool but that's a rare operation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues