BSV Skills vs IRONCLAW BTC Node
BSV Skills is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
BSV Skills is a plugin bundle for AI coding tools published by b-open-io. No marketplace we read lists it any more. IRONCLAW BTC Node is an MCP server published by cariohca-ux. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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.2.15 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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
| Fact | BSV Skillsno longer listed · | IRONCLAW BTC Node |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.btcnode.uk/sse) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/b-open-io/bsv-skills | github.com/cariohca-ux/x402-btc-node |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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 Skills
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bitcoin wallet intelligence for AI agents: trust, labels, tx verify, fees, and timestamps.
-
Block Genomics — Nexus Protocol
Prove Bitcoin block ownership via BIP-322 and register sovereign AI agents on the Nexus Protocol.
-
BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph
-
ordinals io.github.ExpertVagabond/ordinals
Bitcoin Ordinals MCP Server — inscriptions, runes, BRC-20, collections & rare sats
-
mcp-signer io.github.CryptoAPIs-io/mcp-signer
Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls
-
mcp-server io.github.lightningfaucet/mcp-server
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
What each says it does
BSV Skills
Core BSV blockchain operations - backup management, BAP identity, wallet operations, BSocial posts, and blockchain utilities
IRONCLAW BTC Node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402.
How to run each
BSV Skills
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
IRONCLAW BTC Node As a remote MCP server
claude mcp add --transport sse btc-node https://mcp.btcnode.uk/sse
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only IRONCLAW BTC Node 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
Neither one's marketplaces publish the settings it asks for.
What it can do: BSV Skills · What it can do: IRONCLAW BTC Node · 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.