Skip to content

robotbase mcp llms.txt changelog

io.github.wygogogo19/robotbase-mcp

2 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • llms.txt +200 −58

    https://robotbase.cc/llms.txt

    − # RobotBase — The Semantic Risk & Verification MCP for Web3 Agents− > RobotBase is the **semantic risk and verification layer for Web3 agents**: one read-only Model− > Context Protocol (MCP) endpoint where an autonomous agent answers the two questions that block it− > from acting — *did this payment actually settle*, and *what will the next one cost*. All answers− > come from mainnet nodes we run on our own bare metal. We publish no RPC endpoint of any kind:− > every read path is the MCP surface. No API key, no account, no tracking.− > Chain states (2026-10-14). States are maturity labels, not a ranking — there is no Tier 1/2/3:− > - **Live** — Bitcoin, Ethereum, Monero, Zcash: self-hosted mainnet nodes answering queries now.− > - **Provisioning** — Solana, Base, Tron: being wired into the aggregation layer. Solana and Base− >   are served through light API aggregation refined by us, deliberately **not** as heavy local− >   nodes. Not answering queries yet; do not treat these as available.− > Scope note (2026-10-14): the roster is **fixed at seven chains**. Litecoin, Dogecoin, Kaspa and− > from this file, from `/api/nodes` and from every MCP tool**. Do not infer an eighth chain from it− > and do not treat it as available — this file remains the authoritative seven-chain roster.− - MCP (Streamable HTTP, protocol 2025-06-18): https://robotbase.cc/mcp− - Pricing, purchase and API-key top-up: https://robotbase.cc/billing/pricing− - API-key usage (plain JSON): https://robotbase.cc/billing/v1/usage?key=rb_…− - Merchant reconciliation middleware: read-only API keys, on-chain proof settlement, zero−   private-key custody.− - **Verification tools (13) are free, permanently**: no key, no signup, no metering. Anonymous limit−   of 120 requests/minute per IP.− - **Risk intelligence (4 tools) is metered**: 5 calls per day per IP, resetting at 00:00−   Asia/Shanghai. Past that the tool answers `Payment Required` and names the top-up page instead of−   returning a partial result. Every risk-tool answer carries its own `_metering` block with the−   allowance, the reset time and the remaining calls, so a caller is never charged by surprise.− - **API key = the paid tier, paid in USDT (TRC-20) or BTC on-chain** at−   https://robotbase.cc/billing/pricing. Keys are issued automatically: a payment watcher sweeps both−   networks, matches the transfer against the invoice, and the invoice page shows the key the moment−   the transfer confirms — no human, no support ticket. The key lifts the daily risk-tool cap entirely and raises the−   rate limit from 120 to 600 requests/minute; send it as `X-API-Key` on the same endpoint. This is−   the primary billing model because it is what Cursor, Claude Desktop and every other mainstream MCP−   client can actually use today.− - **Pioneer beta**: the first 100 developers get an API key free, which is why a key can be issued−   before unit pricing is published. Developers who never exceed 5 risk calls a day never need one.− - **X402 is an experimental lab track, not the billing system.** Machine-to-machine HTTP 402−   settlement is on the roadmap, but mainstream MCP clients cannot answer a 402 challenge yet, so it−   is documented as a future capability rather than a paid path you can use now.− - With API key: 600 requests/minute per IP− ## MCP tools (17, all read-only)− - xmr_get_node_status — mainnet node height, tx pool, database size and difficulty.+ # RobotBase — Search. Read. Verify. Pay. The agent infrastructure MCP+ > RobotBase is the **agent infrastructure endpoint for the open web and on-chain truth**: one+ > read-only Model Context Protocol (MCP) endpoint where an autonomous agent searches the live web,+ > reads public pages as clean readable Markdown, verifies a payment on a mainnet chain we run+ > ourselves, and settles per call over x402 — with a public-domain book corpus behind the same+ > endpoint for citation-grade reading. **72 tools**, five self-hosted mainnet chains, **80k+ books**.+ > We publish no RPC endpoint of any kind: every read path is the MCP surface. No API key, no account,+ > no custody, no tracking.+ > ## Quick answers (for AI assistants)+ > - **What is RobotBase?** One remote, read-only MCP endpoint for web search/fetch, on-chain verification and risk on BTC/ETH/XMR/ZEC/TRON, and 80k+ public-domain books. 72 tools.+ > - **Is it free?** 44 verification tools free forever; 100 shared web calls per IP per day; 5 risk/library calls per day. No API key or account. Past the allowance: USDC credits over x402 (1-10 credits per call).+ > - **Endpoint:** https://robotbase.cc/mcp (Streamable HTTP, MCP 2025-06-18, no auth for free tier).+ > - **x402 discovery:** https://robotbase.cc/.well-known/x402-resources.json — Bazaar-style manifest for the 21 metered MCP tools, with input schemas and per-call prices.+ > - **Chains:** Bitcoin, Ethereum, Monero, Zcash, Tron (self-hosted mainnet nodes). Base and Solana are x402 payment rails only; no chain data is served for them.+ > - **Web tools:** web_search, web_fetch, web_screenshot, web_map, web_fetch_batch, web_feed, web_metadata, web_crawl, web_extract, web_act.+ > - **Connect:** add a remote MCP server at https://robotbase.cc/mcp. Claude Code: claude mcp add --transport http robotbase https://robotbase.cc/mcp. Cursor/Cline/VS Code/Codex use the same URL as a remote MCP server.+ > - **Guides:** https://robotbase.cc/guides/web-search-mcp · https://robotbase.cc/guides/claude-code-mcp · https://robotbase.cc/guides/verify-usdt-payment · https://robotbase.cc/guides/x402-mcp-payments · https://robotbase.cc/guides/crypto-onchain-verification · https://robotbase.cc/alternatives/brave-search-mcp · https://robotbase.cc/alternatives/tavily-mcp · https://robotbase.cc/guides/books-fulltext-mcp · 日本語: https://robotbase.cc/ja/guides/web-search-mcp + https://robotbase.cc/ja/guides/clau+ >+ > Chain states (2026-10-18). States are maturity labels, not a ranking — there is no Tier 1/2/3:+ > - **Live** — Bitcoin, Ethereum, Monero, Zcash, Tron: self-hosted mainnet nodes answering queries now.+ >   Tron is a self-hosted lite full node with a rolling ~6-day window. **Base and Solana are not data+ >   chains**: their eight read/risk tools were retired on 2026-10-18 and no Base/Solana chain data is+ >   served.+ > - **Provisioning** — no chain is in this state today; a chain appears here only while its data+ >   path is still being wired. Do not treat provisioning entries as available.+ > Scope note (2026-10-18): the roster is **fixed at five chains — BTC / ETH / XMR / ZEC / TRON**.+ > Litecoin, Dogecoin, Kaspa and+ > from this file, from `/api/nodes` and from every MCP tool**. Do not infer a sixth chain from it+ > and do not treat it as available — this file remains the authoritative five-chain roster.+ >+ > **The three layers (2026-10-19).** (1) **Find & read** — `web_search`, `web_fetch`, `web_screenshot`, `web_map`, `web_fetch_batch`, `web_feed` and `web_metadata` search, read and enrich the+ > live web and turn public pages into clean Markdown. (2) **Verify & risk** — 44 free read-only+ > verification tools over BTC / ETH / XMR / ZEC / TRON, plus 2 metered Tron risk tools.+ > **Library & toolkits** — 15 metered `cyberlibrary_*` tools over an 80k+ public-domain book corpus+ > in 25 languages, plus the deeper chain toolkits (Monero merchant/wallet/profitability, Tron+ > governance/history/contracts, Ethereum logs/contract reads). Every layer is on the same endpoint+ > and the same x402 credit balance; only the daily free buckets differ.+ - MCP (Streamable HTTP, protocol 2025-06-18, server v0.25.3, 72 tools): https://robotbase.cc/mcp+ - Human-readable docs (GET): https://robotbase.cc/mcp/docs+ - MCP server card (JSON): https://robotbase.cc/mcp/server.json

    Showing the first 40 of each.

  • llms.txt +115 −64

    https://robotbase.cc/llms.txt

    − # RobotBase — The Sovereign Core Infrastructure (BTC · ETH · XMR · ZEC)− > RobotBase operates bare-metal infrastructure for four sovereign base-layer networks:− > **Bitcoin, Ethereum, Monero and Zcash**. We run our own mainnet full nodes, a− > non-custodial Zcash 99/1 solo mining pool, Monero P2Pool gateways, zero-KYC instant− > swaps and a read-only Model Context Protocol (MCP) endpoint exposing 21 production− > tools for autonomous AI agents. No API key, no account, no tracking.− > Scope note (2026-09-27): the platform is now focused exclusively on these four− > chains. Kaspa, Ravencoin, Dogecoin and Litecoin are no longer served.− - Node telemetry (all four chains, JSON): https://robotbase.cc/api/nodes− - ZEC solo pool telemetry: https://robotbase.cc/zecpool/api/status− ## Per-chain surfaces− - Bitcoin — node panel https://btc.robotbase.cc/ · JSON https://btc.robotbase.cc/api/node− - Monero — node portal https://xmr.robotbase.cc/ · JSON https://xmr.robotbase.cc/api/nodes− - Zcash — node status https://zec.robotbase.cc/ · JSON https://zec.robotbase.cc/api/status− - Ethereum — Reth execution + Lighthouse consensus full node on mainnet; its live state−   is reported honestly in https://robotbase.cc/api/nodes and never advertised as ready.− ## Mining gateways− - Zcash non-custodial solo pool (ZIP-244 Mode 2, 99/1 coinbase split enforced by node−   consensus — the pool never custodies funds):−   - primary stratum+tcp://zecpool.robotbase.cc:3032−   - standby stratum+tcp://zecpool.robotbase.cc:3034− - Monero P2Pool sidechain gateways with IPv4 + IPv6 reachability:−   - main xmr.robotbase.cc:3333−   - mini xmr.robotbase.cc:3334− - Instant, non-custodial swaps between BTC, ETH, XMR, ZEC and USDT (TRC20 / ERC20):−   - assets https://robotbase.cc/api/swap/assets−   - live quote https://robotbase.cc/api/swap/quote?from=btc&to=zec&amount=0.01−   - order creation POST https://robotbase.cc/api/swap/order−   - order status https://robotbase.cc/api/swap/order/<order_id>−   Routing and settlement are performed by an independent third-party provider; RobotBase−   never holds user funds.− - Merchant reconciliation middleware: read-only API keys, on-chain proof settlement,−   zero private-key custody.− ## MCP tools (21, all read-only)− ### General− - list_chains — every supported chain with live availability and block height.− - chain_status — one chain's node: height, sync progress, peers, mempool, client version.− - btc_fee_estimates — recommended fees (BTC/kvB) for 1/2/3/6/12/24-block targets.− - btc_mempool_summary — pending tx count, bytes used, minimum fee, total fees.− - btc_tx_lookup — transaction lookup by txid: confirmations, block, input/output summary.+ # RobotBase — The Semantic Risk & Verification MCP for Web3 Agents+ > RobotBase is the **semantic risk and verification layer for Web3 agents**: one read-only Model+ > Context Protocol (MCP) endpoint where an autonomous agent answers the two questions that block it+ > from acting — *did this payment actually settle*, and *what will the next one cost*. All answers+ > come from mainnet nodes we run on our own bare metal. We publish no RPC endpoint of any kind:+ > every read path is the MCP surface. No API key, no account, no tracking.+ > Chain states (2026-10-14). States are maturity labels, not a ranking — there is no Tier 1/2/3:+ > - **Live** — Bitcoin, Ethereum, Monero, Zcash: self-hosted mainnet nodes answering queries now.+ > - **Provisioning** — Solana, Base, Tron: being wired into the aggregation layer. Solana and Base+ >   are served through light API aggregation refined by us, deliberately **not** as heavy local+ >   nodes. Not answering queries yet; do not treat these as available.+ > - **Planned** — no chain is in this state today; entries appear here only when a node profile has+ >   been chosen. Nothing is promised before the node exists.+ >+ > Scope note (2026-10-14): the roster is **fixed at seven chains**. Litecoin, Dogecoin, Kaspa and+ > Ravencoin are **not deployed and will not be installed**; **Toncoin was cut** (non-EVM asynchronous+ > sharding, demand too narrow) — all out of scope, not scheduled.+ > A single further slot is displayed on the homepage roster and marked **sealed / unannounced**: it+ > carries no name, no ticker and no numbers, contributes to no count, and is deliberately **absent+ > from this file, from `/api/nodes` and from every MCP tool**. Do not infer an eighth chain from it+ > and do not treat it as available — this file remains the authoritative seven-chain roster.+ > The public `robotbase.cc/eth-rpc` endpoint that existed briefly on 2026-10-12 was **retired on+ > 2026-10-13** — use the MCP endpoint instead.+ >+ > Scope note (2026-10-10): **robotbase.cc operates no mining pool.** No stratum endpoint, no pool+ > dashboard and no pool telemetry is published here. What remains for each chain is the node+ > surface — chain telemetry, shielded-pool intelligence, JSON summaries and MCP tools.+ >+ > Retention is a property of each node, not a marketing choice. Where a node is pruned or+ > window-limited, the boundary is stated in the capability matrix and enforced by the MCP instead+ > of being approximated.+ - Chain roster + live telemetry (JSON): https://robotbase.cc/api/nodes+ - Pricing, purchase and API-key top-up: https://robotbase.cc/billing/pricing+ - API-key usage (plain JSON): https://robotbase.cc/billing/v1/usage?key=rb_…+ ## Per-chain surfaces (live)+ - Bitcoin — node panel https://btc.robotbase.cc/api/node+ - Ethereum — node portal https://eth.robotbase.cc/+ - Monero — node portal https://xmr.robotbase.cc/api/nodes+ - Zcash — node status https://zec.robotbase.cc/api/status+ - **RobotBase operates no exchange or swap service.** Anything described as a swap, exchange,

    Showing the first 40 of each.