Ext Ops Panel
Open dashboard
Comparison

Proxmox VE vs com.vpsudo/offers

Proxmox VE is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.vpsudo/offers is an MCP server published by vpsudo.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceProxmox VEcom.vpsudo/offers
Docker MCP Catalog Listed
Version: sha256:6e30b4d837b2
Forks (GitHub): 15
Pulls (Docker Hub): 33 779
Stars (Docker Hub): 3
Stars (GitHub): 209
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

Proxmox VE vs com.vpsudo/offers
FactProxmox VEcom.vpsudo/offers
Marketplaces that list it11
Stars (GitHub) (differs)209No figure on GitHub
Pulls (Docker Hub) (differs)33 779No figure on Docker Hub
Forks (GitHub) (differs)15No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/proxmox)Remote server (mcp.vpsudo.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)286Not published
Environment variables it asks for (differs)8, secrets among them: 2Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/gethosthewalrus/proxmox-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 42 h ago

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

Proxmox VE

In its own words, on Docker MCP Catalog:

Manage Proxmox VE infrastructure including virtual machines, containers, storage, networking, firewall rules, high availability, and more.

com.vpsudo/offers

In its own words, on Official MCP Registry:

Live VPS, bare metal and GPU hosting prices across ~75 providers, rescraped daily.

How to run each

Proxmox VE As a local MCP server: Docker image

Claude Code
claude mcp add --env "PROXMOX_PASSWORD=<YOUR_PROXMOX_PASSWORD>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" --transport stdio proxmox -- docker run -i --rm -e PROXMOX_PASSWORD -e PROXMOX_TOKEN_VALUE mcp/proxmox

Requires: PROXMOX_PASSWORD (secret), PROXMOX_TOKEN_VALUE (secret)

com.vpsudo/offers As a remote MCP server

Claude Code
claude mcp add --transport http offers https://mcp.vpsudo.com/mcp

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

Only com.vpsudo/offers has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of com.vpsudo/offers publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of com.vpsudo/offers publish no settings it asks for, so we do not compare settings.

What it can do: Proxmox VE · What it can do: com.vpsudo/offers · 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