Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
A0nexus Bitcoin is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
6
downloads a day
local
runs on your machine
296
downloads in 30d
What it does
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 account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user a0nexus-bitcoin-mcp '--' npx -y a0nexus-bitcoin-mcp
# 2 — ask your agent for something these tools do
# get_status, get_pricing, get_current_fees and 14 more
A0nexus Bitcoin costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ABAll 1 server
a0nexus-bit1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts A0nexus Bitcoin as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user a0nexus-bitcoin-mcp '--' npx -y a0nexus-bitcoin-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take BTCI_API_URL (Base URL of the a0nexus API.), BTCI_MCP_PAYMENT (Set to 'real' to enable the paid tools (otherwise only the free tools work).), BTCI_MCP_PRIVATE_KEY (Base wallet private key used to pay for paid tools when BTCI_MCP_PAYMENT=real.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Service status, payment mode, and component health (free).
No parameter schema on file.
Per-endpoint pricing and payment network (free).
No parameter schema on file.
Current recommended Bitcoin fee rates (sat/vB) by confirmation target,
No parameter schema on file.
Bitcoin network snapshot: chain height, best block hash, peers, sync
No parameter schema on file.
Current Bitcoin mempool: transaction count, total vsize, min/relay fee,
No parameter schema on file.
Best time to broadcast: given live mempool pressure and the fee forecast,
No parameter schema on file.
Forecast of Bitcoin transaction fees by confirmation target (paid).
No parameter schema on file.
Confirmation status / ETA for a Bitcoin transaction (paid).
No parameter schema on file.
Latest published price forecast for a symbol + timeframe (paid).
No parameter schema on file.
Run a bespoke Kronos forecast (paid POST).
No parameter schema on file.
Aggregated Bitcoin intelligence brief, optionally per timeframe (paid).
No parameter schema on file.
Current Ethereum gas in gwei: next-block base fee plus slow/standard/fast
No parameter schema on file.
Forward Ethereum base-fee forecast (gwei), projected N blocks ahead via the
No parameter schema on file.
Best time to send an Ethereum transaction: send now vs. wait, plus the
No parameter schema on file.
Current Texas (ERCOT) grid electricity price in $/MWh plus a
No parameter schema on file.
Texas (ERCOT) electricity price forecast ($/MWh) for the next N hours, from
No parameter schema on file.
Cheapest upcoming window to run electricity load on the Texas (ERCOT) grid —
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install A0nexus Bitcoin or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.4 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest4fef856f57fb0a2f63110e4ca74695b534cb75f91e4625e847068ed20d9fa156
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_status | no tags | |
| get_pricing | no tags | |
| get_current_fees | no tags | |
| get_network_snapshot | no tags | |
| get_mempool_snapshot | no tags | |
| get_broadcast_timing | no tags | |
| get_fee_forecast | no tags | |
| get_tx_confirmation | no tags | |
| get_latest_forecast | no tags | |
| run_custom_forecast | no tags | |
| get_intelligence | no tags | |
| get_eth_gas_current | no tags | |
| get_eth_gas_forecast | no tags | |
| get_eth_gas_timing | no tags | |
| get_ercot_price_current | no tags | |
| get_ercot_price_forecast | no tags | |
| get_ercot_cheapest_window | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4fef856f57fb0a2f
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.4. Pin a release below and the command asks for exactly that one.
0.1.4
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish A0nexus Bitcoin can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.