Robotbase is a remote MCP server that gives an AI agent 25 tools, among them broadcast_raw_transaction, btc_address_summary, btc_block_summary. It answers at https://robotbase.cc/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 13 September 2026; the last check, on 22 October 2026, succeeded.
On-chain verification and risk intelligence MCP for Web3 agents. BTC/ETH/XMR/ZEC/TRON nodes live.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 de Inputs: chain, signed_raw_tx_hex |
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, w Inputs: address |
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. Inputs: height, blockhash |
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_sum |
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 Inputs: txid |
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 bala Inputs: chain |
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 estim Inputs: chain |
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 halvin |
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 c Inputs: hours |
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 liv |
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 chai |
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. Inputs: chain |
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). N |
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 → |
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 Inputs: chain, wallet, worker |
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. |
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 ra Inputs: asset, limit |
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 minin |
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). Inputs: chain |
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 prin Inputs: blocks |
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 |
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. Inputs: n |
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 h |
Every block below points at https://robotbase.cc/mcp. Pick your client and copy.
claude mcp add --transport http robotbase https://robotbase.cc/mcp
{
"mcpServers": {
"robotbase": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://robotbase.cc/mcp"]
}
}
}{
"mcpServers": {
"robotbase": {
"url": "https://robotbase.cc/mcp"
}
}
}{
"servers": {
"robotbase": {
"type": "http",
"url": "https://robotbase.cc/mcp"
}
}
}{
"context_servers": {
"robotbase": {
"url": "https://robotbase.cc/mcp"
}
}
}{
"mcpServers": {
"robotbase": {
"serverUrl": "https://robotbase.cc/mcp"
}
}
}{
"mcpServers": {
"robotbase": {
"url": "https://robotbase.cc/mcp"
}
}
}name: Robotbase
version: 0.0.1
schema: v1
mcpServers:
- name: Robotbase
type: streamable-http
url: https://robotbase.cc/mcp{
"mcpServers": {
"robotbase": {
"httpUrl": "https://robotbase.cc/mcp"
}
}
}{
"mcpServers": {
"robotbase": {
"type": "http",
"url": "https://robotbase.cc/mcp"
}
}
}{
"mcpServers": {
"robotbase": {
"url": "https://robotbase.cc/mcp"
}
}
}goose://extension?url=https%3A%2F%2Frobotbase.cc%2Fmcp&type=streamable_http&id=robotbase&name=Robotbase
It answered our last check on 22 October 2026 in 128 ms. Over 5 checks since 13 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
25, as returned by the server's own tools/list on 24 September 2026: broadcast_raw_transaction, btc_address_summary, btc_block_summary, btc_fee_estimates, btc_mempool_summary, btc_tx_lookup, chain_status, get_recommended_fee_rate, and 17 more.
It answered our last check on 22 October 2026 in 128 ms. Over 5 checks since 13 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://robotbase.cc/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.wygogogo19. Endpoint host: robotbase.cc. ARD identifier: urn:air:io.github.wygogogo19:mcp:robotbase-mcp.
First indexed 13 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.