Maestro vs Pulse Verity
Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Pulse Verity is an MCP server published by PulseBet. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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 |  Pulse Verity |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:00309c887383 Forks (GitHub): 3 Pulls (Docker Hub): 31 839 Stars (Docker Hub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.6 Downloads/month (npm): 1 370 Downloads/week (npm): 629 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.3.6 Downloads/month (npm): 1 370 Downloads/week (npm): 629 Forks (GitHub): 0 Stars (GitHub): 3 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 | Pulse Verity |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 25 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 31 839 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (mcp/maestro-mcp-server) | Remote server or your machine |
| 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 | MIT |
| Repository (differs) | github.com/maestro-org/maestro-mcp-server | github.com/pulsebet/pulse-verity |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 28 h 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
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.
Pulse Verity
Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.
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)
Pulse Verity As a remote MCP server
claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcpRequires: PULSE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pulse Verity 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 Pulse Verity has
get_account_statusget_index_batchget_index_historyget_index_priceget_recorded_printget_upgrade_optionslist_index_assetssubmit_verity_feedbackverify_print
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Pulse Verity as of 2026-10-24). 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 Pulse Verity asks for
PULSE_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: Pulse Verity · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.