Home / MCP registry index / io.github.wygogogo19/robotbase-web3

Robotbase web3

io.github.wygogogo19/robotbase-web3 in the official MCP registry. Endpoint https://web3.robotbase.cc/mcp. Source: github.com/wygogogo19/robotbase-mcp.

The registry describes it as: Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http robotbase-web3 https://web3.robotbase.cc/mcp

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

code --add-mcp '{"name":"robotbase-web3","type":"http","url":"https://web3.robotbase.cc/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

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 web_extract_schema web_diff web_monitor_set web_monitor_list web_monitor_delete prediction_market_odds crypto_trending list_chains chain_status robotbase_services robotbase_capabilities btc_get_mempool_state btc_get_fee_rates btc_get_transaction btc_get_block btc_get_address btc_get_network_stats broadcast_raw_transaction eth_get_block eth_read_contract eth_get_logs eth_get_transaction eth_get_account eth_get_fee_rates tron_check_address_risk tron_verify_usdt_transfer tron_get_current_block tron_get_transaction tron_get_account tron_read_contract tron_get_block tron_get_node_status tron_get_contract tron_get_chain_economics tron_list_witnesses tron_list_proposals xmr_get_recent_blocks xmr_get_block xmr_get_node_status xmr_get_fee_rates xmr_get_mempool_state xmr_get_transaction xmr_get_network_stats xmr_verify_payment xmr_get_output_distribution xmr_merchant_report xmr_wallet_balance xmr_mining_profitability and 5 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 604e3d1d8c356478. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-wygogogo19-robotbase-web3/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-wygogogo19-robotbase-web3)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers