A0nexus MCP Server

If you already use A0nexus, the a0nexus mcp server is the piece that lets your assistant work with it directly. Predictive data as MCP tools for Claude and other AI apps: live Bitcoin + Ethereum on-chain data, best-time-to-transact timing, AI price forecasts, and Texas (ERCOT) electricity price forecasting — pay-per-call via x402 (USDC on Base), no.

What the server does

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.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• BTCI_MCP_PAYMENT — set to real to pay actual USDC. (Leave it unset, or none, for
• BTCI_MCP_PRIVATE_KEY — the private key of a Base wallet holding a little USDC
• get_broadcast_timing — Best time to broadcast (Bitcoin) — send now vs. wait, and the sat/vB you'd save. Args: target (blocks, default 6), vsize (vB, optional → total
• get_eth_gas_timing — Best 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_forecast — Ethereum base-fee forecast (gwei), N blocks ahead. Args: blocks (default 5)
• get_ercot_cheapest_window — Cheapest window to run load (Texas grid) — when to charge/compute in the next 24h + savings vs the daily average. Args: window_hours (default 2)
• get_ercot_price_forecast — ERCOT electricity price forecast ($/MWh) for the next N hours. Args: hours (default 12), hub
• get_fee_forecast — Forecast of Bitcoin transaction fees by confirmation target
• get_tx_confirmation — Confirmation status / ETA for a transaction. Args: txid
• get_latest_forecast — Latest published AI price forecast. Args: symbol (e.g. BTCUSD), timeframe (e.g. 1h, 4h, 1d)
• run_custom_forecast — Run a bespoke Kronos forecast. Args: symbol, timeframe, horizon, sample_count, lookback
• get_intelligence — Aggregated Bitcoin intelligence brief. Optional arg: timeframe

Credentials and setup notes

Configuration is passed through the environment: BTCI_API_URL, BTCI_MCP_PAYMENT, BTCI_MCP_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. A0nexus's toolset — BTCI_MCP_PAYMENT, BTCI_MCP_PRIVATE_KEY, get_broadcast_timing and 10 more — is a fair guide to whether it matches your workflow. It is maintained by nillagorilla; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against A0nexus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch A0nexus.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.