Robotbase MCP Server

RobotBase MCP Server

Read-only multi-chain data for AI agents — the first MCP server covering the six classic proof-of-work chains: Bitcoin · Kaspa · Zcash · Ravencoin · Dogecoin · Litecoin.

免鉴权 · 无追踪 · 只读 ｜ 面向 AI Agent 的六大经典 PoW 公链数据接口

Hosted endpoint: https://robotbase.cc/mcp · Landing page: https://robotbase.cc/mcp · Server card: https://robotbase.cc/mcp/server.json · Live usage audit: https://robotbase.cc/mcp/stats

Listed in the official MCP Registry as io.github.wygogogo19/robotbase-mcp · indexed by Glama · published on Smithery (wygogogo/robotbase-mcp).

---

Why

Ask any LLM today to check Bitcoin mempool fees, whether our Kaspa solo hashport ever found a real mainnet block, or the Zcash shielded-pool supply and it has nowhere to look: the MCP ecosystem is rich for EVM/Solana and nearly empty for the classic proof-of-work chains. This server fills that gap with 25 strictly read-only tools backed by our own full nodes, our own pool engines and local indexes.

Pioneer Beta — free API keys

The hosted endpoint is free to use anonymously (120 req/min). For the first 100 developers we hand out a dedicated Bearer key that raises the limit to 600 req/min and unlocks all 15 tools, free during the public beta:

→ Request Free Beta Key — open an issue with your project name and a way to reach you; we reply with an rb_… key.

No card, no payment, no custody. The beta is a public stress test — feedback is the currency.

Connect (3 lines)

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

Works with Claude Desktop, Cursor, VS Code (remote MCP), and any MCP client supporting Streamable HTTP (2025-06-18). No API key needed.

curl -s https://robotbase.cc/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"btc_fee_estimates","arguments":{}}}'

Tools (25)

Beyond a generic reader

Most MCP servers wrap a third-party API. These four capabilities come from infrastructure we operate, which is why they are hard to find elsewhere:

1. Mining intelligence — pow_halving_oracle, pow_network_mining_intel and the two pool tools read our own nodes and pool engines, not a public API.
2. Fee & mempool oracles — mempool_congestion_status + get_recommended_fee_rate answer the first question any autonomous agent has before it sends a transaction.
3. Local indexes & native registries — zec_shielded_pools_metrics (six value pools with deltas), zec_block_attribution_intel (shielded-coinbase share + /RobotBase/-tagged blocks from our own node scan), kas_pool_attribution_intel (hundreds of thousands of Kaspa blocks attributed to the pool that found them) and rvn_asset_lookup (Ravencoin's native asset registry straight from our own ravend).
4. Optional relay — broadcast_raw_transaction lets an agent sign locally and use us purely as a high-availability broadcast path; it is disabled unless the operator sets RB_ENABLE_BROADCAST=1.

Architecture

   AI Agent (Claude / Cursor / VS Code / custom)
            │  HTTPS · MCP Streamable HTTP (2025-06-18)
            ▼
   https://robotbase.cc/mcp          ← hosted, no auth required
            │
            ▼
   MCP server (dependency-free Python, this repo)
            ├── BTC  : Bitcoin Core RPC + electrs (address/tx index)
            ├── KAS  : kaspad (Rust) REST + our BlockDAG stratum hashport
            ├── ZEC  : Zebra RPC (valuePools → shielded-pool supply)
            ├── RVN  : Ravencoin Core RPC + our KawPoW solo hashport
            ├── DOGE : Dogecoin Core RPC
            ├── LTC  : Litecoin Core RPC
            └── meta : gateway service aggregation

Privacy & limits

• No auth for anonymous use; optional X-API-Key header (or ?key=) raises the limit.
• Anonymous 120 req/min per IP; with API key 600 req/min per IP (X-MCP-Plan / X-RateLimit-Limit response headers).
• Audit stores only a truncated SHA-256 of the client IP — never query parameters.
• Read-only: no trading, signing, custody, or write methods. BTC transactions are looked up with txindex.
• Responses are trimmed to ~3.8 KB per call to protect LLM context.

Self-hosting (this repo)

server.py is a dependency-free reference implementation that talks to your own nodes. Configure everything with environment variables:

export RB_BIND=0.0.0.0            # bind address (default 127.0.0.1)
export RB_PORT=8090               # listen port
export RB_BTC_RPC_URL=http://127.0.0.1:8332
export RB_BTC_RPC_USER=btcrpc
export RB_BTC_RPC_PASS=...
export RB_BTC_DASHBOARD=http://127.0.0.1:8600/api/node   # optional
export RB_ELECTRS_HOST=127.0.0.1  # electrs for btc_address_summary
export RB_ELECTRS_PORT=50001
export RB_ZEC_BASE=http://127.0.0.1:8080                  # status API with /api/chaininfo
export RB_DOGE_BASE=http://127.0.0.1:8080
export RB_LTC_BASE=http://127.0.0.1:8080
export RB_RVN_ASSET_BASE=http://127.0.0.1:18081           # raven asset registry (rvn_asset_lookup)
export RB_HOME_BASE=http://127.0.0.1:8081                 # gateway: /api/nodes /api/pools /api/node/kas
export RB_USAGE_DB=/opt/mcp/usage.db                      # optional usage audit
export RB_BILLING_DB=/opt/billing/billing.db              # optional: API-key verification
python3 server.py

See examples/ for client configs and examples/env.example for the full variable list. Endpoints exposed by the server itself: / (docs), /tools (tool list JSON), /server.json (server card), /stats (usage audit), /healthz.

License

MIT — see LICENSE.

---

RobotBase · read-only on-chain data infrastructure · https://robotbase.cc/