RobotBase Multi-Chain Data Agent

Name: RobotBase Multi-Chain Data Agent
Author: wygogogo19

AgentA2AMCP

Read-only on-chain data agent for classic non-EVM proof-of-work chains (Bitcoin, Zcash, Dogecoin, Litecoin), exposed over the Model Context Protocol. Anonymous access, no tracking, no private keys.

by wygogogo19repository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"robotbase-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability90/90 checks ok

when	check	result	http	latency	detail
7 h ago	mcp initialize	ok	200	1318 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 20 tools
13 h ago	mcp initialize	ok	200	776 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 20 tools
19 h ago	mcp initialize	ok	200	645 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 20 tools
25 h ago	mcp initialize	ok	200	619 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 20 tools
31 h ago	mcp initialize	ok	200	640 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 20 tools
2 d ago	mcp initialize	ok	200	784 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 21 tools
2 d ago	mcp initialize	ok	200	716 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 21 tools
2 d ago	mcp initialize	ok	200	623 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 21 tools
2 d ago	mcp initialize	ok	200	707 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 21 tools
3 d ago	mcp initialize	ok	200	686 ms	server robotbase-mcp 0.6.0 · protocol 2025-06-18 · 21 tools

Tools observed via MCP handshake

list_chains — Every chain this service supports (BTC / XMR / ZEC) with live availability and block height. When to use: the user asks which chains you support, which nodes ar
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 i
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: ho
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 int
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
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
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
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 late
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…),
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
pow_network_mining_intel — Network hashrate and difficulty for BTC / XMR / ZEC (node-reported or difficulty-derived, stated per chain). When to use: mining economics, security budget, or
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
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
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
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 mine
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
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
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 ove
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 sy
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,

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

A2A Agent Cardhttps://robotbase.cc/.well-known/agent-card.json

first seen 25 d ago · fetched 10 d agoopen ↗

Official MCP Registryio.github.wygogogo19/robotbase-mcp

first seen 25 d ago · fetched 33 h agoopen ↗

Field history (12 recent events)

10 d ago · declared · summary → "Read-only on-chain data agent for classic non-EVM proof-of-work chains (Bitcoin, Zcash, Dogecoin, Litecoin), exposed ov
10 d ago · declared · description → "Read-only on-chain data agent for classic non-EVM proof-of-work chains (Bitcoin, Zcash, Dogecoin, Litecoin), exposed ov
25 d ago · declared · name → "RobotBase Multi-Chain Data Agent"
25 d ago · declared · kind → "agent"
25 d ago · declared · summary → "Read-only on-chain data agent for five non-EVM classic chains (Bitcoin, Monero, Zcash, Dogecoin, Litecoin), exposed ove
25 d ago · declared · description → "Read-only on-chain data agent for five non-EVM classic chains (Bitcoin, Monero, Zcash, Dogecoin, Litecoin), exposed ove
25 d ago · declared · publisherUrl → "https://robotbase.cc/"
25 d ago · declared · homepageUrl → "https://robotbase.cc/"
25 d ago · declared · version → "1.0.0"
25 d ago · declared · protocols → ["a2a","mcp"]
25 d ago · declared · homepageUrl → "https://robotbase.cc/mcp"
25 d ago · declared · repoUrl → "https://github.com/wygogogo19/robotbase-mcp"

RobotBase Multi-Chain Data Agent

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from