Ext Ops Panel
Open dashboard
Comparison

io.github.CryptoAPIs-io/mcp-block-data vs io.github.clawdbotworker/coinopai-mcp

io.github.CryptoAPIs-io/mcp-block-data is an MCP server published by CryptoAPIs-io. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.clawdbotworker/coinopai-mcp is an MCP server published by clawdbotworker. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceio.github.CryptoAPIs-io/mcp-block-dataio.github.clawdbotworker/coinopai-mcp
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 804
Downloads/week (npm): 23
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.2.4
Downloads/month (npm): 1 168
Downloads/week (npm): 80
Forks (GitHub): 2
Stars (GitHub): 1
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.CryptoAPIs-io/mcp-block-data vs io.github.clawdbotworker/coinopai-mcp
Factio.github.CryptoAPIs-io/mcp-block-dataio.github.clawdbotworker/coinopai-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@cryptoapis-io/mcp-block-data)On your machine (coinopai-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cryptoapis-io/cryptoapis-mcp-block-datagithub.com/forgemeshlabs/coinopai-mcp
Changes in the last 7 days00
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

io.github.CryptoAPIs-io/mcp-block-data

In its own words, on Official MCP Registry:

MCP server for retrieving block-level data from EVM, UTXO, and XRP blockchains via Crypto APIs

io.github.clawdbotworker/coinopai-mcp

In its own words, on Official MCP Registry:

Kronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base.

How to run each

io.github.CryptoAPIs-io/mcp-block-data As a local MCP server: npm package

Claude Code
claude mcp add --env "CRYPTOAPIS_API_KEY=<YOUR_CRYPTOAPIS_API_KEY>" --transport stdio mcp-block-data -- npx -y @cryptoapis-io/mcp-block-data

Requires: CRYPTOAPIS_API_KEY (secret)

io.github.clawdbotworker/coinopai-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "WALLET_PRIVATE_KEY=<YOUR_WALLET_PRIVATE_KEY>" --transport stdio coinopai-mcp -- npx -y coinopai-mcp

Requires: WALLET_PRIVATE_KEY (secret)

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

Only io.github.CryptoAPIs-io/mcp-block-data asks for

  • CRYPTOAPIS_API_KEY (secret)

Only io.github.clawdbotworker/coinopai-mcp asks for

  • WALLET_PRIVATE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.CryptoAPIs-io/mcp-block-data · What it can do: io.github.clawdbotworker/coinopai-mcp · 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