Maestro vs io.github.bitbond/token-tool
Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.bitbond/token-tool is an MCP server published by bitbond. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 497 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.1 Forks (GitHub): 1 Stars (GitHub): 6 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 | io.github.bitbond/token-tool |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 6 (worse) |
| Pulls (Docker Hub) (differs) | 31 497 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/maestro-mcp-server) | On your machine (token-tool-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 35 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/maestro-org/maestro-mcp-server | github.com/bitbond/token-tool-mcp |
| 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.
io.github.bitbond/token-tool
Deploy compliant ERC-20 tokens from any AI agent. 17 tools, 10 networks, CertiK-audited.
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)
io.github.bitbond/token-tool As a local MCP server: npm package
claude mcp add --env "BITBOND_PRIVATE_KEY=<YOUR_BITBOND_PRIVATE_KEY>" --transport stdio token-tool -- npx -y token-tool-mcpRequires: BITBOND_PRIVATE_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 io.github.bitbond/token-tool 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 io.github.bitbond/token-tool asks for
BITBOND_PRIVATE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Maestro · What it can do: io.github.bitbond/token-tool · 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.