Ext Ops Panel
Open dashboard
Comparison

Maestro vs io.github.wygogogo19/robotbase-mcp

Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.wygogogo19/robotbase-mcp is an MCP server published by wygogogo19. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceMaestroio.github.wygogogo19/robotbase-mcp
Docker MCP Catalog Listed
Version: sha256:00309c887383
Forks (GitHub): 3
Pulls (Docker Hub): 31 864
Stars (Docker Hub): 1
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.32.2
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

Maestro vs io.github.wygogogo19/robotbase-mcp
FactMaestroio.github.wygogogo19/robotbase-mcp
Marketplaces that list it11
Stars (GitHub) (differs)25 (better)0 (worse)
Pulls (Docker Hub) (differs)31 864No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)Not published2026-10-26
Where it runs (differs)On your machine (mcp/maestro-mcp-server)Remote server (robotbase.cc/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)35Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/maestro-org/maestro-mcp-servergithub.com/wygogogo19/robotbase-mcp
Changes in the last 7 days (differs)09
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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.

io.github.wygogogo19/robotbase-mcp

In its own words, on Official MCP Registry:

Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.

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)

io.github.wygogogo19/robotbase-mcp As a remote MCP server

Claude Code
claude mcp add --transport http robotbase-mcp https://robotbase.cc/mcp

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

Only io.github.wygogogo19/robotbase-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Only Maestro has

  • 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

Only io.github.wygogogo19/robotbase-mcp has

  • broadcast_raw_transaction
  • btc_get_address
  • btc_get_block
  • btc_get_fee_rates
  • btc_get_mempool_state
  • btc_get_network_stats
  • btc_get_transaction
  • chain_status
  • crypto_trending
  • eth_get_account
  • eth_get_block
  • eth_get_fee_rates
Show the remaining 53
  • eth_get_logs
  • eth_get_transaction
  • eth_read_contract
  • list_chains
  • prediction_market_odds
  • robotbase_capabilities
  • robotbase_services
  • tron_check_address_risk
  • tron_get_account
  • tron_get_block
  • tron_get_chain_economics
  • tron_get_contract
  • tron_get_current_block
  • tron_get_node_status
  • tron_get_transaction
  • tron_list_proposals
  • tron_list_witnesses
  • tron_read_contract
  • tron_verify_usdt_transfer
  • web_act
  • web_crawl
  • web_crawl_async
  • web_crawl_job
  • web_diff
  • web_extract
  • web_extract_schema
  • web_feed
  • web_fetch
  • web_fetch_batch
  • web_map
  • web_metadata
  • web_monitor_delete
  • web_monitor_list
  • web_monitor_set
  • web_screenshot
  • web_search
  • xmr_get_block
  • xmr_get_fee_rates
  • xmr_get_mempool_state
  • xmr_get_network_stats
  • xmr_get_node_status
  • xmr_get_output_distribution
  • xmr_get_recent_blocks
  • xmr_get_transaction
  • xmr_merchant_report
  • xmr_mining_profitability
  • xmr_verify_payment
  • xmr_wallet_balance
  • zec_get_network_stats
  • zec_get_pool_status
  • zec_get_recent_blocks
  • zec_get_transaction
  • zec_get_treestate

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.wygogogo19/robotbase-mcp as of 2026-10-23). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of io.github.wygogogo19/robotbase-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Maestro · What it can do: io.github.wygogogo19/robotbase-mcp · 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.

Where the data comes from: how the catalog is built