Read-only MCP for BTC, ETH, XMR and ZEC: fees, nodes, p2pool, shielded pools.
Listed on
- Official MCP Registry
- Glamavia MCP Toplist
First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
2
Directories
1 via MCP Toplist
19
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
| list_chains | Every chain on the RobotBase roster (BTC / ETH / XMR / ZEC live today, Base / Solana / Tron being provisioned, TON planned) with its tier, 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; for what a node can answer at all, use robotbase_capabilities. | Not declared |
| mempool_congestion_status | 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. | Not declared |
| 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. | Not declared |
| pow_network_mining_intel | Network hashrate and difficulty for the proof-of-work chains we run: BTC / XMR / ZEC (node-reported or difficulty-derived, stated per chain; Ethereum is proof-of-stake and has no mining hashrate). When to use: mining economics, security budget, or comparing chain weight. Do not use: pool-level stats — RobotBase operates no mining pool. | Not declared |
| robotbase_capabilities | What every RobotBase node can and cannot answer, including pruning and retention limits per chain. When to use: before promising a user that some query is possible — check here first, because pruned and window-limited nodes state their boundary and refuse out-of-range queries instead of approximating. Note: RobotBase publishes no RPC endpoint; every read path is this MCP surface. | Not declared |
| robotbase_services | Live availability of every service behind the RobotBase gateway: the chain nodes, Web3 Agent Hub, AITOKENS and MCP itself. When to use: an overall health check, or which services are down. | Not declared |
| 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: pool-level stats — RobotBase operates no mining pool. | Not declared |
| 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 whether the /RobotBase/ tag appears in a coinbase. Scope: chain facts only — no third-party pool label list is applied. | Not declared |
| 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). | Not declared |
| 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. | Not declared |
| 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). | Not declared |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | io.github.wygogogo19/robotbase-mcp | - | 2 Oct 2026 |
| Glama | Listed there according to MCP Toplist’s dataset; not collected by InvokeRank. | ||