io.github.wygogogo19/robotbase-mcp

Tools

• broadcast_raw_transaction

  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.

  shallow
• btc_address_summary

  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.

  shallow
• btc_block_summary

  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.

  shallow
• btc_fee_estimates

  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.

  shallow
• btc_mempool_summary

  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.

  shallow
• btc_tx_lookup

  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: Monero transactions → xmr_tx_lookup.

  shallow
• chain_status

  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 or xmr_fee_estimate; address balance → btc_address_summary.

  shallow
• eth_node_status

  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).

  shallow
• get_recommended_fee_rate

  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.

  shallow
• kas_node_status

  Kaspa node status: network height, DAA score, difficulty, network hashrate, DAG tips, block reward, 10 BPS cadence, next halving and the hashport ports this node serves. When to use: how high and how healthy the Kaspa node is, or the halving schedule. Do not use: our own pool's miners/blocks → kas_pool_status.

  shallow
• kas_pool_attribution_intel

  Kaspa chain-wide pool attribution computed locally: which pool found how many blocks, with percentage share, over a window of 1-720 hours, plus the newest attributed blocks. When to use: Kaspa mining decentralisation, competitor share, or checking how a pool performs. Powered by our own block index (hundreds of thousands of blocks attributed), not a third-party API.

  shallow
• kas_pool_status

  RobotBase Kaspa solo hashport: tier state, pool hashrate, connected miners, accepted shares, blocks found, uptime, share difficulty, the last block found (hash, blue score, age) and stale/invalid counts. When to use: is the KAS hashport live, who is mining on it, did it ever find a real mainnet block. Do not use: chain-level hashrate → kas_node_status.

  shallow
• list_chains

  Every chain this service supports (BTC/XMR/ZEC/DOGE/LTC) 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.

  shallow
• mempool_congestion_status

  Mempool congestion for BTC (txs, bytes, usage vs capacity, min fee, total fees, busy/normal verdict) and tx counts for LTC/DOGE where our node API exposes them. When to use: decide whether now is a good moment for an on-chain settlement.

  shallow
• pow_halving_oracle

  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).

  shallow
• pow_network_mining_intel

  Network hashrate and difficulty for BTC/KAS/ZEC/RVN/LTC/DOGE, with the method stated per chain (node-reported vs difficulty-derived). When to use: mining economics, security budget, or comparing chain weight. Do not use: pool-level stats → kas_pool_status / rvn_pool_status.

  shallow
• robotbase_pool_worker_query

  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).

  shallow
• robotbase_services

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

  shallow
• rvn_asset_lookup

  Ravencoin native assets straight from our ravend: pass an asset name or id for amount, units, reissuable flag and IPFS metadata, or omit it to list recent assets. When to use: token/asset checks on Ravencoin, where assets are UTXO-native rather than smart contracts.

  shallow
• rvn_node_status

  Ravencoin node status: height, sync state, network hashrate, difficulty and client version. When to use: whether the RVN node is synced and how big the network is right now.

  shallow
• rvn_pool_status

  RobotBase Ravencoin solo hashport: engine state, pool hashrate, connected miners, shares, share difficulty, the Stratum endpoint, fee and the per-miner independent coinbase payout mode. When to use: is the RVN hashport open, is anyone mining, what endpoint do I point a GPU rig at. Do not use: node-level data → rvn_node_status.

  shallow
• utxo_chain_status

  Node status for DOGE or LTC (height, sync progress, peers, mempool tx count). When to use: Dogecoin or Litecoin node progress. For ZEC/BTC/XMR use chain_status (any chain in one call).

  shallow
• xmr_fee_estimate

  Monero fee estimate: per-byte rate, tiered rates (low/medium/high) and the quantization mask. When to use: how much fee an XMR transfer costs, or the current rate.

  shallow
• xmr_last_block

  Latest Monero block header: height, hash, timestamp, difficulty, block reward, transaction count. When to use: XMR's most recent block time, latest height, or whether the chain stalled.

  shallow
• xmr_mempool_stats

  Monero mempool statistics: total bytes, total fees, and a transaction histogram grouped by size (congestion level). When to use: is XMR congested right now, or how many transactions are waiting.

  shallow
• xmr_node_info

  Monero full-node info: height, sync state, difficulty, in/out connections, database size, mempool tx count, version. When to use: how high the XMR node is, whether it finished syncing, whether it is connected to the network.

  shallow
• xmr_node_status

  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.

  shallow
• xmr_pool_status

  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.

  shallow
• xmr_tx_lookup

  Look up a Monero transaction by txid: still in the mempool or already mined, block height and confirmations, input/output counts, output indices. When to use: judge whether an XMR transaction or atomic swap is mined, or stuck unconfirmed past its timeout. Do not use: Bitcoin transactions → btc_tx_lookup.

  shallow
• zec_block_attribution_intel

  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.

  shallow
• zec_chain_info

  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).

  shallow
• zec_recent_blocks

  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.

  shallow
• zec_shielded_pools_metrics

  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).

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/50ec31d0-2470-4e8d-a992-f50f471f0f54/badge.svg)](https://vouch.tools/servers/50ec31d0-2470-4e8d-a992-f50f471f0f54)