Ext Ops Panel
Open dashboard
Comparison

Maestro vs Crypto Perps Pulse MCP

Maestro is an MCP server published by maestro-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Crypto Perps Pulse MCP is an MCP server published by donniertf-hub. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
MarketplaceMaestroCrypto Perps Pulse MCP
Docker MCP Catalog Listed
Version: sha256:00309c887383
Forks (GitHub): 3
Pulls (Docker Hub): 32 115
Stars (Docker Hub): 1
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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 Crypto Perps Pulse MCP
FactMaestroCrypto Perps Pulse MCP
Marketplaces that list it11
Stars (GitHub) (differs)25 (better)0 (worse)
Pulls (Docker Hub) (differs)32 115No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/maestro-mcp-server)Remote server (trading-data-mcp.donniertf.workers.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-servergithub.com/donniertf-hub/uk-mcp-fleet
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-29
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 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

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.

Crypto Perps Pulse MCP

In its own words, on Official MCP Registry:

Crypto perps funding rates, open interest and movers. Read-only, not financial advice.

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)

Crypto Perps Pulse MCP As a remote MCP server

Claude Code
claude mcp add --transport http trading-data-mcp https://trading-data-mcp.donniertf.workers.dev/mcp

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

Only Crypto Perps Pulse MCP has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Crypto Perps Pulse MCP publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Crypto Perps Pulse MCP publish no settings it asks for, so we do not compare settings.

What it can do: Maestro · What it can do: Crypto Perps Pulse 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