MCP Radar
MCP Server

robotbase-mcp

io.github.wygogogo19/robotbase-mcp
Crypto & Web3 Data & Analytics Public & reachable MCP 2026-07-28

What this MCP does

Provides read-only blockchain data for Bitcoin, Kaspa, Zcash, Ravencoin, Dogecoin, and Litecoin, including addresses, transactions, blocks, fees, mempools, nodes, and mining pools.

Capabilities

Tools

21 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.
Input schema 
{'type': 'object', 'required': ['chain', 'signed_raw_tx_hex'], 'properties': {'chain': {'enum': ['btc'], 'type': 'string'}, 'signed_raw_tx_hex': {'type': 'string', 'description': 'Raw signed transaction hex'}}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'required': ['address'], 'properties': {'address': {'type': 'string', 'description': 'Bitcoin mainnet address'}}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {'height': {'type': 'integer', 'description': 'Block height (optional)'}, 'blockhash': {'type': 'string', 'description': 'Block hash (optional; use instead of height)'}}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'required': ['txid'], 'properties': {'txid': {'type': 'string', 'pattern': '^[0-9a-fA-F]{64}$', 'description': 'Bitcoin transaction hash (64 hex chars)'}}, 'additionalProperties': False}
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; Monero pool detail → xmr_pool_status.
Input schema 
{'type': 'object', 'required': ['chain'], 'properties': {'chain': {'enum': ['btc', 'eth', 'xmr', 'zec'], 'type': 'string', 'description': 'Chain id: btc / eth / xmr / zec'}}, 'additionalProperties': False}
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).
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'required': ['chain'], 'properties': {'chain': {'enum': ['btc', 'zec', 'ltc', 'doge', 'rvn'], 'type': 'string', 'description': 'btc / zec / ltc / doge / rvn'}}, 'additionalProperties': False}
list_chains
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'required': ['chain'], 'properties': {'chain': {'enum': ['btc', 'ltc', 'doge'], 'type': 'string', 'description': 'btc / ltc / doge'}}, 'additionalProperties': False}
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).
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
pow_network_mining_intel
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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).
Input schema 
{'type': 'object', 'required': ['chain'], 'properties': {'chain': {'enum': ['kas', 'zec', 'rvn'], 'type': 'string'}, 'wallet': {'type': 'string', 'description': 'Miner payout address (optional)'}, 'worker': {'type': 'string', 'description': 'Worker name (optional)'}}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {'blocks': {'type': 'integer', 'default': 200, 'maximum': 500, 'minimum': 10, 'description': 'How many recent blocks to classify (default 200)'}}, 'additionalProperties': False}
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).
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
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.
Input schema 
{'type': 'object', 'properties': {'n': {'type': 'integer', 'default': 5, 'maximum': 20, 'minimum': 1, 'description': 'How many recent blocks to return; default 5'}}, 'additionalProperties': False}
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).
Input schema 
{'type': 'object', 'properties': {}, 'additionalProperties': False}
History

Recent tool changes

Removed
utxo_chain_status
Sept. 29, 2026, 2:58 a.m.
Removed
rvn_pool_status
Sept. 29, 2026, 2:58 a.m.
Removed
rvn_node_status
Sept. 29, 2026, 2:58 a.m.
Removed
rvn_asset_lookup
Sept. 29, 2026, 2:58 a.m.
Removed
kas_pool_status
Sept. 29, 2026, 2:58 a.m.
Removed
kas_pool_attribution_intel
Sept. 29, 2026, 2:58 a.m.
Removed
kas_node_status
Sept. 29, 2026, 2:58 a.m.
Added
eth_node_status
Sept. 29, 2026, 2:58 a.m.
Added
xmr_pool_status
Sept. 29, 2026, 2:58 a.m.
Added
xmr_node_status
Sept. 29, 2026, 2:58 a.m.
Changed
mempool_congestion_status
Sept. 29, 2026, 2:58 a.m.
Changed
pow_network_mining_intel
Sept. 29, 2026, 2:58 a.m.
Changed
chain_status
Sept. 29, 2026, 2:58 a.m.
Changed
list_chains
Sept. 29, 2026, 2:58 a.m.
Added
rvn_asset_lookup
Sept. 25, 2026, 2:58 a.m.
Added
zec_block_attribution_intel
Sept. 25, 2026, 2:58 a.m.
Added
broadcast_raw_transaction
Sept. 25, 2026, 2:58 a.m.
Added
robotbase_pool_worker_query
Sept. 25, 2026, 2:58 a.m.
Added
kas_pool_attribution_intel
Sept. 25, 2026, 2:58 a.m.
Added
zec_shielded_pools_metrics
Sept. 25, 2026, 2:58 a.m.
Added
mempool_congestion_status
Sept. 25, 2026, 2:58 a.m.
Added
get_recommended_fee_rate
Sept. 25, 2026, 2:58 a.m.
Added
pow_network_mining_intel
Sept. 25, 2026, 2:58 a.m.
Added
pow_halving_oracle
Sept. 25, 2026, 2:58 a.m.
Removed
xmr_tx_lookup
Sept. 19, 2026, 2:47 a.m.
Removed
xmr_node_info
Sept. 19, 2026, 2:47 a.m.
Removed
xmr_mempool_stats
Sept. 19, 2026, 2:47 a.m.
Removed
xmr_last_block
Sept. 19, 2026, 2:47 a.m.
Removed
xmr_fee_estimate
Sept. 19, 2026, 2:47 a.m.
Changed
robotbase_services
Sept. 19, 2026, 2:47 a.m.
Discover

Similar MCP servers

Crypto Bot Audit + Market Data (x402 paid)

io.github.kaminariouji/x402-audit-agent

Audits crypto bot source code and provides paid crypto market, token, gas, stablecoin, and DeFi TVL data.

DeltaSignal ATLAS-7

io.github.aitrailblazer/deltasignal-atlas-7

Analyzes SEC and XBRL data for crypto-related public companies, including fundamentals, issuer signals, peer comparisons, stress …

intel

io.chainhelix/intel

Provides multi-chain market intelligence, blockchain activity metrics, trading and portfolio planning, sanctions clearance, agent…

pulsenetwork

com.theaslangroupllc.pulse/pulsenetwork

Provides paid, multi-domain intelligence endpoints covering markets, finance, crypto, compliance, healthcare, climate, education,…

Oblique Markets

markets.oblique.api/oblique-markets

Offers paid research, web extraction, agent-service routing, market analytics, Base blockchain inspection, browser evidence, and …

Market Intelligence API

com.marketintelligenceapi.api/market-intelligence

Analyzes crypto and tokenized-asset markets using DEX flows, perpetual positioning, smart-money activity, token risk, market news…

API Acre

com.apiacre/api-acre

Offers paid APIs for EVM blockchain inspection, data transformation and validation, geocoding, weather, currency conversion, and …

Polyform

org.polyform/polyform

Offers pay-per-call APIs for economic, financial, geographic, healthcare, domain, email, sanctions, blockchain, and business risk…