robotbase-mcp

Every chain this service supports (BTC / ETH / XMR / ZEC) with live availability and block height. When to use: the user asks which chains you support, which nodes are online, or how high each chain is. Do not use: for detail on one chain, use chain_status.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Run-time status of one chain's node: block height, sync progress, connected peers, mempool tx count, client version. When to use: whether a given chain's node is synced, healthy or lagging. Do not use: fees → btc_fee_estimates; address balance → btc_address_summary; Monero pool detail → xmr_pool_status.

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "enum": [
        "btc",
        "eth",
        "xmr",
        "zec"
      ],
      "description": "Chain id: btc / eth / xmr / zec"
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false
}

Zcash mainnet info including the supply of all six value pools (transparent/sprout/sapling/orchard/lockbox/ironwood) — i.e. shielded-pool state. When to use: how much ZEC sits in the shielded/sapling/orchard pools, or privacy-pool size. Do not use: whether the ZEC node is synced → chain_status(zec).

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Height, hash, block time and difficulty of the most recent N Zcash blocks (N ≤ 20). When to use: check whether ZEC is producing blocks normally, and at what interval.

{
  "type": "object",
  "properties": {
    "n": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "default": 5,
      "description": "How many recent blocks to return; default 5"
    }
  },
  "additionalProperties": false
}

Recommended Bitcoin fees: rates (BTC/kvB) for 1/2/3/6/12/24-block confirmation targets, plus the mempool minimum fee. When to use: how much fee to pay, or what gets a fast confirmation. Do not use: overall congestion level → btc_mempool_summary.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Bitcoin mempool overview: pending tx count, bytes used, minimum fee, total fees, capacity limit. When to use: is the network congested right now, or how big the backlog is.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Look up a Bitcoin transaction by txid: confirmed or not, block height, confirmations, size, input/output summary. When to use: the user gives a 64-hex BTC txid and asks whether it confirmed or which block it is in. Do not use: other chains → chain_status.

{
  "type": "object",
  "properties": {
    "txid": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{64}$",
      "description": "Bitcoin transaction hash (64 hex chars)"
    }
  },
  "required": [
    "txid"
  ],
  "additionalProperties": false
}

Bitcoin block summary: tx count, size, weight, block time, confirmations; omit parameters for the current chain tip. When to use: how many transactions the latest block holds, or an overview of a given height or block hash.

{
  "type": "object",
  "properties": {
    "height": {
      "type": "integer",
      "description": "Block height (optional)"
    },
    "blockhash": {
      "type": "string",
      "description": "Block hash (optional; use instead of height)"
    }
  },
  "additionalProperties": false
}

Balance and activity of a Bitcoin address: confirmed/unconfirmed balance, UTXO count and total, tx count, last 10 transactions. Supports P2PKH (1…), P2SH (3…), bech32 (bc1q…), bech32m (bc1p…). When to use: how much BTC this address holds, whether it received funds, how active it is. Note: ultra-active addresses such as exchange cold wallets may return a degraded response under index load.

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Bitcoin mainnet address"
    }
  },
  "required": [
    "address"
  ],
  "additionalProperties": false
}

Halving countdown for every chain we run: height, next halving height, blocks remaining, ETA in days, and the reward before/after. When to use: an agent needs a precise schedule anchor (emissions, mining economics, long-horizon planning). Note: heights are read live from our own nodes, schedules are protocol constants. DOGE has no further halvings (flat subsidy).

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Network hashrate and difficulty for BTC / XMR / ZEC (node-reported or difficulty-derived, stated per chain), plus an explicit proof-of-stake note for ETH. When to use: mining economics, security budget, or comparing chain weight. Do not use: pool-level stats → xmr_pool_status or robotbase_pool_worker_query.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Fee recommendation tiers for a chain: fast / medium / slow plus the mempool minimum. BTC is computed from our own node's fee estimator; ZEC returns the ZIP-317 conventional fee (protocol rule, not a market estimate); chains without an estimator say so instead of guessing. When to use: an autonomous agent is about to send a transaction and must pick a fee.

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "enum": [
        "btc",
        "zec",
        "ltc",
        "doge",
        "rvn"
      ],
      "description": "btc / zec / ltc / doge / rvn"
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false
}

Mempool congestion for BTC (txs, bytes, usage vs capacity, min fee, total fees, busy/normal verdict). When to use: decide whether now is a good moment for an on-chain settlement.

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "enum": [
        "btc",
        "ltc",
        "doge"
      ],
      "description": "btc / ltc / doge"
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false
}

All six Zcash value pools (transparent, sprout, sapling, orchard, ironwood, lockbox) with balances, share of supply and 1h/24h deltas. When to use: privacy-pool capital allocation, shielded-supply trends, ZEC macro flows. Do not use: node health → chain_status(zec).

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Look up one miner on our own hashports: hashrate, shares, stale/invalid, current difficulty and last-seen, by wallet address or worker name. When to use: a miner asks their agent "how is my rig doing on robotbase?". Privacy: the address is masked in the reply, and only an exact wallet/worker match returns data (no listings).

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "enum": [
        "kas",
        "zec",
        "rvn"
      ]
    },
    "wallet": {
      "type": "string",
      "description": "Miner payout address (optional)"
    },
    "worker": {
      "type": "string",
      "description": "Worker name (optional)"
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false
}

Relay an already-signed raw transaction to the network through our own full node (non-custodial: we never see a private key). The transaction is first validated with testmempoolaccept; rejected transactions are never relayed. Disabled by default on this deployment and enabled per-operator with RB_ENABLE_BROADCAST=1. When to use: an agent signed locally and wants a high-availability broadcast path.

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "string",
      "enum": [
        "btc"
      ]
    },
    "signed_raw_tx_hex": {
      "type": "string",
      "description": "Raw signed transaction hex"
    }
  },
  "required": [
    "chain",
    "signed_raw_tx_hex"
  ],
  "additionalProperties": false
}

Zcash coinbase attribution over the last 10-500 blocks: the shielded-pool share of block rewards (privacy mining), coinbase outputs split into consensus funding streams (lockbox) vs real miner payout addresses, and the pool tags miners printed into their own coinbase text plus our own /RobotBase/ tag. When to use: privacy-pool mining trends, shielded adoption, or checking whether our own pool found blocks. Scope: chain facts only — no third-party pool label list is applied.

{
  "type": "object",
  "properties": {
    "blocks": {
      "type": "integer",
      "minimum": 10,
      "maximum": 500,
      "default": 200,
      "description": "How many recent blocks to classify (default 200)"
    }
  },
  "additionalProperties": false
}

Live availability of every service behind the RobotBase gateway: the chain nodes, hashport engines, Web3 Agent Hub, AITOKENS and MCP itself. When to use: an overall health check, or which services are down.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Monero node state: height vs target, sync flag, difficulty, txpool size, database size, monerod version and peer counts. When to use: whether the XMR node is synced and healthy, or how big its chain/txpool is. Do not use: p2pool/mining side → xmr_pool_status.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Our Monero p2pool (mini + nano sidechains) plus Monero network state: per-sidechain hashrate, miners, sidechain height/difficulty, blocks found, last block age, this node's workers, fee and the non-custodial flag. When to use: solo/p2pool mining economics on Monero, sidechain health, or which stratum endpoint to point a rig at. Do not use: plain node RPC state → xmr_node_status.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Ethereum node state from our own Reth (execution) + Lighthouse (consensus): sync state, height/head slot, peers, clients, and — while the node is still being provisioned — an explicit provisioning status. When to use: whether the ETH node is up/synced, or what stage its provisioning/sync is at. Do not use: for PoW hashrate questions — Ethereum is proof-of-stake (see pow_network_mining_intel).

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}