Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MinerYield

REMOTE · MINERYIELD.COM · 2 COMPONENTS

ASIC solar/battery profit. Keyless MCP 20/min+200/day; paid 25/1k/10k/50k. Not financial advice.

0 this week 23 Trust /100

Last scanned (15 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 12 Nov 26 −51
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 74

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mineryield.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mineryield.com CN=WR3,O=Google Trust Services,C=US 13 Nov 2026 11 Feb 2027 RSA 2048 SHA256-RSA d1a908ea66ddf2b60ae342015d70c808
SANs: mineryield.com, www.mineryield.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mineryield.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
mineryield.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 429

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mineryield.com/mcp Auth required 401
http (plaintext) http://mineryield.com/mcp HTTPS enforced 301 https://mineryield.com/mcp
MCP tools · 10 exposed · ~2,186 tokens

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 →

Tool Tokens
calculate_profitability ~800

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 at night → power=3000, elecCost=0.15, solarW=<array watts>, powerSources={solar:true, battery:false, grid:true} (add batteryCapacity and battery:true to store leftover sun). Returns dailyProfit, dailyCost, solarSavings, runtimeHours, effectiveElecCost. Figures are MinerYield model estimates from live market inputs: estimates only, not investment, financial, or tax advice, and not ROI guarantees. Results vary with network difficulty, coin price, power cost, and hardware performance. Do your own research.

NameTypeReqDescription
algorithmstringyesCatalog algorithm name as stored on MinerYield (SHA-256, Scrypt, KHeavyHash, Eaglesong, SHA512256d, Blake2B, Blake2B-Sia, Blake2B-SHA3, Blake256R14, X11, Cuckatoo31, Cuckatoo32, Equihash, RandomX, SH…
batteryCapacitynumber–Battery storage in kWh (20 = 20 kWh). Only used when powerSources.battery is true (passing batteryCapacity without powerSources turns battery on). Excess daytime solar charges the battery; the batter…
elecCostnumberyesGrid 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…
hardwareCostnumber–Upfront hardware cost in USD used for estimated payback days.
hashratenumberyesHashing power (TH/s for SHA-256, MH/s for Scrypt; same units as the catalog).
powernumberyesMiner wall power in Watts (3000 = 3 kW). Used with solar/battery/grid to compute leftover watts and runtime.
powerSourcesobject–Which legs of the site calculator to use. solar=true uses solarW during Peak Sun Hours; battery=true uses leftover solar stored in batteryCapacity at night; grid=true keeps the miner running 24h on l…
preferredCoinstring–Target coin when an algorithm supports more than one (BTC/BCH/QUAI, SC/BTCB2, BTCB2/SC, ZEC/ARRR, ETC/OCTA/ETHW/QKC, DCR/SCP). Blake2B-SHA3 is HNS only; Cuckatoo31 is MWC only; Cuckatoo32 is GRIN onl…
solarWnumber–Home/small-business solar array capacity in Watts (10000 = 10 kW). Used with Peak Sun Hours from zipCode. Solar generation is treated as free during the sun window; leftover watts can charge the batt…
zipCodestring–5-digit US ZIP for Peak Sun Hours. Defaults to the API-key owner profile, then 06716. Needed for a realistic solar-by-day estimate.

No output schema declared.

No examples provided.

get_difficulty_prediction ~149

GET /api/v1/difficulty-prediction — 7-day network difficulty trend for a coin (default BTC). Model estimate, not a guarantee.

NameTypeReqDescription
coinstring–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…

No output schema declared.

No examples provided.

get_market ~110

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_market_data ~95

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rigs ~102

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 tax advice, and not ROI guarantees. Results vary with network difficulty, coin price, power cost, and hardware performance. Do your own research.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_solar_forecast ~128

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.

NameTypeReqDescription
capacityWnumber–Solar array capacity in Watts (10000 = 10 kW). Falls back to the API-key owner profile solarW.
zipCodestring–5-digit US ZIP code. Falls back to the API-key owner profile, then 06716.

No output schema declared.

No examples provided.

list_catalog_miners ~118

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 SC/BTCB2). No API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_miners ~510

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 kWh battery → solarW=10000, batteryCapacity=20, powerSources={solar:true, battery:true, grid:true}; sort PROFIT/DAY. Includes Kadena/KDA, NexaPow/NEXA, XPHash/XP, SHA-256 QUAI, and NiceHash daily revenue when a rate exists. Figures are MinerYield model estimates from live market inputs: estimates only, not investment, financial, or tax advice, and not ROI guarantees. Results vary with network difficulty, coin price, power cost, and hardware performance. Do your own research.

NameTypeReqDescription
batteryCapacitynumber–Battery storage in kWh (20 = 20 kWh). Only used when powerSources.battery is true (passing batteryCapacity without powerSources turns battery on). Excess daytime solar charges the battery; the batter…
elecCostnumber–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…
powerSourcesobject–Which legs of the site calculator to use. solar=true uses solarW during Peak Sun Hours; battery=true uses leftover solar stored in batteryCapacity at night; grid=true keeps the miner running 24h on l…
solarWnumber–Home/small-business solar array capacity in Watts (10000 = 10 kW). Used with Peak Sun Hours from zipCode. Solar generation is treated as free during the sun window; leftover watts can charge the batt…
zipCodestring–5-digit US ZIP for Peak Sun Hours. Defaults to the API-key owner profile, then 06716. Needed for a realistic solar-by-day estimate.

No output schema declared.

No examples provided.

list_mrr_rates ~82

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_nicehash_rates ~92

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the MinerYield MCP server?

MinerYield is a hosted endpoint at https://mineryield.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mineryield.com

# add to Claude Code
claude mcp add --transport http nadeaup-mineryield-mcp 'https://mineryield.com/mcp'
Common questions

What is the MinerYield MCP server?

MinerYield is an MCP server listed in the public MCP registry as io.github.nadeaup/mineryield-mcp. ASIC solar/battery profit. Keyless MCP 20/min+200/day; paid 25/1k/10k/50k. Not financial advice. This page covers its hosted endpoint (https://mineryield.com/mcp).

Is the MinerYield MCP server safe to use?

MinerYield scores 23 out of 100 on VerifyMCP. 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 MinerYield MCP server expose?

MinerYield exposes 10 tools: list_miners, get_rigs, calculate_profitability, get_market, get_solar_forecast, and 5 more. Their descriptions and schemas cost roughly 2,186 tokens of context every time the server is loaded.

Does the MinerYield MCP server require authentication?

Its publisher declares no required credentials for MinerYield. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the MinerYield MCP server still maintained?

MinerYield is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MinerYield MCP server?

VerifyMCP ran 4 checks on MinerYield, covering TLS certificate, HTTPS, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about MinerYield: Authorization, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.