Back to Directory/Developer Tools

io.github.A0Nexus-bit/a0nexus-bitcoin-mcp

Crypto (BTC/ETH) + ERCOT electricity data & forecasts as MCP tools. Pay-per-call via x402.

Developer ToolsTypeScriptv0.1.4

a0nexus-bitcoin-mcp

Live crypto + energy predictive data + AI forecasts, right inside Claude (and any MCP-capable AI app).

This is a Model Context Protocol server that gives your AI assistant real-time predictive intelligence — Bitcoin network, mempool, and fees; Ethereum gas; best-time-to-transact timing on both chains; AI Bitcoin price forecasts; and Texas (ERCOT) electricity price forecasting including the cheapest upcoming window to run load — all as tools it can call mid-conversation. Data comes from the a0nexus.com Predictive Intelligence API.

Live Bitcoin fees/network/mempool, Ethereum gas, and current ERCOT power prices are free and need no wallet — install it and ask "what's the current Bitcoin fee?", "what's ETH gas right now?", or "what's Texas power costing?" right away. The differentiated tools (forecasts, fee forecast, confirmation ETA, mempool depth, intelligence brief) are pay-per-call: each request is settled with a few cents of USDC on Base via x402 (HTTP 402) — no account, no signup, no subscription. You only enable paid tools if you want them.

Install it with a single npx line (below). Node 18+ required.

Tools

Free (no wallet needed)

ToolWhat it returns
get_current_feesCurrent recommended Bitcoin fee rates (sat/vB) by confirmation target.
get_network_snapshotChain height, best block hash, peers, sync state, mempool summary.
get_mempool_snapshotCurrent mempool size, fee-rate histogram, and congestion.
get_eth_gas_currentEthereum gas now (gwei): base fee + slow/standard/fast tiers + congestion.
get_ercot_price_currentTexas power now ($/MWh) on the ERCOT grid + cheap/normal/expensive level. Arg: hub.
get_statusService status, active payment mode, and component health.
get_pricingPer-endpoint pricing and the payment network in use.

Paid (require a funded Base wallet — see Paid tools)

ToolWhat it returns
get_broadcast_timingBest time to broadcast (Bitcoin) — send now vs. wait, and the sat/vB you'd save. Args: target (blocks, default 6), vsize (vB, optional → total sats saved).
get_eth_gas_timingBest time to send (Ethereum) — send now vs. wait, and the gwei/ETH you'd save. Args: blocks (default 5), gas_limit (optional).
get_eth_gas_forecastEthereum base-fee forecast (gwei), N blocks ahead. Args: blocks (default 5).
get_ercot_cheapest_windowCheapest window to run load (Texas grid) — when to charge/compute in the next 24h + savings vs the daily average. Args: window_hours (default 2), horizon_hours (default 24), hub.
get_ercot_price_forecastERCOT electricity price forecast ($/MWh) for the next N hours. Args: hours (default 12), hub.
get_fee_forecastForecast of Bitcoin transaction fees by confirmation target.
get_tx_confirmationConfirmation status / ETA for a transaction. Args: txid.
get_latest_forecastLatest published AI price forecast. Args: symbol (e.g. BTCUSD), timeframe (e.g. 1h, 4h, 1d).
run_custom_forecastRun a bespoke Kronos forecast. Args: symbol, timeframe, horizon, sample_count, lookback.
get_intelligenceAggregated Bitcoin intelligence brief. Optional arg: timeframe.

Install

Add the server to your AI app's MCP config. All three use the same one-line npx command — no clone, no build, no global install.

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "a0nexus-bitcoin": {
      "command": "npx",
      "args": ["-y", "a0nexus-bitcoin-mcp"],
      "env": {
        "BTCI_API_URL": "https://a0nexus.com"
      }
    }
  }
}

Claude Code

Add an .mcp.json at your project root:

{
  "mcpServers": {
    "a0nexus-bitcoin": {
      "command": "npx",
      "args": ["-y", "a0nexus-bitcoin-mcp"],
      "env": {
        "BTCI_API_URL": "https://a0nexus.com"
      }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "a0nexus-bitcoin": {
      "command": "npx",
      "args": ["-y", "a0nexus-bitcoin-mcp"],
      "env": {
        "BTCI_API_URL": "https://a0nexus.com"
      }
    }
  }
}

Restart the app. Your assistant can now fetch live Bitcoin fees and network status for free immediately — try asking "what's the current Bitcoin fee?"

Paid tools

The free tools work with no wallet at all. To unlock the paid tools, add two environment variables to the env block above:

"env": {
  "BTCI_API_URL": "https://a0nexus.com",
  "BTCI_MCP_PAYMENT": "real",
  "BTCI_MCP_PRIVATE_KEY": "0x……"
}
  • BTCI_MCP_PAYMENT: set to real to pay actual USDC. (Leave it unset, or none, for free-only operation.)
  • BTCI_MCP_PRIVATE_KEY: the private key of a Base wallet holding a little USDC. Each paid call spends that endpoint's price (a few cents). Fund it with only what you're comfortable spending — call get_pricing to see exact per-endpoint costs.
  • BTCI_MCP_NETWORK (optional): base (default) or base-sepolia for testnet.

Treat the private key like any secret: use a dedicated low-balance wallet, and never commit it to source control.

How it works

Paid endpoints use the x402 standard: the server requests a resource, the API replies HTTP 402 Payment Required with a price, the client signs a USDC transfer on Base and retries, and the API returns live data. It's true pay-per-call metering — no account, no signup, no monthly bill. You pay only for the calls your assistant actually makes.

Learn more and see live pricing at a0nexus.com.

License

MIT

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y a0nexus-bitcoin-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-a0nexus-bit-a0nexus-bitcoin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "a0nexus-bitcoin-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

a0nexus-bitcoin-mcpnpm

Compatible MCP Clients

io.github.A0Nexus-bit/a0nexus-bitcoin-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More