Maestro vs Frankfurter
Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Frankfurter is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  Maestro |  Frankfurter |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:00309c887383 Forks (GitHub): 3 Pulls (Docker Hub): 32 322 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 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
| Fact | Maestro | Frankfurter |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 32 322 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | On your machine (mcp/maestro-mcp-server) | Remote server (gateway.pipeworx.io/frankfurter/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| 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/pipeworx-io/mcp-frankfurter |
| 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 | Status out of date: last check 40 h ago returned HTTP 200 |
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.
Frankfurter
Frankfurter MCP — wraps Frankfurter API (api.frankfurter.dev)
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)
Frankfurter As a remote MCP server
claude mcp add --transport http frankfurter https://gateway.pipeworx.io/frankfurter/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Frankfurter has a remote endpoint we check. How we check endpoints
Tools each declares
Only Maestro has
event_create_triggerevent_delete_triggerevent_get_logevent_get_triggerevent_healthcheckevent_list_logsevent_list_trigger_condition_optionsevent_list_triggersevent_update_triggerget_address_activityget_address_balanceget_address_balance_historical
Show the remaining 23
get_address_brc20get_address_brc20_transfer_inscriptionsget_address_inscription_activityget_address_inscriptionsget_address_rune_activityget_address_rune_utxosget_address_runesget_address_statisticsget_address_txsget_address_utxosget_brc20_infoget_btc_price_by_timestampget_dex_ohlcget_mempool_address_balanceget_mempool_address_runesget_rune_price_by_timestamplist_brc20_assetslist_supported_dexsrpc_block_miner_inforpc_block_volumerpc_chain_inforpc_mempool_inforpc_mempool_transactions
Only Frankfurter has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_research
Show the remaining 36
discover_toolsentity_profileforgetgenerate_llms_txtget_historicalget_latestget_timeserieskalshi_weather_edgelist_currencieslist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribeupdown_divergence_rateupdown_venue_comparevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Frankfurter as of 2026-11-07). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only Maestro asks for
API_KEY_API_KEY (secret)
Only Frankfurter asks for
PIPEWORX_API_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: Frankfurter · 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.