Alpaca Trading API integration for Model Context Protocol (MCP)
MinerYield 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.
What it does
ASIC solar/battery profit. Keyless MCP 20/min+200/day; paid 25/1k/10k/50k. Not financial advice.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'MINERYIELD_API_KEY=${MINERYIELD_API_KEY}' --transport stdio mineryield-mcp '--' npx -y mineryield-mcp
# 2 — ask your agent for something these tools do
# list_miners, get_rigs, calculate_profitability and 7 more
It needs MINERYIELD_API_KEY: this reads it from your environment, so export it first.
MinerYield costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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. Claude Code reads MINERYIELD_API_KEY (Bearer API key created at https://mineryield.com/api while signed in) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx MINERYIELD_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'MINERYIELD_API_KEY=${MINERYIELD_API_KEY}' --transport stdio mineryield-mcp '--' npx -y mineryield-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://mineryield.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http mineryield-mcp https://mineryield.com/mcpIt reaches a system of yours, so it needs your own credential rather than the publisher’s: MINERYIELD_API_KEY — Bearer API key created at https://mineryield.com/api while signed in.. You set it in your own client’s config, on your machine — this marketplace never holds it.
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.
10 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.
GET /api/v1/miners — rank catalog ASICs by daily profit for a home or small-business solar+battery+grid setup (same model as the site calculator). Optional solarW (10000=10 kW), batteryCapacity (kWh), zipCode, elecCost, and powerSources override the API-key owner profile. Example: 10 kW array + 20…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| solarW | number | no | — |
| batteryCapacity | number | no | — |
| zipCode | string | no | — |
| elecCost | number | no | Grid electricity price in USD per kWh (0.15 = 15 cents). Applied only to leftover watts after solar and battery. There is no separate day/night rate: solar covers the sun window, grid covers the rest |
| powerSources | object | no | — |
GET /api/v1/rigs — the signed-in API-key owner's saved My Rigs list with per-unit yield estimates, including NiceHash daily revenue (USD/day) when a market rate exists (null otherwise). Figures are MinerYield model estimates from live market inputs: estimates only, not investment, financial, or…
No parameter schema on file.
POST /api/v1/calculator — one-machine home/small-business profitability with the same solar/battery/grid leftover-watt model as the site. Required: hashrate, power, algorithm, elecCost. Optional: solarW, batteryCapacity, zipCode, powerSources. Example: 3 kW miner on solar by day, grid at $0.15/kWh…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hashrate | number | yes | Hashing power (TH/s for SHA-256, MH/s for Scrypt; same units as the catalog). |
| power | number | yes | Miner wall power in Watts (3000 = 3 kW). Used with solar/battery/grid to compute leftover watts and runtime. |
| algorithm | string | yes | — |
| elecCost | number | yes | — |
| solarW | number | no | — |
| zipCode | string | no | — |
| hardwareCost | number | no | Upfront hardware cost in USD used for estimated payback days. |
| batteryCapacity | number | no | — |
| powerSources | object | no | — |
| preferredCoin | string | no | — |
GET /api/v1/market — live spot prices for BTC, BCH, LTC, DOGE, ZEC, KAS, CKB, RXD, SC, DCR, DASH, GRIN, ALPH, XTM, ETC, XMR, ALEO, HNS, BTCB2, KDA, NEXA, XP, QUAI, ARRR, OCTA, ETHW, QKC, MWC, SCP. Prices can move; not a trading feed.
No parameter schema on file.
GET /api/v1/solar-forecast — 7-day estimated kWh from a home/small-business solar array (US ZIP + capacityW, 10000=10 kW). Weather-based production only; pair with calculate_profitability or list_miners for miner profit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zipCode | string | no | 5-digit US ZIP code. Falls back to the API-key owner profile, then a server default. |
| capacityW | number | no | Solar array capacity in Watts (10000 = 10 kW). Falls back to the API-key owner profile solarW. |
GET /api/v1/difficulty-prediction — 7-day network difficulty trend for a coin (default BTC). Model estimate, not a guarantee.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| coin | string | no | Cryptocurrency ticker. Allowed values match GET /api/v1/difficulty-prediction: BTC, BCH, LTC, DOGE, ZEC, KAS, CKB, RXD, SC, DCR, DASH, GRIN, ALPH, XTM, ETC, XMR, ALEO, HNS, BTCB2, KDA, NEXA, XP, QUAI, |
GET /api/v1/catalog/miners — public ASIC catalog (specs only, no user profitability). Includes Kadena/KDA, NexaPow/NEXA, XPHash/XP, zkSNARK/ALEO, Blake3/ALPH, and SHA-256 QUAI-capable SKUs under 5000 W. Goldshell HS-Lite is one row (hs-lite) with dual modes (Blake2B-SHA3/HNS and Blake2B…
No parameter schema on file.
GET /api/v1/mrr-rates — public cached Mining Rig Rentals algorithm rates. SHA3X, zkSNARK, Blake256R14, Kadena, and XPHash have no primary MRR book (null). NexaPow maps to the MRR nexapow book. No API key required. Market snapshot, not a rental booking.
No parameter schema on file.
GET /api/v1/nicehash-rates — public cached NiceHash algorithm paying rates (sat per H/s or Sol/s per day). SHA3X, zkSNARK, Blake256R14, Kadena, and XPHash have no NiceHash paying book (null). No API key required. Market snapshot used for My Rigs NiceHash revenue ($/day), not a rental booking.
No parameter schema on file.
GET /api/v1/market-data — public full market payload (prices plus network hashrate/difficulty used by the web app), including KDA, NEXA, XP, QUAI, ARRR, OCTA, ETHW, QKC, MWC, and SCP. New-coin and XP hashRate/blockReward may be null/omitted. No API key required. Broader than get_market.
No parameter schema on file.
- 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 MinerYield or to call it, at any volume.
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.
| 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 |
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.
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. | ||
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
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 1.0.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish MinerYield can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.