Home / MCP registry index / io.github.wygogogo19/robotbase-mcp
io.github.wygogogo19/robotbase-mcp
io.github.wygogogo19/robotbase-mcp in the official MCP registry.
Endpoint https://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.
We read its 65 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
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
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-wygogogo19-robotbase-mcp)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
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |