Agents Index

RobotBase Web3 MCP — on-chain verification, risk and market intelligence

OnlineNew

Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.

Visit publisherConnectJSON

What it can do: 70 tools

  • web_search read-onlySearch the live web and get ranked results with title, URL, snippet and published date. When to use: an agent needs current facts, news or links that are not on chain - 'what is the BTC fee market saying today', 'recent
  • web_fetch read-onlyFetch one public web page and return its readable text as clean markdown or plain text, with navigation, scripts, headers and footers stripped. When to use: you have a specific URL (from web_search or the user) and need
  • web_screenshot read-onlyCapture a screenshot of one public web page as an image (JPEG) plus metadata. When to use: visual layout matters - a dashboard, chart, UI state, or 'what does this page look like'. Do not use: to read text (use web_fetch
  • web_map read-onlyDiscover the URLs of one site - sitemap first, then same-host links from the homepage. When to use: you need the list of pages a site exposes before fetching a few of them. Do not use: as a crawler (max 50 URLs, no page
  • web_fetch_batch read-onlyFetch up to 5 public URLs in one call and return each page's title, engine and a short snippet (first ~1200 characters), so an agent can triage several links quickly. When to use: search returned several candidate pages
  • web_feed read-onlyRead an RSS or Atom feed and return its latest items. When to use: the user wants the latest posts/news from a site that publishes a feed, or you found a feed URL and want headlines plus links. Do not use: to read articl
  • web_metadata read-onlyExtract a page's structured metadata: Open Graph, Twitter cards, canonical URL, language and JSON-LD. When to use: you need the title/description/author/image of a page, or JSON-LD structured data for a product/article,
  • web_crawl read-onlyCrawl one site's same-host pages starting from a URL (depth 1-2, at most 20 pages) and return each page's title, URL and readable text. When to use: you need several pages from one site (docs section, news index, product
  • web_extract read-onlyExtract structured data from one public page: tables (headers + rows), JSON-LD blocks, and Open Graph/Twitter/canonical/language metadata. When to use: the page has tables or schema.org JSON-LD you need as data, without
  • web_act read-onlyDrive a real Chromium browser on one public page: click, type, press keys, scroll, wait for selectors, then return the resulting text (and optionally a screenshot and JSON XHR responses). When to use: the page needs inte
  • web_crawl_async read-onlySubmit a same-host crawl as an asynchronous job and return a job_id immediately. When to use: you need more than a couple of pages and cannot hold a long HTTP request; submit here, then poll web_crawl_job until status is
  • web_crawl_job read-onlyCheck or cancel an asynchronous crawl job created by web_crawl_async. When to use: after web_crawl_async, poll with action=status until status is done/failed/cancelled; use action=cancel to stop a running job. Do not use
  • web_extract_schema read-onlyExtract a page's structured data into a named schema's common fields (no LLM): article, product, event, faq, recipe, course, organization, local_business, breadcrumb, dataset or job_posting. When to use: you need fields
  • web_diff read-onlyFetch a page now and compare it with the previous snapshot of the same URL, returning whether it changed and a unified diff (no LLM). When to use: monitoring a page for updates - prices, docs, policy pages, SEO titles/me
  • web_monitor_set read-onlyCreate a scheduled change monitor for one public URL: the server re-fetches the page on an interval, stores a new snapshot and records a diff event whenever the readable text changes. When to use: the user wants to be to
  • web_monitor_list read-onlyList the scheduled change monitors owned by the calling IP, with latest/next check time, last title or error, and the 5 most recent change events. When to use: after web_monitor_set, poll this instead of re-fetching the
  • web_monitor_delete read-onlyDelete one scheduled change monitor owned by the calling IP (its event history is removed too). When to use: the user no longer needs to watch a page, or the per-IP monitor limit was reached. Do not use: to pause a monit
  • prediction_market_odds read-onlyLive implied probabilities from prediction markets (Polymarket primary, Manifold fallback). When to use: 'what does the market think will happen', event odds, election/crypto/macro probabilities. Do not use: for spot pri
  • crypto_trending read-onlyCrypto attention and market context: CoinGecko trending coins, top markets, DeFi TVL and Fear & Greed. When to use: what is trending in crypto, which tokens are moving, risk appetite, TVL leaders. Do not use: for on-chai
  • list_chains read-onlyList every chain on the RobotBase roster with its state. When to use: the user asks which chains are supported, which nodes are online, or where to start. Do not use: for one chain's live health call chain_status; for wh
  • chain_status read-onlyLive run-time state of one chain's node. When to use: is this chain's node synced, healthy or lagging; what is its height, peer count, mempool depth or client version. Do not use: fees (that is btc_get_fee_rates); a spec
  • robotbase_services read-onlyLive availability of every service behind the RobotBase gateway: the chain nodes, Web3 Agent Hub, AITOKENS and MCP itself. When to use: an overall platform health check, or finding which service is down. Do not use: for
  • robotbase_capabilities read-onlyPer-chain capability, retention boundary and fee model. When to use: before promising that some query is possible, or when a tool refused a query as out of range. Do not use: for live numbers (that is chain_status). Retu
  • btc_get_mempool_state read-onlyBitcoin mempool depth, capacity load and a busy/normal verdict. When to use: deciding whether now is a good moment to settle on-chain, or how large the backlog is. Do not use: to choose a fee (that is btc_get_fee_rates).
  • btc_get_fee_rates read-onlyBitcoin fee rates for confirmation targets, plus the mempool floor. When to use: pricing a Bitcoin transaction, or deciding when a sweep will confirm cheaply. Do not use: to measure backlog depth (that is btc_get_mempool
  • btc_get_transaction read-onlyLook up one Bitcoin transaction by txid - the core settlement check. When to use: has this payment arrived, which block is it in, how many confirmations does it have. Do not use: for a whole block (that is btc_get_block)
  • btc_get_block read-onlyBitcoin block summary by height or hash; omit both for the chain tip. When to use: an overview of a block, or confirming which block a payment landed in. Do not use: to fetch a single payment (that is btc_get_transaction
  • btc_get_address read-onlyBalance and activity of a Bitcoin address, with no key involved. When to use: reconciling a merchant wallet, or checking whether an address received funds and how active it is. Do not use: we do not label or risk-score a
  • btc_get_network_stats read-onlyBitcoin network and node state: difficulty, network hashrate, total transactions processed and the current tx/s rate, protocol version, peer connections, relay fee, mempool size, uptime and which indexes (txindex) are sy
  • broadcast_raw_transaction read-onlyRelay an already-signed raw transaction to the network through our own full node (non-custodial: we never see a private key). When to use: an agent signed a transaction locally and wants a high-availability broadcast pat
  • ltc_get_fee_rates read-onlyLitecoin fee rates for confirmation targets, plus the mempool floor, read from our own litecoind. When to use: pricing an LTC payment or deciding when a transfer will confirm cheaply. Do not use: to measure backlog depth
  • ltc_get_mempool_state read-onlyLitecoin mempool depth, fee-rate histogram and a busy/normal verdict. When to use: deciding whether now is a good moment to settle LTC, or how deep the pending backlog is. Do not use: to choose a fee (that is ltc_get_fee
  • ltc_get_transaction read-onlyLook up one Litecoin transaction by txid: the settlement check for an LTC payment. When to use: did an LTC payment arrive, which block is it in, how many confirmations does it have, or is it still pending. Do not use: fo
  • ltc_get_block read-onlyLitecoin block summary by height or hash; omit both for the chain tip. When to use: an overview of an LTC block, fee totals, MWEB activity, or confirming which block a payment landed in. Do not use: to fetch a single pay
  • ltc_get_network_stats read-onlyLitecoin network and node statistics from our own full node. When to use: network difficulty or hashrate, chain transaction throughput, node version, peers, uptime, relay fee or index health. Do not use: for fee advice (
  • eth_get_block read-onlyOne Ethereum block by number, tag (latest/finalized/safe) or hash: timestamp, transaction count, gas used against the limit, base fee, block builder and size. When to use: block-level context - how full is Ethereum right
  • eth_read_contract read-onlyRead-only (eth_call) against any Ethereum contract, executed by our own Reth node. ERC-20 helpers balanceOf / allowance / decimals / symbol / name / totalSupply are built in; any other function can be called by passing i
  • eth_get_logs read-onlyEthereum event logs over a block range, optionally filtered by contract address and event signature, with ERC-20 Transfer logs decoded (token, from, to, amount). When to use: find transfers or contract events in a window
  • eth_get_transaction read-onlyEthereum transaction check by hash: success or reverted, gas used, fee paid, confirmations, whether the block is finalized, and any ERC-20 transfers decoded from the receipt logs (token, from, to, amount). When to use: d
  • eth_get_account read-onlyEthereum account state from our own node: ETH balance, nonce, and whether the address is a contract. When to use: balance and account type before sizing a transfer, or telling an EOA from a contract. Do not use: for ERC-

…and 30 more.

Connect it

Claude Code
claude mcp add --transport http robotbase-web3-mcp-on-chain-verification https://web3.robotbase.cc/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://web3.robotbase.cc/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "robotbase-web3-mcp-on-chain-verification": {
      "url": "https://web3.robotbase.cc/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "robotbase-web3-mcp-on-chain-verification": {
      "type": "http",
      "url": "https://web3.robotbase.cc/mcp"
    }
  }
}

Questions

What does RobotBase Web3 MCP — on-chain verification, risk and market intelligence do?

Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools. It exposes 70 tools to AI assistants.

What tools does RobotBase Web3 MCP — on-chain verification, risk and market intelligence provide?

70 tools, including web_search, web_fetch, web_screenshot, web_map, web_fetch_batch, web_feed, web_metadata, web_crawl, web_extract, web_act, web_crawl_async, web_crawl_job….

How do I connect RobotBase Web3 MCP — on-chain verification, risk and market intelligence to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://web3.robotbase.cc/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does RobotBase Web3 MCP — on-chain verification, risk and market intelligence require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is RobotBase Web3 MCP — on-chain verification, risk and market intelligence online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes RobotBase Web3 MCP — on-chain verification, risk and market intelligence?

@wygogogo19 on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Crypto & Web3