Ext Ops Panel
Open dashboard
Comparison

AWS Cloud Control API vs ISMS Copilot

AWS Cloud Control API is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). ISMS Copilot is an MCP server published by tristanroth1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAWS Cloud Control APIISMS Copilot
Docker MCP Catalog Listed
Version: sha256:b53d235b43c4
Forks (GitHub): 1 827
Pulls (Docker Hub): 15 096
Stars (Docker Hub): 0
Stars (GitHub): 9 830
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
No figure published
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 ISMS Copilot
FactAWS Cloud Control APIISMS Copilot
Marketplaces that list it11
Stars (GitHub) (differs)9 830No figure on GitHub
Pulls (Docker Hub) (differs)15 096No figure on Docker Hub
Forks (GitHub) (differs)1 827No figure on GitHub
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/ccapi-mcp-server)Remote server (account.ismscopilot.com/v1/account/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)14Not published
Environment variables it asks for (differs)4, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 31 h ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AWS Cloud Control API

In its own words, on Docker MCP Catalog:

Direct resource management with security scanning.

ISMS Copilot

In its own words, on Official MCP Registry:

The compliance specialist your AI calls: ISO 27001, SOC 2, GDPR, NIS 2, DORA and more.

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)

ISMS Copilot As a remote MCP server

Claude Code
claude mcp add --transport http ismscopilot-account https://account.ismscopilot.com/v1/account/mcp

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

Only ISMS Copilot has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of ISMS Copilot publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of ISMS Copilot publish no settings it asks for, so we do not compare settings.

What it can do: AWS Cloud Control API · What it can do: ISMS Copilot · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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