Comparison

Maestro vs SatoshiAPI — Bitcoin Data via Lightning

Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). SatoshiAPI — Bitcoin Data via Lightning is an MCP server published by SatoshiAPI. 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

Where each is published
Marketplace	Maestro	SatoshiAPI — Bitcoin Data via Lightning
Docker MCP Catalog	Listed Version: sha256:00309c887383 Forks (GitHub): 3 Pulls (Docker Hub): 31 505 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 1.0.2 Downloads/month (PyPI): 106 Downloads/week (PyPI): 25 Not marked · First seen 2026-10-11

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

Maestro vs SatoshiAPI — Bitcoin Data via Lightning
Fact	Maestro	SatoshiAPI — Bitcoin Data via Lightning
Marketplaces that list it	1	1
Stars (GitHub) (differs)	25	No figure on GitHub
Pulls (Docker Hub) (differs)	31 505	No figure on Docker Hub
Forks (GitHub) (differs)	3	No figure on GitHub
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/maestro-mcp-server)	Remote server or your machine
Transport (differs)	stdio	stdio, Streamable HTTP
Tools it declares (differs)	35	Not published
Environment variables it asks for (differs)	1, secrets among them: 1	3, secrets among them: 0
Licence (differs)	Apache-2.0	Not stated
Repository (differs)	github.com/maestro-org/maestro-mcp-server	github.com/satoshiapi/satoshi-btc-api
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Not responding since 2026-10-14

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

In its own words, on Docker MCP Catalog:

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.

SatoshiAPI — Bitcoin Data via Lightning

In its own words, on Official MCP Registry:

L402 Lightning-paid Bitcoin data: price, fees, blocks, sentiment, DCA signals.

How to run each

Maestro As a local MCP server: Docker image

Claude Code

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)

SatoshiAPI — Bitcoin Data via Lightning As a local MCP server: PyPI package

Claude Code

claude mcp add --transport stdio satoshi-btc-api -- uvx satoshiapi-mcp

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

Only SatoshiAPI — Bitcoin Data via Lightning has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of SatoshiAPI — Bitcoin Data via Lightning 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 SatoshiAPI — Bitcoin Data via Lightning asks for

SATOSHIAPI_LND_CERT
SATOSHIAPI_LND_MACAROON
SATOSHIAPI_LND_REST

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Maestro · What it can do: SatoshiAPI — Bitcoin Data via Lightning · 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 2026-10-14. We publish no contact details for plugin publishers.