MCP servers observed by Lowdown
io.github.wygogogo19/robotbase-web3 MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 70 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.wygogogo19/robotbase-web3
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.wygogogo19/robotbase-web3?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
70 tools on 2026-11-18:
broadcast_raw_transactionbtc_get_addressbtc_get_blockbtc_get_fee_ratesbtc_get_mempool_statebtc_get_network_statsbtc_get_transactionchain_statuscrypto_trendingeth_get_accounteth_get_blocketh_get_fee_rateseth_get_logseth_get_transactioneth_read_contractlist_chainsltc_get_blockltc_get_fee_ratesltc_get_mempool_stateltc_get_network_statsltc_get_transactionprediction_market_oddsrobotbase_capabilitiesrobotbase_servicestron_check_address_risktron_get_accounttron_get_blocktron_get_chain_economicstron_get_contracttron_get_current_blocktron_get_node_statustron_get_transactiontron_list_proposalstron_list_witnessestron_read_contracttron_verify_usdt_transferweb_actweb_crawlweb_crawl_asyncweb_crawl_jobweb_diffweb_extractweb_extract_schemaweb_feedweb_fetchweb_fetch_batchweb_mapweb_metadataweb_monitor_deleteweb_monitor_listweb_monitor_setweb_screenshotweb_searchxmr_get_blockxmr_get_fee_ratesxmr_get_mempool_statexmr_get_network_statsxmr_get_node_statusxmr_get_output_distributionxmr_get_recent_blocksxmr_get_transactionxmr_merchant_reportxmr_mining_profitabilityxmr_verify_paymentxmr_wallet_balancezec_get_network_statszec_get_pool_statuszec_get_recent_blockszec_get_transactionzec_get_treestate
MCP Registry declaration
- Registry name:
io.github.wygogogo19/robotbase-web3 - Declared version: 0.32.3
- Status: active
- Declared hosts:
web3.robotbase.cc
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.wygogogo19/robotbase-web3", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.wygogogo19/robotbase-web3?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).