BTCFi API vs IRONCLAW BTC Node
BTCFi API is an MCP server published by aiindigo925. Marketplaces we read that list it: 1 (Official MCP Registry). 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-30. 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
| Marketplace |  BTCFi API |  IRONCLAW BTC Node |
|---|---|---|
| Official MCP Registry | Listed Version: 3.0.1 Downloads/month (npm): 137 Downloads/week (npm): 18 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 | BTCFi API | IRONCLAW BTC Node |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@aiindigo/btcfi-mcp) | Remote server (mcp.btcnode.uk/sse) |
| Transport (differs) | stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/aiindigo925/btcfi-api | github.com/cariohca-ux/x402-btc-node |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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. 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
BTCFi API
Bitcoin data for AI agents. 27 tools with x402 micropayments. No API keys needed.
IRONCLAW BTC Node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402.
How to run each
BTCFi API As a local MCP server: npm package
claude mcp add --env "SVM_PRIVATE_KEY=<YOUR_SVM_PRIVATE_KEY>" --transport stdio btcfi -- npx -y @aiindigo/btcfi-mcpRequires: SVM_PRIVATE_KEY (secret)
IRONCLAW BTC Node As a remote MCP server
claude mcp add --transport sse btc-node https://mcp.btcnode.uk/sseCommands 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
The marketplaces of IRONCLAW BTC Node publish no settings it asks for, so we do not compare settings.
What it can do: BTCFi API · What it can do: IRONCLAW BTC Node · 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.