io.github.wygogogo19/robotbase-mcp
Description
Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)
What our measurements say
io.github.wygogogo19/robotbase-mcp is a remote MCP server published at robotbase.cc. It has been probed 6 times since 9/14/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 842 ms, a delay an agent will notice. It exposes a broad tool surface of 16 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are descriptive and align with their functions (e.g., 'chain_status' for node health).
- Most tools include 'When to use' guidance, aiding agent decision-making.
Weaknesses
- Some parameters lack explicit constraints (e.g., 'n' in 'zec_recent_blocks' is optional but no max/min values).
- Tool 'utxo_chain_status' overlaps with 'chain_status' for DOGE/LTC, risking agent confusion.
zec_chain_info— No explicit error handling for non-ZEC chain inputs.utxo_chain_status— Ambiguous parameter 'chain' with no validation guidance.btc_address_summary— Truncated description ('Note: ultra-acti') may omit critical info.
Verdict
Event narrative
Risk: low
- 2026-09-14T06:26:32.997Z — smokeOk changed from null to true · indicates passing smoke test for first time
- 2026-09-14T08:31:43.472Z — smokeOk changed from true to null · suggests smoke test failure after initial success
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test passed · last run:
- Cold-start: cold 710ms → warm 378ms (penalty 332ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
list_chainsEvery chain this service supports (BTC/XMR/ZEC/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.
chain_statusRun-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 or xmr_fee_estimate; address balance → btc_address_summary.
chainstringrequired
zec_chain_infoZcash 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_blocksHeight, 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.
ninteger
btc_fee_estimatesRecommended 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_summaryBitcoin 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_lookupLook 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: Monero transactions → xmr_tx_lookup.
txidstringrequired
btc_block_summaryBitcoin 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.
heightintegerblockhashstring
btc_address_summaryBalance 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.
addressstringrequired
xmr_node_infoMonero full-node info: height, sync state, difficulty, in/out connections, database size, mempool tx count, version. When to use: how high the XMR node is, whether it finished syncing, whether it is connected to the network.
xmr_fee_estimateMonero fee estimate: per-byte rate, tiered rates (low/medium/high) and the quantization mask. When to use: how much fee an XMR transfer costs, or the current rate.
xmr_last_blockLatest Monero block header: height, hash, timestamp, difficulty, block reward, transaction count. When to use: XMR's most recent block time, latest height, or whether the chain stalled.
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Legacy
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-wygogogo19-robotbase-mcp)<a href="https://mcpmetrics.io/servers/io-github-wygogogo19-robotbase-mcp"><img src="https://mcpmetrics.io/badge/io.github.wygogogo19/robotbase-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- HODLXXI Read-Onlyhodlxxi.com
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
- Rialto Swap (read-only)mcp-rialto.hoodly.io
Read-only MCP for Rialto quotes and swap preflight on Robinhood Chain. No signing or broadcast.
- MCP Observatory: one read only walk over every https endpoint in the official registryobservatory.horizonshield.dev
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
- data: URI media-type only, payload discardedagent-observatory-sensor.nolimit-observatory.workers.dev
data: URI media-type only, payload discarded
- Zillow MCP — Property Data, Zestimates & Listings for AI Agentsapi.zillapi.com
Zillow MCP for AI agents: property data, Zestimates & listings — 300+ fields per home. Free tier.
- US Economic, SEC EDGAR & On-Chain Data (x402)x402.agentfund.net
21 paid tools: US macro data, SEC EDGAR filings, on-chain EVM reads. Settled in USDC on Base.
Comments
Sign in to write a comment
No comments yet. Be the first.