robotbase-mcp
Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)
Server tool list (15)
Raw names from tools/list. Only developers need these.
| list_chains | Every chain this service supports (BTC/KAS/ZEC/RVN/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. |
| 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; address balance → btc_address_summary; pool detail → kas_pool_status / rvn_pool_status. |
| 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). |
| 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. |
| 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. |
| 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. |
| 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: other chains → chain_status. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 BTC/KAS/ZEC/RVN use chain_status (any chain in one call). |
| robotbase_services | 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. |