Ext Ops Panel
Open dashboard
Comparison

Maestro vs Agent Desk API (deskfeed.dev)

Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Agent Desk API (deskfeed.dev) is an MCP server published by deskfeed.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceMaestroAgent Desk API (deskfeed.dev)
Docker MCP Catalog Listed
Version: sha256:00309c887383
Forks (GitHub): 3
Pulls (Docker Hub): 31 685
Stars (Docker Hub): 1
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.0
No figure published
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 Agent Desk API (deskfeed.dev)
FactMaestroAgent Desk API (deskfeed.dev)
Marketplaces that list it11
Stars (GitHub) (differs)25No figure on GitHub
Pulls (Docker Hub) (differs)31 685No figure on Docker Hub
Forks (GitHub) (differs)3No figure on GitHub
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (mcp/maestro-mcp-server)Remote server (deskfeed.dev/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-serverNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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.

Agent Desk API (deskfeed.dev)

In its own words, on Official MCP Registry:

Crypto market context, BSC alerts & token verdicts for agents. x402 on Base.

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)

Agent Desk API (deskfeed.dev) As a remote MCP server

Claude Code
claude mcp add --transport http deskfeed-api https://deskfeed.dev/mcp

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

Only Agent Desk API (deskfeed.dev) 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 Agent Desk API (deskfeed.dev) has

  • bsc_alerts
  • bsc_verdict
  • event_facts
  • market_state
  • ping

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Agent Desk API (deskfeed.dev) as of 2026-10-19). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Agent Desk API (deskfeed.dev) publish no settings it asks for, so we do not compare settings.

What it can do: Maestro · What it can do: Agent Desk API (deskfeed.dev) · 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