Ext Ops Panel
Open dashboard
Comparison

BTCFi API vs Satoshidata Wallet Intel

BTCFi API is an MCP server published by aiindigo925. Marketplaces we read that list it: 1 (Official MCP Registry). Satoshidata Wallet Intel is an MCP server published by wrbtc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceBTCFi APISatoshidata Wallet Intel
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
No figure published
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

BTCFi API vs Satoshidata Wallet Intel
FactBTCFi APISatoshidata Wallet Intel
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@aiindigo/btcfi-mcp)Remote server (satoshidata.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/aiindigo925/btcfi-apiNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 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

In its own words, on Official MCP Registry:

Bitcoin data for AI agents. 27 tools with x402 micropayments. No API keys needed.

Satoshidata Wallet Intel

In its own words, on Official MCP Registry:

Bitcoin wallet intelligence for AI agents: trust, labels, tx verify, fees, and timestamps.

How to run each

BTCFi API As a local MCP server: npm package

Claude Code
claude mcp add --env "SVM_PRIVATE_KEY=<YOUR_SVM_PRIVATE_KEY>" --transport stdio btcfi -- npx -y @aiindigo/btcfi-mcp

Requires: SVM_PRIVATE_KEY (secret)

Satoshidata Wallet Intel As a remote MCP server

Claude Code
claude mcp add --transport http wallet-intelligence https://satoshidata.ai/mcp/ --header "X-WR-API-Key: <YOUR_X_WR_API_KEY>"

Requires: X-WR-API-Key header

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

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

What it can do: BTCFi API · What it can do: Satoshidata Wallet Intel · 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