Finance · Local MCP server
A0nexus Bitcoin MCP
Crypto (BTC/ETH) + ERCOT electricity data & forecasts as MCP tools. Pay-per-call via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp- Version
- 0.1.4
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-13
- Updated
- 2026-07-13
- Publisher
- A0Nexus-bit (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/A0Nexus-bit) · how
- Listed under
- Weather MCP servers, Bitcoin MCP servers
- Website
- a0nexus.com
- Repository
- github.com/A0Nexus-bit/a0nexus-bitcoin-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | a0nexus-bitcoin-mcp | 0.1.4 | stdio |
How to connect A0nexus Bitcoin MCP
A0nexus Bitcoin MCP runs locally from a Node.js package published to the npm registry: a0nexus-bitcoin-mcp version 0.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y a0nexus-bitcoin-mcp@0.1.4. It reads these environment variables: BTCI_API_URL, BTCI_MCP_PAYMENT and BTCI_MCP_PRIVATE_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"a0nexus-bitcoin-mcp": {
"command": "npx",
"args": [
"-y",
"a0nexus-bitcoin-mcp@0.1.4"
],
"env": {
"BTCI_API_URL": "<value>",
"BTCI_MCP_PAYMENT": "<value>",
"BTCI_MCP_PRIVATE_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| 42matters42matters MCP - wraps the 42matters App Market Data API (42matters.com) | Remote · HTTPLive check: ✓ handshake |
| 47620 Multichain Data API - onchain, crypto, utilities, x402 statsX402 pay-per-call: onchain data (Solana/Base/Polygon), crypto market, JWT/unit utils, x402 stats. | Remote · HTTPLive check: ✓ handshake |
| 47620 Solana DataPay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key. | Remote · HTTPLive check: ✓ handshake |
| 47620 Solana Data APIX402 pay-per-call Solana data + crypto market + JWT/unit utils for AI agents. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| A2AWireEscrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2. | Remote · HTTP, SSELive check: ✓ handshake |
| aaaa-nexus - Formally Verified AI Safety APIsFormally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup. | Remote · HTTPLive check: ✓ handshake |
| AAAA-Nexus MCPFormally verified AI safety APIs. 75+ endpoints, pay-per-call via USDC x402, no signup. | Local · stdio |
| AANetMetered coordination for agent swarms: locks, sub-keys, storage, messaging. x402 billing (USDC). | Remote · HTTPLive check: ✓ handshake |