Robotbase MCP Server

by wygogogo19 Your server? Claim it

answering

Robotbase MCP is answering right now. Last checked 2 min ago. It exposes 15 tools. Last commit 18 Sep 2026.

Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)

Uptime history 5 days of history · worst day 99%

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

905 ms

Response time

average over 24h

Stars

last commit 18 Sep 2026

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

18 Sep a tool changed version

17 Sep 5 tool descriptions were rewritten btc_tx_lookup, chain_status, list_chains and 2 more

17 Sep 5 tools disappeared xmr_fee_estimate, xmr_last_block, xmr_mempool_stats and 2 more

17 Sep 4 tools appeared kas_node_status, kas_pool_status, rvn_node_status and 1 more

17 Sep a tool changed the parameters it asks for chain_status

Robotbase MCP missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add robotbase-mcp --transport http https://robotbase.cc/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "robotbase-mcp": {
      "url": "https://robotbase.cc/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.robotbase-mcp]
url = "https://robotbase.cc/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "robotbase-mcp": {
      "url": "https://robotbase.cc/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "robotbase-mcp": {
      "url": "https://robotbase.cc/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

btc

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.

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

kas

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

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.

zec

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.

chain

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.

chains

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.

robotbase

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.

utxo

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

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

xmr_fee_estimate

removed 17 Sep 2026

xmr_last_block

removed 17 Sep 2026

xmr_mempool_stats

removed 17 Sep 2026

xmr_node_info

removed 17 Sep 2026

xmr_tx_lookup

removed 17 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://robotbase.cc/mcp	streamable-http	answering	834 ms	2 min ago

Alternatives to Robotbase MCP

same job, measured the same way

Polymarket MCP

by 0xchron

Read-only Polymarket prediction market data for AI agents.

174 installs/wk local only

Polymarket Toolkit

by runesleo

Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders.

48 installs/wk local only

1F4BC

by 1f4bcai

Read-only MCP access to the 1F4BC job board for AI agents.

5 tools answering

Wafergraph MCP

by wafergraph

Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.

30 tools answering

Specshield MCP Server

by specshield-io

The API-change deploy gate for AI coding agents. Read-only breaking-change detection.

local only

Base Intel MCP

by datakoot

Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.

5 tools answering

DataCharter

by datacharter

Local-first, contract-governed data explorer with read-only, PII-masked query tools for AI agents.

1 416 installs/wk local only

Base Intel MCP

by datakoot

Read-only on-chain intel for AI agents on Base: balances, tokens, gas, tx status. No API keys.

5 tools answering

Robotbase MCP — questions

Answers built from our own checks of this server.

What can Robotbase MCP do?

It exposes 15 tools, read directly from the server on our last check. Among them: btc_address_summary, btc_block_summary, btc_fee_estimates, btc_mempool_summary, btc_tx_lookup, chain_status and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Robotbase MCP mostly used for?

Its tools cluster around btc, kas and zec. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Robotbase MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 905 ms. The bar chart above shows every period we have measured.

Did Robotbase MCP ever remove tools?

Yes. xmr_fee_estimate, xmr_last_block, xmr_mempool_stats, xmr_node_info and 1 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect Robotbase MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Robotbase MCP need an API key?

No. Robotbase MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Robotbase MCP?

It answers our handshake in 905 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Robotbase MCP open source?

Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.