Skip to main content
Glama
privacyplaybook

sops-mcp

by privacyplaybook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to sops-mcp

No user-submitted related servers found.

    Related Servers

    • simple-secret-storage

      megamen32
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for end-to-end encrypted secret storage and retrieval, enabling LLM agents to fetch secrets by name via one-time URLs while keeping plaintext out of model context and logs.
      1
      -

    • safe-key-mcp

      Yormede
      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

    • demipass

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

    • agent-secrets

      nyx-builds
      A
      license
      Not graded
      quality
      B
      maintenance
      Encrypted secrets management MCP server for AI agents, enabling secure storage, retrieval, rotation, and auditing of API keys and credentials with AES-128 encryption.
      MIT

    • 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.
      112 npm
      30
      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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct roles (update_external vs rotate_generated vs add_secrets are well-differentiated by their descriptions). The main overlap is between sops_create_secrets and sops_add_secrets, and especially sops_create_oidc_secret which is explicitly a convenience wrapper over create_secrets, but the descriptions make the boundaries clear enough to choose correctly.

    Naming Consistency4/5

    All tools use a consistent sops_verb_noun snake_case pattern (sops_create_secrets, sops_delete_secrets, sops_list_domains). Minor deviations: sops_update_external drops the 'secrets' noun and sops_rename_secret uses singular 'secret' whereas peers use plural, but the convention is still predictable.

    Tool Count5/5

    11 tools is well-scoped for a SOPS secret lifecycle server, with each mutation, read, and maintenance operation earning its place. No redundant or filler tools.

    Completeness4/5

    Covers creation, addition, deletion, renaming, rotation, metadata, rekeying, domain listing, and external update — a solid lifecycle surface. The notable gap is a tool to decrypt/read plaintext values of existing secrets (list_secrets only exposes key names), which could force workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources