tron_get_contract — robotbase mcp MCP Tool
tron_get_contract
(tron get contract) is one of 70 tools on the
robotbase mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tron_get_contract from your client
- Claude Code robotbase mcp tron_get_contract run in your project directory
- Claude Desktop robotbase mcp tron_get_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor robotbase mcp tron_get_contract ~/.cursor/mcp.json
- VS Code robotbase mcp tron_get_contract .vscode/mcp.json
- Zed robotbase mcp tron_get_contract ~/.config/zed/settings.json
- Windsurf robotbase mcp tron_get_contract ~/.codeium/windsurf/mcp_config.json
- Cline robotbase mcp tron_get_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI robotbase mcp tron_get_contract ~/.gemini/settings.json
- Grok robotbase mcp tron_get_contract .mcp.json (in your project root)
- ChatGPT robotbase mcp tron_get_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai robotbase mcp tron_get_contract Settings → Connectors → Add custom connector
- LangChain robotbase mcp tron_get_contract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http robotbase-mcp https://robotbase.cc/mcpOther tools on this server
- 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
- ltc_get_fee_rates
- ltc_get_mempool_state
- ltc_get_transaction
- ltc_get_block
- ltc_get_network_stats
- 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_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
- zec_get_recent_blocks
- zec_get_pool_status
- zec_get_transaction
- zec_get_treestate
- zec_get_network_stats
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.