Robotbase Content

RobotBase MCP Server

One MCP endpoint for agents: search the web, read any page, verify on-chain payments, and pay per call — no API keys.

免鉴权 · 无追踪 · 只读 ｜ 自建裸金属全节点，对 Agent 暴露统一的「验证 + 风控」语义入口

Hosted surface: three MCP editions, all including the full 17-tool web toolbox: Web3 (https://web3.robotbase.cc/mcp, 65 tools — BTC/ETH/XMR/ZEC/TRON verification & risk, prediction markets, crypto trends), Dev (https://dev.robotbase.cc/mcp, 18 tools — GitHub/HF/npm/PyPI/HN trends + web), and Content (https://content.robotbase.cc/mcp, 35 tools — social hot lists, attention trends, 16 CyberLibrary book tools + web). https://robotbase.cc/mcp is the Web3 compatibility alias. This repository is the dependency-free reference implementation: 45 tools (41 free verification + 2 risk + 2 web).

https://robotbase.cc/mcp is a compatibility alias of Web3 for existing clients — it is not a separate MCP server and should not be listed as a separate connector.

All four include the 17-tool web toolbox. Free web allowance is 100 calls/day/IP per edition; the x402 credit balance is shared.

• Install guide for agents: llms-install.md · Privacy: https://robotbase.cc/privacy · Security: SECURITY.md

Base and Solana data tools were retired on 2026-10-18. The five-chain surface is Bitcoin, Ethereum, Monero, Zcash and Tron. x402 payments still settle in USDC on Base or Solana; that is a payment rail, not a data service.

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

An autonomous agent handling crypto has exactly two blocking questions: did this payment actually settle, and what will the next one cost. Ask an LLM those today and it has nowhere reliable to look — the MCP ecosystem is rich in wrappers around hosted indexers and thin on self-run infrastructure.

The Web3 edition answers with 65 strictly read-only tools (44 free verification tools + 2 metered risk tools + 2 market/trend tools + 17 web tools: 14 metered plus 3 free helpers — web_crawl_job, web_monitor_list and web_monitor_delete); this reference implementation ships 45 of them (41 free + 2 risk + 2 web). Everything is backed by our own full nodes, local indexes and a metered web layer: btc_get_transaction for the settlement check, btc_get_fee_rates and btc_get_mempool_state for the price of the next one, zec_get_pool_status for Zcash shielded-pool supply, a full Monero surface (xmr_get_fee_rates, xmr_get_transaction, xmr_verify_payment, …) read straight off our own monerod, an Ethereum surface (eth_get_transaction, eth_get_fee_rates, eth_read_contract) on our own Reth node, and a Tron surface (tron_read_contract, tron_get_transaction) on our own java-tron node.

Pricing

Base and Solana are a payment rail only. x402 settles in USDC on Base or Solana, but RobotBase does not serve Base or Solana chain data: those eight data tools were retired on 2026-10-18, and the roster is Bitcoin, Ethereum, Monero, Zcash and Tron.

Every metered answer carries its own _metering block (allowance, reset time, calls left), and a call that fails local validation — a malformed address or txid — does not consume the allowance. Past the free allowance the tool returns Payment Required and names the top-up page instead of a partial result.

There is no API key, no account and no subscription — from 2026-10-16 the paid tier is x402 machine payment only. When the free allowance runs out the tool answers 402 Payment Required with the full machine-readable terms in structuredContent.accepts[]. An agent settles one credit pack (EIP-3009 on Base, a signed transfer on Solana), then re-sends that same payment payload in params._meta["x402/payment"] on every later call: settlement is idempotent per payment nonce, so the payload is never charged twice — each call simply spends one credit until the pack is empty. Buy another pack to continue.

Replay works the same on both networks. For Solana the payload carries only the signed transaction, so the server recovers the payer from the settled-payment ledger by the transaction hash — it never re-simulates a transaction that already landed.

The x402 payment layer (open source)

x402_pay.py is the complete paid-tier implementation and it ships in this repo. It is standard library only — it talks HTTP to your facilitator and keeps a sqlite ledger. It never touches a private key and never submits a transaction.

What it does:

Enable it entirely through environment variables (see examples/x402.env.example):

export RB_X402_ENABLED=1

export RB_X402_FACILITATOR_URL=https://facilitator.example export RB_X402_OPTIONS='[{"network":"eip155:8453","asset":"0x…","pay_to":"0x…","decimals":6, …}]' export RB_X402_PACKS='[{"amount_atomic":"100000","calls":10,"label":"10 calls"}]' export RB_X402_LEDGER_DB=./x402_credit.db python3 server.py

With those unset, the server runs the free tier only. This repo ships the 45 chain/web tools as a reference implementation — the only differences from the hosted endpoint are where the per-chain backends point (your RB_* variables instead of ours) and the hosted-only CyberLibrary bridge (16 book tools) and fifteen additional web tools (screenshot, map, batch, feed, metadata, crawl, extract, act, extract_schema, diff, crawl_async, crawl_job, monitor_set, monitor_list, monitor_delete), which are not included here.

Check a payer's balance without spending a call:

GET https://robotbase.cc/mcp/credits?payer=<the address that paid>

→ { "found": true, "credits_remaining": 19, "calls_charged": 1, "last_payment": { … }, "packs": [ … ] }

EVM addresses are case-insensitive; there is no authentication because the balance is derived from public on-chain payments.

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_get_fee_rates","arguments":{}}}'

Tools (45 — reference implementation)

Public order is web-first, then high-frequency verification (the order returned by tools/list and server.json); the hosted endpoint puts its 16 CyberLibrary tools last.

The hosted endpoint https://robotbase.cc/mcp has 79 tools: these 45 plus 3 free XMR wallet/merchant tools, the 16 CyberLibrary book tools (cyberlibrary_catalog_index, cyberlibrary_language_shard, cyberlibrary_book_meta, cyberlibrary_get_toc, cyberlibrary_get_chapter, cyberlibrary_get_markdown, cyberlibrary_cite, cyberlibrary_search_books, cyberlibrary_fulltext_search, cyberlibrary_service_info, cyberlibrary_get_chunks, cyberlibrary_verify_quote, cyberlibrary_search_passages, cyberlibrary_rag_context, cyberlibrary_semantic_search, cyberlibrary_search) twelve additional web tools (web_screenshot, web_map, web_fetch_batch, web_feed, web_metadata, web_crawl, web_extract, web_act, web_extract_schema, web_diff, web_crawl_async, web_crawl_job) and 3 scheduled-monitor tools (web_monitor_set, web_monitor_list, web_monitor_delete).

Web tools (high-frequency)

The hosted endpoint exposes seventeen web tools: web_search, web_fetch, web_screenshot, web_map, web_fetch_batch, web_feed, web_metadata, web_crawl, web_extract, web_act, web_extract_schema, web_diff, web_crawl_async, web_crawl_job, web_monitor_set, web_monitor_list and web_monitor_delete. This reference implementation ships the first two; the other fifteen are hosted-only. They are listed first in the public tools/list order.

Two general-purpose web tools sit next to the on-chain surface. They are the entry point an agent uses before it verifies: search the live web, read the one page that looks authoritative, then check the claim on chain. No API key is needed to call them.

| To