AWS Core vs Proxbase
AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Proxbase is an MCP server published by virtbase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  Proxbase |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f624682618e2 Forks (GitHub): 1 805 Pulls (Docker Hub): 128 530 Stars (Docker Hub): 3 Stars (GitHub): 9 776 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 1 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 | Proxbase |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 776 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 128 530 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-core-mcp-server) | On your machine (ghcr.io/virtbase/proxbase:0.2.1) |
| Transport | stdio | stdio |
| 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/virtbase/proxbase |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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.
Proxbase
Create, test and break real Proxmox VE clusters in QEMU/KVM on the local host.
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-serverProxbase As a local MCP server: Docker image
claude mcp add --transport stdio proxbase -- docker run -i --rm --device /dev/kvm --group-add "<YOUR_KVM_GID>" --network host --volume proxbase:/data ghcr.io/virtbase/proxbase:0.2.1 mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Proxbase 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: Proxbase · 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.