MCP server

Robotbase

io.github.wygogogo19/robotbase-mcp

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.

Working at last checkAbout 16,981 tokens per request once connected65 tools

Website Source

https://robotbase.cc/mcp

At a glance

Type: MCP server
Publisher: Not verified
Status: Working at last check
Tools: 65
Token cost: About 16,981 tokens per request
Sets up in: Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok
Last checked: 26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to Cursor Add to VS Code VS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

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

Gemini CLI

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

Cursor

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

VS Code

{"servers":{"robotbase-mcp":{"type":"http","url":"https://robotbase.cc/mcp"}}}

Antigravity

agy mcp add robotbase-mcp https://robotbase.cc/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"robotbase-mcp","server_url":"https://robotbase.cc/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"robotbase-mcp","server_url":"https://robotbase.cc/mcp"}

Tools

broadcast_raw_transaction Sends messages · ~255 tokens
Relay an already-signed raw transaction to the network through our own full node (non-custodial: we never see a private key). When to use: an agent signed a transaction locally and wants a high-availability broadcast path into the Bitcoin network. Do not use: to build or sign a transaction (we never
btc_get_address ~216 tokens
Balance and activity of a Bitcoin address, with no key involved. When to use: reconciling a merchant wallet, or checking whether an address received funds and how active it is. Do not use: we do not label or risk-score addresses; for a single payment use btc_get_transaction. Returns: address, confir
btc_get_block ~166 tokens
Bitcoin block summary by height or hash; omit both for the chain tip. When to use: an overview of a block, or confirming which block a payment landed in. Do not use: to fetch a single payment (that is btc_get_transaction). Returns: hash, height, time, txs, size, weight, confirmations, previousblockh
btc_get_fee_rates ~173 tokens
Bitcoin fee rates for confirmation targets, plus the mempool floor. When to use: pricing a Bitcoin transaction, or deciding when a sweep will confirm cheaply. Do not use: to measure backlog depth (that is btc_get_mempool_state). There is no equivalent for Zcash: ZEC fees are protocol-fixed, see robo
btc_get_mempool_state ~128 tokens
Bitcoin mempool depth, capacity load and a busy/normal verdict. When to use: deciding whether now is a good moment to settle on-chain, or how large the backlog is. Do not use: to choose a fee (that is btc_get_fee_rates). Returns: txs, bytes, usage_mb, max_mempool_mb, load_pct, min_fee_btc_kvb, total
btc_get_network_stats ~211 tokens
Bitcoin network and node state: difficulty, network hashrate, total transactions processed and the current tx/s rate, protocol version, peer connections, relay fee, mempool size, uptime and which indexes (txindex) are synced on our node. When to use: macro questions about Bitcoin - how much hashrate
btc_get_transaction ~187 tokens
Look up one Bitcoin transaction by txid - the core settlement check. When to use: has this payment arrived, which block is it in, how many confirmations does it have. Do not use: for a whole block (that is btc_get_block); for an address balance (that is btc_get_address). Returns: txid, blockhash, co
chain_status ~208 tokens
Live run-time state of one chain's node. When to use: is this chain's node synced, healthy or lagging; what is its height, peer count, mempool depth or client version. Do not use: fees (that is btc_get_fee_rates); a specific payment (that is btc_get_transaction); ZEC pool distribution (that is zec_g
crypto_trending ~186 tokens
Crypto attention and market context: CoinGecko trending coins, top markets, DeFi TVL and Fear & Greed. When to use: what is trending in crypto, which tokens are moving, risk appetite, TVL leaders. Do not use: for on-chain settlement verification (use btc/eth/xmr/zec/tron tools) or price charts. Retu
eth_get_account ~164 tokens
Ethereum account state from our own node: ETH balance, nonce, and whether the address is a contract. When to use: balance and account type before sizing a transfer, or telling an EOA from a contract. Do not use: for ERC-20 token balances (eth_read_contract with balanceOf) or address risk scoring. Re
eth_get_block ~282 tokens
One Ethereum block by number, tag (latest/finalized/safe) or hash: timestamp, transaction count, gas used against the limit, base fee, block builder and size. When to use: block-level context - how full is Ethereum right now, when a block was produced, what the base fee was, or which builder produce
eth_get_fee_rates ~198 tokens
Ethereum fee market from our own Reth node: current and next base fee, priority-fee percentiles over the last blocks, and the estimated ETH cost of a plain transfer and of an ERC-20 transfer. When to use: pricing an Ethereum transaction, or deciding what tip gets included quickly. Do not use: for Bi
eth_get_logs ~375 tokens
Ethereum event logs over a block range, optionally filtered by contract address and event signature, with ERC-20 Transfer logs decoded (token, from, to, amount). When to use: find transfers or contract events in a window - 'who moved this token in the last N blocks', or watch a contract's activity w
eth_get_transaction ~295 tokens
Ethereum transaction check by hash: success or reverted, gas used, fee paid, confirmations, whether the block is finalized, and any ERC-20 transfers decoded from the receipt logs (token, from, to, amount). When to use: did this ETH or ERC-20 payment actually settle, is it irreversible, who paid whom
eth_read_contract ~418 tokens
Read-only (eth_call) against any Ethereum contract, executed by our own Reth node. ERC-20 helpers balanceOf / allowance / decimals / symbol / name / totalSupply are built in; any other function can be called by passing its 4-byte `selector` plus ABI-encoded `parameter`. Nothing is signed or written.
list_chains ~141 tokens
List every chain on the RobotBase roster with its state. When to use: the user asks which chains are supported, which nodes are online, or where to start. Do not use: for one chain's live health call chain_status; for what a node can and cannot answer call robotbase_capabilities. Returns: chains[],
prediction_market_odds ~209 tokens
Live implied probabilities from prediction markets (Polymarket primary, Manifold fallback). When to use: 'what does the market think will happen', event odds, election/crypto/macro probabilities. Do not use: for spot prices (crypto_trending) or historical search interest (attention_trend). Returns:
robotbase_capabilities ~159 tokens
Per-chain capability, retention boundary and fee model. When to use: before promising that some query is possible, or when a tool refused a query as out of range. Do not use: for live numbers (that is chain_status). Returns: one row per chain {chain, tier, name, client, state, capability}, plus the
robotbase_services ~144 tokens
Live availability of every service behind the RobotBase gateway: the chain nodes, Web3 Agent Hub, AITOKENS and MCP itself. When to use: an overall platform health check, or finding which service is down. Do not use: for a single chain's node state (chain_status) or its capability boundary (robotbase
tron_check_address_risk ~310 tokens
TRON address risk intelligence: judicial and black-market labels, account profile and a 0-100 safety score. When to use: before accepting USDT from a counterparty - OTC settlement, merchant payout, or any agent that must not receive tainted funds; also to sanity-check an address you are about to pay
tron_get_account ~224 tokens
TRON account state read straight off our own node: TRX balance, whether the account is activated, energy and bandwidth (used / limit), whether it is a witness, and account age. When to use: TRX balance and resource state before sizing a transfer, or checking whether an address exists on chain. Do no
tron_get_block ~259 tokens
One Tron block by height or block id, read from our own node: producer, timestamp, transaction count split by contract type, and the tx ids in it. When to use: inspect a specific block, or confirm which block a transaction landed in. Do not use: for the tip only (tron_get_current_block) or for a tra
tron_get_chain_economics ~222 tokens
TRON chain economics straight off our node: energy price (sun per energy unit), transaction fee, account creation fee, witness pay per block, total energy and bandwidth limits, maintenance interval and the next maintenance time, unfreeze delay. When to use: working out what a transaction will actual
tron_get_contract ~178 tokens
TRON contract metadata: name, creator, whether its ABI is published on chain, the function list, code hash and whether it looks like a TRC-20. When to use: before calling a contract, or to tell an unverified contract from a published one. Do not use: for risk/backdoor analysis (that is tron_check_ad
tron_get_current_block ~163 tokens
The current (tip) TRON block: number, id, parent, timestamp, transaction count and a breakdown by contract type, plus the producing witness. When to use: how busy TRON is right now, what is in the block being produced, who produced it. Do not use: to fetch an older block - a lite full node serves th
tron_get_node_status ~175 tokens
TRON node state from our own java-tron full node: tip height, finalized (solidity) height and how far solidity lags, peers, client version, transactions in the tip block. When to use: is the TRON node we operate synced and healthy, and how far behind is the finalized state. Do not use: for historica
tron_get_transaction ~280 tokens
One Tron transaction by txid: success or reverted, energy used, the call it made, and - this is the important part - any TRC-20 transfers decoded from the receipt logs (token, from, to, amount). When to use: did this USDT payment really land, for how much, from whom, and is it finalized. Do not use:
tron_list_proposals ~194 tokens
Tron governance proposals: id, proposer, state, approvals, expiry and the parameters they would change. When to use: governance or staking questions, or checking whether a chain-parameter change is pending. Do not use: for the current parameter values (tron_get_chain_economics) or the witness list (
tron_list_witnesses ~202 tokens
TRON super representatives and candidates: who is producing blocks, how many they produced, how many they missed, votes and websites - read from our own node. When to use: governance or staking questions about TRON, or checking the health of block production. Do not use: for account balances (tron_g
tron_read_contract ~401 tokens
Read-only (constant) call against any TRON contract, executed by our own node. TRC-20 helpers balanceOf / allowance / decimals / symbol / name / totalSupply are built in; any other function can be called with a raw selector plus ABI-encoded parameter. No state is changed and no key is involved. When
tron_verify_usdt_transfer Moves money · ~442 tokens
TRC-20 USDT settlement check by transaction id: did it land, is it irreversible, how much, from and to whom. When to use: an agent or a merchant must confirm a USDT payment before releasing value - this is the settlement check that closes an automated trade loop. Do not use: to assess the counterpar
xmr_get_block ~218 tokens
One Monero block header, by height or by block hash. When to use: confirming which block a transaction landed in, or inspecting reward, difficulty and weight of a block. Do not use: to list recent blocks (xmr_get_recent_blocks) or to look up a transaction (xmr_get_transaction). Returns: height, hash
xmr_get_fee_rates ~186 tokens
Monero fee estimate per kB, split into ascending priority tiers, read from our own monerod. When to use: pricing an XMR transaction, or deciding whether to pay the baseline fee to land in the next block. Do not use: for Bitcoin fees (btc_get_fee_rates) or for mempool depth (xmr_get_mempool_state). R
xmr_get_mempool_state ~164 tokens
Monero mempool: pending transaction count, total bytes and fees, age of the oldest pending tx, double-spend/failing counts. When to use: is the network quiet or piling up, and roughly how long a new transaction waits. Do not use: for fees (xmr_get_fee_rates) or for a specific payment (xmr_get_transa
xmr_get_network_stats ~194 tokens
Monero network-wide state: network hashrate, difficulty, emission and fees over the last 720 blocks, protocol version and the next hard fork. When to use: macro questions about the Monero network - how much hashrate secures it, what is being issued, and which protocol version is active. Do not use:
xmr_get_node_status ~204 tokens
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 and txpool are. Do not use: for fees call xmr_get_fee_rates; for one transaction call xmr_get_transac
xmr_get_output_distribution ~282 tokens
Monero output distribution: how many spendable outputs fall into each ring-size bucket, read from our own monerod. This is the anonymity-set side of Monero that free explorers rarely expose. When to use: reasoning about Monero privacy - how large the spendable-output set is at a given height. Do not
xmr_get_recent_blocks ~166 tokens
The most recent Monero blocks with the observed block interval. When to use: checking that XMR is producing blocks normally and at roughly the 120s target. Do not use: for one specific block (xmr_get_block). Returns: tip_height, avg_block_interval_s, target_interval_s, blocks[] {height, hash, timest
xmr_get_transaction ~247 tokens
Look up one Monero transaction by txid: is it mined, in which block, how many confirmations, its size, output count and ring size. When to use: did this XMR transfer get into a block, and how deep is it now. Do not use: to learn the amount or the sender/recipient - Monero hides those by design and n
xmr_merchant_report ~379 tokens
Historical incoming-payment ledger for one Monero address, computed with a view key. Returns per-day counts and totals, the largest common amounts, confirmations, unlocked flags and a completion flag for a 1-30 day window. When to use: a merchant or treasury needs to reconcile what actually arrived
xmr_mining_profitability ~364 tokens
Mining profitability calculator using live chain difficulty and the Monero tail-emission reward: gross XMR per day/month, power cost, net USD profit, break-even XMR price, break-even electricity price and hardware ROI days. When to use: decide whether a given hashrate is worth running at a power pri
xmr_verify_payment ~454 tokens
Verify one Monero payment cryptographically, using proof material only the recipient can provide. Give it a txid plus either the transaction key (from your own wallet: get_tx_key <txid>) or a transaction proof signature (get_tx_proof), and it returns whether that transaction really pays the given ad
xmr_wallet_balance ~259 tokens
Balance for one Monero address using a view key: total, unlocked and pending XMR, with the scanned window and a completion flag. When to use: an agent or merchant wants to know how much an address holds right now, or whether incoming funds have unlocked, without running a wallet. Do not use: for pay
zec_get_network_stats ~227 tokens
Zcash network and node state: mempool size and bytes, node version, difficulty, network hashrate, chain progress and disk, block subsidy, and the funding streams (including Zcash Community Grants). When to use: macro questions about Zcash - how much hashrate secures it, whether our node is caught up
zec_get_pool_status ~182 tokens
Zcash chain state plus the distribution of all six value pools, in one call. When to use: how much ZEC sits in each shielded pool, the shielded share of supply, and whether the ZEC node is caught up. Do not use: we do not index Zcash transactions or wallets; for node peers and disk usage call chain_
zec_get_recent_blocks ~147 tokens
The most recent Zcash blocks. When to use: checking whether ZEC is producing blocks normally and at what interval. Do not use: for shielded-pool supply (that is zec_get_pool_status). Returns: for the last N blocks (default 5, max 20): height, hash, time, difficulty.
zec_get_transaction ~299 tokens
Zcash transaction check by txid from our own Zebra node: confirmations, block height and time, whether it is in the active chain, size, and how much of it is transparent versus shielded. When to use: did this ZEC payment land, how deep is it, and does it involve shielded inputs/outputs. Do not use:
zec_get_treestate ~195 tokens
Zcash shielded commitment-tree state: the Sapling, Orchard and Ironwood anchor roots at a given block. When to use: shielded-pool depth - how the shielded sets advance over time, or the anchor a wallet or prover needs to recognise. Do not use: for pool supplies (zec_get_pool_status) or a transaction

Browse

Related MCP servers

Robotbase Content
Agent MCP: 35 tools — social hot lists, attention trends, 80k+ books, 17 web tools.
ChainRay
Multi-chain on-chain intelligence for AI agents through a public remote MCP server.
TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures
Deterministic options, forex, risk, on-chain & futures math. 77 tools. Not AI estimates.
Tachyo
Crypto market intelligence, token rug-checks, and wallet verification in one MCP server.
Parlay
Read-only MCP server for live Polymarket, Kalshi, Limitless odds; Manifold sentiment.
SupplyGraph.AI Data
Official SupplyGraph.AI data MCP: POIs, parks, regions, industry chains, and companies.
Automaton Onchain Tools
Paid x402 crypto safety tools (Base/ETH/BSC): tx, approvals, contract risk, token deep scan.
OneQAZ Trading Intelligence
Verifiable crypto/KR/US market intelligence for AI agents: signals, hash-chained ledger. Not advice.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.github.wygogogo19/robotbase-mcp.svg)](https://aptlynx.net/servers/io.github.wygogogo19/robotbase-mcp)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents