Ext Ops Panel
Open dashboard
Comparison

AWS Cloud Control API vs secrets-vault

secrets-vault is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). secrets-vault is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAWS Cloud Control APIsecrets-vault
Docker MCP Catalog Listed
Version: sha256:b53d235b43c4
Forks (GitHub): 1 823
Pulls (Docker Hub): 14 944
Stars (Docker Hub): 0
Stars (GitHub): 9 812
Not marked · First seen
Not listed
Community marketplace barnburner121/claude-plugin-marketplace Not listed Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

AWS Cloud Control API vs secrets-vault
FactAWS Cloud Control APIsecrets-vaultno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)9 8123
Pulls (Docker Hub) (differs)14 944No figure on Docker Hub
Forks (GitHub) (differs)1 8230
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/ccapi-mcp-server)On your machine (@barnburner121/plugin-hub-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)14Not published
Environment variables it asks for (differs)4, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/barnburner121/claude-plugin-marketplace
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of secrets-vault

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • infisical-setup

    Interactive setup guide for integrating Infisical into your projects — CLI, Docker, Kubernetes, CI/CD, SDKs, and machine identity auth.

    by Infisical · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • infisical-secret-syncs

    Guide for configuring Infisical Secret Syncs to push secrets to all 48 supported destinations including AWS Secrets Manager, GCP Secret Manager, Azure Key Vault, GitHub, Vercel…

    by Infisical · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • infisical-dynamic-secrets

    Guide for configuring Infisical Dynamic Secrets — on-demand, short-lived credentials for databases, cloud IAM, SSH, and Kubernetes across all 30 providers.

    by Infisical · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • infisical-terraform

    Guide for using the Infisical Terraform Provider — HCL resources, ephemeral secrets, data sources, project roles, and Terraform Cloud OIDC integration.

    by Infisical · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • infisical-self-host

    Guide for self-hosting Infisical — Docker, Kubernetes Helm, environment variables, ENCRYPTION_KEY setup, FIPS compliance, scaling, and production hardening.

    by Infisical · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • envcp dev.fentz.envcp/envcp

    Encrypted environment variable vault with AI access policies, keeping secrets safe from AI agents.

    by envcp.fentz.dev · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

AWS Cloud Control API

In its own words, on Docker MCP Catalog:

Direct resource management with security scanning.

secrets-vault

In its own words, on Community GitHub marketplaces:

Generate secrets manager integrations (Vault, AWS, Azure)

How to run each

AWS Cloud Control API As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio awslabs-ccapi -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY mcp/ccapi-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret)

secrets-vault

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of secrets-vault publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of secrets-vault publish no settings it asks for, so we do not compare settings.

What it can do: AWS Cloud Control API · What it can do: secrets-vault · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built