Skip to main content
Glama
vaulted-fyi

Vaulted MCP Server

by vaulted-fyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Vaulted MCP Server

No user-submitted related servers found.

    Related Servers

    • zKettle

      benderterminal
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination
      3
      AGPL 3.0

    • 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

    • secrets-mcp-server

      KauaLealz
      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

    • SecureNote.link MCP Server

      jackalterman
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create end-to-end encrypted, self-destructing notes that can be securely shared via a one-click link, ensuring secrets are never stored in plain text in chat history.
      1
      -

    • agentkeychain

      linsipeng
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a zero-knowledge credential vault for AI agents, allowing secure storage, retrieval, and management of secrets with cross-agent delegation and tamper-evident audit.
      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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: check_status monitors secret usage, create_secret generates new secrets, list_secrets provides an overview of existing secrets, and view_secret retrieves and decrypts secrets. The descriptions clearly differentiate between monitoring, creation, listing, and retrieval actions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (check_status, create_secret, list_secrets, view_secret) with clear, descriptive names that accurately reflect their functions. There are no deviations in naming conventions across the set.

    Tool Count5/5

    With 4 tools, this server is well-scoped for managing secure secrets, covering the essential CRUD-like operations: create, list, view, and check status. Each tool earns its place without redundancy or bloat, making it easy for agents to navigate.

    Completeness5/5

    The tool set provides complete coverage for the secret-sharing domain: create_secret handles creation, list_secrets and check_status cover monitoring and status, and view_secret handles retrieval. There are no obvious gaps, as all lifecycle stages (creation, viewing, monitoring, expiration) are addressed.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources