Maestro vs ScoutWyze Compute
Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). ScoutWyze Compute is an MCP server published by scoutwyze-max. 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 |  Maestro |  ScoutWyze Compute |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:00309c887383 Forks (GitHub): 3 Pulls (Docker Hub): 31 891 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 164 Downloads/week (npm): 34 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 | Maestro | ScoutWyze Compute |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 31 891 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/maestro-mcp-server) | On your machine (@scoutwyze/compute-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 35 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/maestro-org/maestro-mcp-server | github.com/scoutwyze-max/scoutwyze-compute |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Maestro
A Model Context Protocol (MCP) server exposing Bitcoin blockchain data through the Maestro API platform. Provides tools to explore blocks, transactions, addresses, inscriptions, runes, and other metaprotocol data.
ScoutWyze Compute
Ranks current RunPod GPU offers by price and freshness. Supports x402/USDC-on-Base payments.
How to run each
Maestro As a local MCP server: Docker image
claude mcp add --env "API_KEY_API_KEY=<YOUR_API_KEY_API_KEY>" --transport stdio maestro-mcp-server -- docker run -i --rm -e API_KEY_API_KEY mcp/maestro-mcp-serverRequires: API_KEY_API_KEY (secret)
ScoutWyze Compute As a local MCP server: npm package
claude mcp add --env "SCOUTWYZE_API_KEY=<YOUR_SCOUTWYZE_API_KEY>" --transport stdio compute-mcp -- npx -y @scoutwyze/compute-mcpRequires: SCOUTWYZE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of ScoutWyze Compute publish no list of tools, so we do not compare tools.
Settings each asks for
Only Maestro asks for
API_KEY_API_KEY (secret)
Only ScoutWyze Compute asks for
SCOUTWYZE_API_KEY (secret)SCOUTWYZE_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Maestro · What it can do: ScoutWyze Compute · 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.