Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is mineryield free to use?

Partly — some of its tools are open, others need a key or payment.

What tools does mineryield have?

10 tools: calculate_profitability, list_catalog_miners, list_miners, get_rigs, get_solar_forecast, list_mrr_rates, list_nicehash_rates, get_market_data, ….

Is mineryield safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 1h ago

mineryield

https://mineryield.com

Registry code: 4b6f8d769de064ff

api record

MinerYield tools for home miners and small businesses: ASIC profitability with solar, battery, and grid leftover-watt accounting. Estimates only; not investment, financial, or tax advice. Results vary with network difficulty, coin price, power cost, and hardware performance. Do your own research.

endpoint: https://mineryield.com/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is mineryield live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mineryield free to use?: Partly — some of its tools are open, others need a key or payment.
What tools does mineryield have?: 10 tools: calculate_profitability, list_catalog_miners, list_miners, get_rigs, get_solar_forecast, list_mrr_rates, list_nicehash_rates, get_market_data, ….
Is mineryield safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

427ms

last good check

priced tools

of 10 tools

_ answered our checks, 90 days 1 checks · signed record

2026-11-12 00:40 unknown → live

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 10 tools

1 open2 auth-required 7 never probed 3 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_market_data open 1h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

get_difficulty_prediction auth-required 1h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "coin": {
      "type": "string",
      "description": "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, ARRR, OCTA, ETHW, QKC, MWC, SCP. Defaults to BTC."
    }
  }
}

arguments 10 lines

get_market auth-required 1h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

calculate_profitability unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hashrate",
    "power",
    "algorithm",
    "elecCost"
  ],
  "properties": {
    "power": {
      "type": "number",
      "description": "Miner wall power in Watts (3000 = 3 kW). Used with solar/battery/grid to compute leftover watts and runtime."
    },
    "solarW": {
      "type": "number",
      "description": "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 battery."
    },
    "zipCode": {
      "type": "string",
      "description": "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."
    },
    "elecCost": {
      "type": "number",
      "description": "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 at this price."
    },
    "hashrate": {
      "type": "number",
      "description": "Hashing power (TH/s for SHA-256, MH/s for Scrypt; same units as the catalog)."
    },
    "algorithm": {
      "type": "string",
      "description": "Catalog algorithm name as stored on MinerYield (SHA-256, Scrypt, KHeavyHash, Eaglesong, SHA512256d, Blake2B, Blake2B-Sia, Blake2B-SHA3, Blake256R14, X11, Cuckatoo31, Cuckatoo32, Equihash, RandomX, SHA3X, Ethash4G, Blake3, zkSNARK, Kadena, NexaPow, XPHash)."
    },
    "hardwareCost": {
      "type": "number",
      "description": "Upfront hardware cost in USD used for estimated payback days."
    },
    "powerSources": {
      "type": "object",
      "required": [
        "solar",
        "battery",
        "grid"
      ],
      "properties": {
        "grid": {
          "type": "boolean",
          "description": "Draw leftover kWh from the grid at elecCost so the miner can run 24 hours. Off = solar/battery-only runtime."
        },
        "solar": {
          "type": "boolean",
          "description": "Use the solar array (solarW) during Peak Sun Hours. Turn on for any home-solar scenario."
        },
        "battery": {
          "type": "boolean",
          "description": "Use leftover daytime solar stored in batteryCapacity to cover night hours."
        }
      },
      "description": "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 leftover grid kWh. solar=true + grid=true + battery=false is \"solar by day, grid at night\". If grid=false the miner only runs while solar or battery energy lasts (runtimeHours < 24)."
    },
    "preferredCoin": {
      "type": "string",
      "description": "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 only. Scrypt reports LTC/DOGE (merged). When omitted, the most profitable supported coin is used except Ethash4G, which defaults to ETC."
    },
    "batteryCapacity": {
      "type": "number",
      "description": "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 battery covers night hours before grid."
    }
  }
}

arguments 71 lines

list_catalog_miners unknown never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

list_miners unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "solarW": {
      "type": "number",
      "description": "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 battery."
    },
    "zipCode": {
      "type": "string",
      "description": "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."
    },
    "elecCost": {
      "type": "number",
      "description": "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 at this price. On list_miners this overrides the API-key owner profile."
    },
    "powerSources": {
      "type": "object",
      "required": [
        "solar",
        "battery",
        "grid"
      ],
      "properties": {
        "grid": {
          "type": "boolean",
          "description": "Draw leftover kWh from the grid at elecCost so the miner can run 24 hours. Off = solar/battery-only runtime."
        },
        "solar": {
          "type": "boolean",
          "description": "Use the solar array (solarW) during Peak Sun Hours. Turn on for any home-solar scenario."
        },
        "battery": {
          "type": "boolean",
          "description": "Use leftover daytime solar stored in batteryCapacity to cover night hours."
        }
      },
      "description": "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 leftover grid kWh. solar=true + grid=true + battery=false is \"solar by day, grid at night\". If grid=false the miner only runs while solar or battery energy lasts (runtimeHours < 24)."
    },
    "batteryCapacity": {
      "type": "number",
      "description": "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 battery covers night hours before grid."
    }
  }
}

arguments 45 lines

get_rigs unknown never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

get_solar_forecast unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "zipCode": {
      "type": "string",
      "description": "5-digit US ZIP code. Falls back to the API-key owner profile, then 06716."
    },
    "capacityW": {
      "type": "number",
      "description": "Solar array capacity in Watts (10000 = 10 kW). Falls back to the API-key owner profile solarW."
    }
  }
}

arguments 14 lines

list_mrr_rates unknown never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
list_nicehash_rates unknown never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4b6f8d769de064ff.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4b6f8d769de064ff/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/4b6f8d769de064ff/badge.svg)](https://brick.blue/agent/4b6f8d769de064ff?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.