io.github.A0Nexus-bit/a0nexus-bitcoin-mcp
NPM · A0NEXUS-BITCOIN-MCP
Crypto (BTC/ETH) + ERCOT electricity data & forecasts as MCP tools. Pay-per-call via x402.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 114 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 906 tokens (~53/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/a0nexus-bitcoin-mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_broadcast_timing ~97
Best time to broadcast: given live mempool pressure and the fee forecast, whether to send a Bitcoin transaction now or wait, with the expected sat/vB savings (and total sats if you pass the tx vsize). Paid.
| Name | Type | Req | Description |
|---|---|---|---|
| target | integer | – | Desired confirmation window in blocks (1–144, default 6). |
| vsize | integer | – | Transaction virtual size in vB, to get total sats saved. |
No output schema declared.
No examples provided.
get_current_fees ~37
Current recommended Bitcoin fee rates (sat/vB) by confirmation target, from a full node's estimator. FREE — no wallet needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ercot_cheapest_window ~106
Cheapest upcoming window to run electricity load on the Texas (ERCOT) grid — when to charge/compute in the next 24h and how far below the daily average. Paid.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_hours | integer | – | Search horizon in hours (1–48, default 24). |
| hub | string | – | ERCOT hub (default HB_HUBAVG). |
| window_hours | integer | – | Window length in hours (1–12, default 2). |
No output schema declared.
No examples provided.
get_ercot_price_current ~71
Current Texas (ERCOT) grid electricity price in $/MWh plus a cheap/normal/expensive level. FREE — no wallet needed.
| Name | Type | Req | Description |
|---|---|---|---|
| hub | string | – | ERCOT hub, e.g. HB_HUBAVG (default), HB_HOUSTON, HB_WEST. |
No output schema declared.
No examples provided.
get_ercot_price_forecast ~79
Texas (ERCOT) electricity price forecast ($/MWh) for the next N hours, from hour-of-week seasonality anchored to the recent level. Paid.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Hours ahead (1–48, default 12). |
| hub | string | – | ERCOT hub (default HB_HUBAVG). |
No output schema declared.
No examples provided.
get_eth_gas_current ~41
Current Ethereum gas in gwei: next-block base fee plus slow/standard/fast priority-fee tiers and congestion. FREE — no wallet needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_eth_gas_forecast ~61
Forward Ethereum base-fee forecast (gwei), projected N blocks ahead via the EIP-1559 rule, with a trend label. Paid.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | integer | – | Blocks ahead to project (1–30, default 5). |
No output schema declared.
No examples provided.
get_eth_gas_timing ~79
Best time to send an Ethereum transaction: send now vs. wait, plus the gwei/ETH you'd save at a given gas limit. Paid.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | integer | – | Blocks ahead (1–30, default 5). |
| gas_limit | integer | – | Gas limit for total-savings calc (default 21000). |
No output schema declared.
No examples provided.
get_fee_forecast ~21
Forecast of Bitcoin transaction fees by confirmation target (paid).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_intelligence ~41
Aggregated Bitcoin intelligence brief, optionally per timeframe (paid).
| Name | Type | Req | Description |
|---|---|---|---|
| timeframe | string | – | Optional, e.g. 1d. Omit for default. |
No output schema declared.
No examples provided.
get_latest_forecast ~55
Latest published price forecast for a symbol + timeframe (paid).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | e.g. BTCUSD |
| timeframe | string | yes | e.g. 1h, 4h, 1d |
No output schema declared.
No examples provided.
get_mempool_snapshot ~40
Current Bitcoin mempool: transaction count, total vsize, min/relay fee, and the fee-rate histogram. FREE — no wallet needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_network_snapshot ~37
Bitcoin network snapshot: chain height, best block hash, peers, sync state, and a mempool summary. FREE — no wallet needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~19
Per-endpoint pricing and payment network (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_status ~20
Service status, payment mode, and component health (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tx_confirmation ~32
Confirmation status / ETA for a Bitcoin transaction (paid).
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Transaction id (hex). |
No output schema declared.
No examples provided.
run_custom_forecast ~70
Run a bespoke Kronos forecast (paid POST).
| Name | Type | Req | Description |
|---|---|---|---|
| horizon | integer | yes | Steps to forecast ahead. |
| lookback | integer | yes | Historical candles of context. |
| sample_count | integer | yes | Monte-Carlo sample paths. |
| symbol | string | yes | – |
| timeframe | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp runs locally as an npm package, launched with npx -y a0nexus-bitcoin-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · a0nexus-bitcoin-mcp
claude mcp add a0nexus-bit-a0nexus-bitcoin-mcp -- npx -y a0nexus-bitcoin-mcp
What is the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp is listed in the public MCP registry as io.github.A0Nexus-bit/a0nexus-bitcoin-mcp. Crypto (BTC/ETH) + ERCOT electricity data & forecasts as MCP tools. Pay-per-call via x402. This page covers its npm package (a0nexus-bitcoin-mcp).
Is the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server safe to use?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp scores 79 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server expose?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp exposes 17 tools: get_status, get_pricing, get_current_fees, get_network_snapshot, get_mempool_snapshot, and 12 more. Their descriptions and schemas cost roughly 906 tokens of context every time the server is loaded.
Is the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server still maintained?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.A0Nexus-bit/a0nexus-bitcoin-mcp server under?
io.github.A0Nexus-bit/a0nexus-bitcoin-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.