Skip to main content
Glama
rosostolato

Veil

by rosostolato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Veil

No user-submitted related servers found.

    Related Servers

    • Janee

      rsdouglas
      A
      license
      Not graded
      quality
      C
      maintenance
      Secrets management MCP server that injects credentials into API requests for AI agents, enforcing policies and logging all activity without exposing raw keys.
      54 npm
      30
      MIT

    • Agentic Vault

      AliProgrammin
      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

    • AgentVault

      bch1212
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI-native credential management, enabling agents to securely store, retrieve, and manage API keys with encryption, spending budgets, and audit logging.
      MIT

    • blindfold

      xxgvqxx
      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.
      24 npm
      MIT

    • secretsminter

      scorellis
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that mints, places, and rotates cloud secrets (e.g., Cloudflare, GitHub, Supabase) without exposing secret values to the agent, using a signed destination allow-list and self-maintaining rotation.
      Apache 2.0

    • demipass

      bildow
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for DemiPass secrets management, enabling AI agents to securely store, rotate, and use credentials without exposing them in context windows.
      75 npm
      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.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: status checks a pending request, store initiates a credential request, cancel aborts it, revise replaces it, and destinations lists available targets. No overlap in purpose, making agent selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent 'secret.<action>' pattern with clear, concise verbs (status, store, cancel, revise) and one noun (destinations). The pattern is uniform and predictable, though 'destinations' is a noun rather than a verb, it still fits the domain prefix style.

    Tool Count5/5

    With 5 tools, the server is tightly scoped to credential request management. This is within the ideal range and each tool earns its place; no redundancy or bloat.

    Completeness5/5

    The tool surface covers the entire lifecycle of a credential request: create (store), read (status), update/replace (revise), delete (cancel), and context (destinations). There are no evident gaps—even revision gracefully handles invalidation of prior authorizations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources