Ext Ops Panel
Open dashboard
Comparison

Bitrefill vs Maestro

Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-13. 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
MarketplaceBitrefillMaestro
Docker MCP Catalog Listed
Version: sha256:7ff5cc499284
Forks (GitHub): 1
Pulls (Docker Hub): 39 274
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: sha256:00309c887383
Forks (GitHub): 3
Pulls (Docker Hub): 31 503
Stars (Docker Hub): 1
Stars (GitHub): 25
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

Bitrefill vs Maestro
FactBitrefillMaestro
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)25 (better)
Pulls (Docker Hub) (differs)39 274 (better)31 503 (worse)
Forks (GitHub) (differs)1 (worse)3 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/bitrefill)On your machine (mcp/maestro-mcp-server)
Transportstdiostdio
Tools it declares (differs)1235
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITApache-2.0
Repository (differs)github.com/bitrefill/bitrefill-mcp-servergithub.com/maestro-org/maestro-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-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

Bitrefill

In its own words, on Docker MCP Catalog:

A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.

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.

How to run each

Bitrefill As a local MCP server: Docker image

Claude Code
claude mcp add --env "BITREFILL_API_SECRET=<YOUR_BITREFILL_API_SECRET>" --transport stdio bitrefill -- docker run -i --rm -e BITREFILL_API_SECRET mcp/bitrefill

Requires: BITREFILL_API_SECRET (secret)

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)

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

Tools each declares

Only Bitrefill declares

  • categories
  • create_invoice
  • detail
  • get_account_balance
  • get_invoice
  • get_invoices
  • get_order
  • get_orders
  • pay_invoice
  • ping
  • search
  • unseal_order

Only Maestro declares

  • event_create_trigger
  • event_delete_trigger
  • event_get_log
  • event_get_trigger
  • event_healthcheck
  • event_list_logs
  • event_list_trigger_condition_options
  • event_list_triggers
  • event_update_trigger
  • get_address_activity
  • get_address_balance
  • get_address_balance_historical
Show the remaining 23
  • get_address_brc20
  • get_address_brc20_transfer_inscriptions
  • get_address_inscription_activity
  • get_address_inscriptions
  • get_address_rune_activity
  • get_address_rune_utxos
  • get_address_runes
  • get_address_statistics
  • get_address_txs
  • get_address_utxos
  • get_brc20_info
  • get_btc_price_by_timestamp
  • get_dex_ohlc
  • get_mempool_address_balance
  • get_mempool_address_runes
  • get_rune_price_by_timestamp
  • list_brc20_assets
  • list_supported_dexs
  • rpc_block_miner_info
  • rpc_block_volume
  • rpc_chain_info
  • rpc_mempool_info
  • rpc_mempool_transactions

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Bitrefill asks for

  • BITREFILL_API_ID
  • BITREFILL_API_SECRET (secret)

Only Maestro asks for

  • API_KEY_API_KEY (secret)

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

What it can do: Bitrefill · What it can do: Maestro · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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