BSV MCP vs ChainRPC MCP
BSV MCP is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
BSV MCP is a plugin bundle for AI coding tools published by b-open-io. No marketplace we read lists it any more. ChainRPC MCP is an MCP server published by John0n1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace b-open-io/claude-plugins | Removed on 2026-10-17 Version: 0.6.3 Forks (GitHub): 9 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.2 Downloads/month (npm): 145 Downloads/week (npm): 17 Forks (GitHub): 0 Stars (GitHub): 4 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 | BSV MCPno longer listed · | ChainRPC MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 22 | 4 |
| Forks (GitHub) (differs) | 9 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (bsv-mcp) | Remote server (chainrpc-mcp.mitander.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/b-open-io/bsv-mcp | github.com/john0n1/chainrpc-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-15 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of BSV MCP
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
49 Bitcoin tools for AI agents: fees, mempool, blocks, mining, price. Zero config.
-
chia-mcp io.github.danieljperry/chia-mcp
MCP server for the Chia blockchain. Read-only full-node access via Coinset hosted nodes, 36 tools.
-
mcp-server io.github.sudzikcoin/mcp-server
Pay-per-call x402 tools: crypto market pulse, wallet reputation, token check, endpoint search.
-
mcp-server io.github.aibtcdev/mcp-server
Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments.
-
Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC.
-
blockchair-mcp io.github.mrfentmen/blockchair-mcp
Blockchain stats from Blockchair. No key required.
What each says it does
BSV MCP
Bitcoin SV MCP server with interactive dashboard — Explorer, Wallet, and Ordinals via MCP Apps. Price, transactions, wallet, NFT marketplace.
ChainRPC MCP
Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions
How to run each
BSV MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ChainRPC MCP As a remote MCP server
claude mcp add --transport http chainrpc-mcp https://chainrpc-mcp.mitander.io/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChainRPC MCP 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 BSV MCP publish no settings it asks for, so we do not compare settings.
What it can do: BSV MCP · What it can do: ChainRPC MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.