AWS Core vs South Carolina Code
AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). South Carolina Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  AWS Core |  South Carolina Code |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f624682618e2 Forks (GitHub): 1 835 Pulls (Docker Hub): 131 913 Stars (Docker Hub): 3 Stars (GitHub): 9 839 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | AWS Core | South Carolina Code |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 839 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 131 913 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 835 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-core-mcp-server) | Remote server (gateway.pipeworx.io/south-carolina-code/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/pipeworx-io/mcp-south-carolina-code |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-27 |
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 Core
Starting point for using the awslabs MCP servers.
South Carolina Code
South Carolina Code of Laws — state statutes by citation.
How to run each
AWS Core As a local MCP server: Docker image
claude mcp add --transport stdio aws-core-mcp-server -- docker run -i --rm mcp/aws-core-mcp-serverSouth Carolina Code As a remote MCP server
claude mcp add --transport http south-carolina-code https://gateway.pipeworx.io/south-carolina-code/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only South Carolina Code has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of South Carolina Code publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: AWS Core · What it can do: South Carolina Code · 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.