Ext Ops Panel
Open dashboard
Comparison

io.github.donnywin85/bsc-dex-spread vs EchoLedger

io.github.donnywin85/bsc-dex-spread is an MCP server published by donnywin85. Marketplaces we read that list it: 1 (Official MCP Registry). EchoLedger is an MCP server published by icmoore. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.donnywin85/bsc-dex-spreadEchoLedger
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 174
Downloads/week (npm): 12
Not marked · First seen
Listed
Version: 0.2.3
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

io.github.donnywin85/bsc-dex-spread vs EchoLedger
Factio.github.donnywin85/bsc-dex-spreadEchoLedger
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (bsc-dex-spread-mcp)Remote server (mcp.echoledger.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/donnywin85/bsc-dex-spread-mcpgithub.com/echoledger/echoledger-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (34 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

io.github.donnywin85/bsc-dex-spread

In its own words, on Official MCP Registry:

Cross-DEX price & spread for PancakeSwap v2+v3 on BSC via x402. Tool get_dex_spread(pair, fee?).

EchoLedger

In its own words, on Official MCP Registry:

Live LP analytics — Uniswap V2/V3, Balancer, Curve stableswap: PnL, health, slippage, depeg risk.

How to run each

io.github.donnywin85/bsc-dex-spread As a local MCP server: npm package

Claude Code
claude mcp add --env "EVM_PRIVATE_KEY=<YOUR_EVM_PRIVATE_KEY>" --transport stdio bsc-dex-spread -- npx -y bsc-dex-spread-mcp

Requires: EVM_PRIVATE_KEY (secret)

EchoLedger As a remote MCP server

Claude Code
claude mcp add --transport http echoledger-mcp https://mcp.echoledger.ai/mcp

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

Only EchoLedger has a remote endpoint we check. How we check endpoints

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 EchoLedger publish no settings it asks for, so we do not compare settings.

What it can do: io.github.donnywin85/bsc-dex-spread · What it can do: EchoLedger · Compare two other plugins

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