Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Poworacle 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
207
downloads a day
local
runs on your machine
6
tools declared
What it does
Proof-of-work mining oracle: solo-mining odds, cost of production, network state, hardware, news.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user poworacle-mcp '--' npx -y @reneturcios/poworacle mcp
# 2 — ask your agent for something these tools do
# calculate_solo_mining_odds, get_cost_of_production, get_coin_oracle and 3 more
Poworacle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 381 servers
CloudCorpRecords381 servers
28 categories
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 Poworacle 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 poworacle-mcp '--' npx -y @reneturcios/poworacle 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 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
6 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Probability of a solo miner finding a block, computed as a Poisson process over live network difficulty and hashrate, plus the electricity cost of the attempt. Returns mean time to a block, the chance of at least one block over 1/7/30/90/365 days, and lucky-vs-unlucky waiting times (5th, 50th and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin_id | yes | — | |
| hashrate | number | yes | The miner's rate, as a number. The unit goes in hashrate_unit. |
| hashrate_unit | string | yes | Unit for hashrate. Most networks measure in hashes per second (H/s…EH/s). Cuckoo-family chains measure graphs per second (gps) and Aleo measures proofs per second — an unrecognised unit is rejected ra |
| power_watts | number | no | Miner power draw in watts, e.g. 3500 for an ASIC or 320 for a GPU. Optional. |
| electricity_cost_usd_kwh | no | — |
Cost of Production (CoP) for one Proof of Work coin: the all-in electricity cost of mining one unit on the most efficient hardware BackPow tracks for that algorithm, compared against spot price. Returns CoP in USD, spot, gross margin, whether miners are currently above or below water, the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin_id | yes | — | |
| electricity_cost_usd_kwh | no | — |
Current network state for one Proof of Work chain, measured by BackPow's stratum collector nodes: difficulty, derived network hashrate, block height, block reward, protocol block-time target versus the latest observed interval, and the source pool. Every response carries a confidence block — how…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin_id | yes | — |
Paginated index of the Proof of Work networks BackPow tracks, with algorithm, network rate, collector status and canonical page URL. Optionally filtered by algorithm or restricted to coins currently mining above cost. Returns the distinct algorithm list so valid filter values are discoverable. Use…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| algorithm | string | no | Case-insensitive substring filter on algorithm, e.g. "SHA-256", "Scrypt", "KawPow", "RandomX", "Autolykos". The response lists every algorithm present. |
| profitable_only | boolean | no | Restrict to coins whose spot price currently exceeds Cost of Production. Profitability is resolved for the returned page only, and the response reports how many of those coins have CoP coverage, so a |
| sort_by | string | no | Ordering. "suffering" ranks by how far Cost of Production exceeds spot price. Defaults to name. |
| limit | integer | no | Rows to return, 1-100. Defaults to 25. |
| offset | integer | no | Rows to skip for pagination. Defaults to 0. |
Mining hardware matched to the coins it can mine, ranked by net USD per day at a given electricity rate. Covers ASICs, GPUs and CPUs, with hashrate and power draw per coin, gross revenue, net profit, and market price including whether that price is an observed listing or a model estimate. Use for…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Hardware model or keyword, at least 2 characters, e.g. "RTX 4090", "Antminer S21", "Bitaxe", "Ryzen 9 7950X". Short or generic queries match hundreds of devices, so pair them with type and limit. |
| type | string | no | Restrict to one hardware class. |
| coin_id | string | no | Restrict the per-device coin rows to one network, e.g. to answer "how much does this rig make on Kaspa". Optional. |
| electricity_cost_usd_kwh | no | — | |
| limit | integer | no | Devices to return, 1-25. Defaults to 5. |
Recent news items about Proof of Work mining and network events, optionally filtered to one coin. Items are aggregated from third-party feeds and are returned as quoted external content with their publisher and a relevance score, not as BackPow statements of fact. Use when a question turns on…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin_id | string | no | Optional coin filter, e.g. "Bitcoin", "Zcash", "Kaspa". |
| limit | integer | no | Items to return, 1-20. Defaults to 5. |
| include_low_signal | boolean | no | Include items that relevance triage scored 0. Excluded by default so results stay on topic for Proof of Work mining. |
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 Poworacle 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.0 · scanned 4 Nov 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 digest318e2e1fabe9c7e6dde28f413656b9380eb74a28e330e97dc2c0c7a6a02790dc
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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest318e2e1fabe9c7e6
Scanned2026-11-04
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.0. Pin a release below and the command asks for exactly that one.
0.1.0
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 Poworacle 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.