Maestro vs Metis RWA Research
Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Metis RWA Research is a plugin bundle for AI coding tools published by Metis. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:00309c887383 Forks (GitHub): 3 Pulls (Docker Hub): 31 509 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Community marketplace metis-rwa/mcp | Not listed | Not seen in the last pass Version: 0.1.1 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 | Metis RWA Research |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 31 509 | 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) | Remote server (metisagent.co/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 35 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/maestro-org/maestro-mcp-server | github.com/metis-rwa/mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-13 |
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.
Metis RWA Research
Ask who controls a tokenized stock on Solana, whether you could sell it again, and how far it trades from the security it tracks. Connects to a hosted, read-only research endpoint, so there is nothing to install and no key to configure.
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-server
Requires: API_KEY_API_KEY (secret)
Metis RWA Research As a Claude Code plugin
/plugin marketplace add metis-rwa/mcp
/plugin install metis@metis-rwa
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Metis RWA Research has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Metis RWA Research publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Metis RWA Research publish no settings it asks for, so we do not compare settings.
What it can do: Maestro · What it can do: Metis RWA Research · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.