Mcp

Hive Mos

Tether MiningOS bridge — site telemetry, paying demand, BTC to USDC settlement

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Hive Mos

Choose if

You're operating Bitcoin mining infrastructure (or an agent that does) and need site telemetry, hashrate / energy data, mining pool status, or energy-arbitrage signals callable from an MCP host. Settles in USDC/USDT on Base, Ethereum, or Solana via the shared Hive Civilization gateway with x402 micropayments. Pair with sibling Hive MCPs for full agent-native financial infrastructure.

Avoid if

README explicitly tags this as "scaffold shim — backend pending Q3 2026." The README does not enumerate specific tools beyond the shared Hive earn-rails — the MOS-specific endpoints are not yet substantively callable. Also avoid for general crypto data lookup (use Coingecko, Glassnode, or a dedicated price MCP) or for any non-Tether-MOS mining platform.

Risk Flags

  • HIGH runtime README explicitly states "Scaffold shim — backend pending Q3 2026." Treat as a discovery anchor, not a live mining-data substrate.
  • MEDIUM scope Scope is narrowly tied to Tether's Mining OS (MOS) plugin ecosystem. Mining operators using other platforms (Foreman, LuxOS, Braiins, etc.) get no coverage.
  • LOW data_quality No tool inventory or pricing in the README — only gateway URL and discovery surface documented. Verify tools/list and pricing live before designing flows.

Cost

Type: Usage based

Distribution

MCP Registry
io.github.srotzin/hive-mcp-mos
Repository
https://github.com/srotzin/hive-mcp-mos