Ext Ops Panel
Open dashboard
Comparison

ScalpStream Data vs CCXT

ScalpStream Data is an MCP server published by DV1-321. Marketplaces we read that list it: 1 (Official MCP Registry). CCXT is an MCP server published by ccxt. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. 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
MarketplaceScalpStream DataCCXT
Official MCP Registry Listed
Version: 0.1.11
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 856
Downloads/week (npm): 186
Forks (GitHub): 8 926
Stars (GitHub): 44 605
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

ScalpStream Data vs CCXT
FactScalpStream DataCCXT
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)44 605 (better)
Forks (GitHub) (differs)0 (worse)8 926 (better)
Last release (differs)2026-10-28Not published
Where it runs (differs)On your machine (ghcr.io/dv1-321/scalpstream-mcp:v0.1.11)On your machine (ccxt-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/dv1-321/scalpstream-mcpgithub.com/ccxt/ccxt
Changes in the last 7 days (differs)60
First seen2026-10-112026-10-11

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

ScalpStream Data

In its own words, on Official MCP Registry:

Pay-per-call air quality, US product recalls, border waits and cheapest fuel for AI agents via x402.

CCXT

In its own words, on Official MCP Registry:

Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets

How to run each

ScalpStream Data As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVM_BASE_PRIVATE_KEY=<YOUR_EVM_BASE_PRIVATE_KEY>" --transport stdio scalpstream-mcp -- docker run -i --rm -e EVM_BASE_PRIVATE_KEY ghcr.io/dv1-321/scalpstream-mcp:v0.1.11

Requires: EVM_BASE_PRIVATE_KEY (secret)

CCXT As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ccxt-mcp -- npx -y ccxt-mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of CCXT publish no settings it asks for, so we do not compare settings.

What it can do: ScalpStream Data · What it can do: CCXT · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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