Skip to content
ProtocolProbe
Explore

MCP servers › io.github.wygogogo19 › robotbase-web3

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.github.wygogogo19/robotbase-web3

Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 0.32.0Pythonstreamable HTTP65 tools

Summary

io.github.wygogogo19/robotbase-web3 is a remote MCP server listed in the official MCP registry at version 0.32.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 65 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
65
Last tested
2026-10-24

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-24
Mode
read-only (no tool calls)
Latest version
0.32.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
First listed version
2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-24
Package and repository
checked 2026-10-24
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 0.32.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory
65tools
0resources
0prompts

None of its 65 tools are described as changing anything. For 65 the reading was uncertain, so no mark is shown.

  • web_searchon 69 other servers

    “Search the live web and get ranked results with title, URL, snippet and published date.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • querystringrequired“Search query (1-200 characters).”
    • countinteger“Number of results to return, 1-10.”
    • freshnessstring“Optional freshness filter.”
    • sitestring“Optional: restrict results to one domain, e.g.”
    • langstring“Optional language preference, e.g.”
  • web_fetchon 14 other servers

    “Fetch one public web page and return its readable text as clean markdown or plain text, with navigation, scripts, headers and footers stripped.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • urlstringrequired“The http(s) URL to read (max 2048 chars).”
    • max_charsinteger“Truncate the returned content to this many characters (2000-20000).”
    • formatstring“Output format.”
    • ocrboolean“Force OCR on scanned PDFs/images (auto-detected by default; set false to skip).”
  • web_screenshoton 3 other servers

    “Capture a screenshot of one public web page as an image (JPEG) plus metadata.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • urlstringrequired“The http(s) URL to capture (max 2048 chars).”
    • widthinteger“Viewport width 320-1920.”
    • heightinteger“Viewport height 240-1200.”
    • full_pageboolean“Capture the whole page instead of the viewport.”
  • web_mapon 1 other server

    “Discover the URLs of one site - sitemap first, then same-host links from the homepage.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Site root or page URL (max 2048 chars).”
    • limitinteger“Max URLs to return, 1-50.”
  • web_fetch_batch

    “Fetch 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • urlsarrayrequired“1-5 http(s) URLs to fetch in one call.”
    • max_charsinteger“Snippet length per page, 200-2000.”
    • formatstring“Snippet format.”
  • web_feed

    “Read an RSS or Atom feed and return its latest items.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“RSS/Atom feed URL (max 2048 chars).”
    • limitinteger“Max items to return, 1-20.”
  • web_metadataon 2 other servers

    “Extract a page's structured metadata: Open Graph, Twitter cards, canonical URL, language and JSON-LD.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • urlstringrequired“The http(s) page URL (max 2048 chars).”
  • web_crawlon 9 other servers

    “Crawl 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • urlstringrequired“Start URL (same host is crawled).”
    • depthinteger“Link depth 1-2.”
    • max_pagesinteger“Max pages 1-20.”
    • max_charsinteger“Per-page content cap 200-4000.”
  • web_extracton 15 other servers

    “Extract structured data from one public page: tables (headers + rows), JSON-LD blocks, and Open Graph/Twitter/canonical/language metadata.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“The http(s) page URL.”
    • include_linksboolean“Also return same-host links (max 100).”
  • web_acton 1 other server

    “Drive 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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 2 required
    • urlstringrequired“The http(s) page URL.”
    • actionsarrayrequired“Actions: {type: click|type|press|scroll|wait_for|wait_ms, ...}”
    • screenshotboolean“Return a JPEG screenshot.”
    • full_pageboolean“Full-page screenshot.”
    • include_xhrboolean“Return JSON XHR responses captured while acting.”
    • max_charsinteger“Text cap 1000-20000.”
  • web_crawl_async

    “Submit a same-host crawl as an asynchronous job and return a job_id immediately.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • urlstringrequired“Start URL (same host is crawled).”
    • depthinteger“Link depth 1-2.”
    • max_pagesinteger“Max pages 1-20.”
    • max_charsinteger“Per-page content cap 200-4000.”
    • idempotency_keystring“Optional; retries within 24h return the same job.”
  • web_crawl_job

    “Check or cancel an asynchronous crawl job created by web_crawl_async.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • job_idstringrequired“job_id returned by web_crawl_async.”
    • actionstring“Poll status (default) or cancel the job.”
Show 53 more tools
  • web_extract_schema

    “Extract 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“The http(s) page URL.”
    • schemastring“Target schema; auto detects from JSON-LD types.”
  • web_diff

    “Fetch a page now and compare it with the previous snapshot of the same URL, returning whether it changed and a unified diff (no LLM).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • urlstringrequired“The http(s) page URL.”
    • max_charsinteger“Compare at most this many chars (500-12000).”
    • freshboolean“Bypass the page cache with a cache-busting query.”
  • web_monitor_set

    “Create 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • urlstringrequired“The http(s) URL to watch (max 2048 chars).”
    • interval_minutesinteger“Check interval 15-1440 minutes.”
    • webhook_urlstring“Optional https endpoint notified on each change (HMAC-signed).”
  • web_monitor_list

    “List 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs
    • monitor_idstring“Optional: return this monitor (owned by the calling IP) plus its most recent change diff.”
    • include_diffboolean“With monitor_id, include the latest unified diff.”
  • web_monitor_delete

    “Delete one scheduled change monitor owned by the calling IP (its event history is removed too).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • monitor_idstringrequired“monitor_id returned by web_monitor_set.”
  • prediction_market_odds

    “Live implied probabilities from prediction markets (Polymarket primary, Manifold fallback).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • querystring“Optional event/topic search, e.g.”
    • limitinteger
  • crypto_trendingon 5 other servers

    “Crypto attention and market context: CoinGecko trending coins, top markets, DeFi TVL and Fear & Greed.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • limitinteger
    • querystring“Optional token/theme hint (currently informational).”
  • list_chainson 16 other servers

    “List every chain on the RobotBase roster with its state.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • chain_statuson 2 other servers

    “Live run-time state of one chain's node.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • chainstringrequired“Chain id: btc / eth / xmr / zec / tron”
  • robotbase_services

    “Live availability of every service behind the RobotBase gateway: the chain nodes, Web3 Agent Hub, AITOKENS and MCP itself.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • robotbase_capabilities

    “Per-chain capability, retention boundary and fee model.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • btc_get_mempool_state

    “Bitcoin mempool depth, capacity load and a busy/normal verdict.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • btc_get_fee_rates

    “Bitcoin fee rates for confirmation targets, plus the mempool floor.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • btc_get_transaction

    “Look up one Bitcoin transaction by txid - the core settlement check.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • txidstringrequired“Bitcoin transaction hash (64 hex chars)”
  • btc_get_block

    “Bitcoin block summary by height or hash; omit both for the chain tip.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • heightinteger“Block height (optional)”
    • blockhashstring“Block hash (optional; use instead of height)”
  • btc_get_address

    “Balance and activity of a Bitcoin address, with no key involved.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • addressstringrequired“Bitcoin mainnet address”
  • btc_get_network_stats

    “Bitcoin 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 ind…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • broadcast_raw_transaction

    “Relay an already-signed raw transaction to the network through our own full node (non-custodial: we never see a private key).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • chainstringrequired
    • signed_raw_tx_hexstringrequired“Raw signed transaction hex”
  • eth_get_block

    “One Ethereum block by number, tag (latest/finalized/safe) or hash: timestamp, transaction count, gas used against the limit, base fee, block builder and size.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • height“Block number (integer or hex), or a tag like latest / finalized / safe”
    • block_hashstring“0x + 64 hex block hash; takes precedence”
  • eth_read_contract

    “Read-only (eth_call) against any Ethereum contract, executed by our own Reth node.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 2 required
    • contractstringrequired“0x + 40 hex contract address”
    • functionstringrequired“balanceOf | allowance | decimals | symbol | name | totalSupply, or a label for a raw selector”
    • argumentstring“Ethereum address argument (balanceOf / allowance)”
    • argument2string“Second address argument (allowance)”
    • selectorstring“Explicit 4-byte selector hex for non-ERC-20 calls”
    • parameterstring“ABI-encoded parameter hex (with an explicit selector)”
    • output_typestring
  • eth_get_logs

    “Ethereum event logs over a block range, optionally filtered by contract address and event signature, with ERC-20 Transfer logs decoded (token, from, to, amount).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs
    • from_block“Integer or hex or tag; defaults to 50 blocks back”
    • to_block“Integer or hex or tag; defaults to latest”
    • addressstring“Optional contract address filter”
    • topic0string“Optional event signature hash filter”
    • limitinteger“Max logs to return (default 50)”
  • eth_get_transaction

    “Ethereum 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, am…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • txidstringrequired“0x + 64 hex transaction hash”
  • eth_get_account

    “Ethereum account state from our own node: ETH balance, nonce, and whether the address is a contract.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • addressstringrequired“0x + 40 hex address”
  • eth_get_fee_rates

    “Ethereum fee market from our own Reth node: current and next base fee, priority-fee percentiles over the last blocks, and the estimated ETH cost of a plain transfer and of an ERC-20 transfer.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • tron_check_address_risk

    “TRON address risk intelligence: judicial and black-market labels, account profile and a 0-100 safety score.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • addressstringrequired“TRON base58 address (T...)”
  • tron_verify_usdt_transfer

    “TRC-20 USDT settlement check by transaction id: did it land, is it irreversible, how much, from and to whom.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • txidstringrequired“TRON transaction id (64 hex chars)”
    • expected_tostring“Optional: the recipient you expect”
    • expected_amount_usdtnumber“Optional: the USDT amount you expect”
  • tron_get_current_block

    “The current (tip) TRON block: number, id, parent, timestamp, transaction count and a breakdown by contract type, plus the producing witness.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • tron_get_transaction

    “One Tron transaction by txid: success or reverted, energy used, the call it made, and - this is the important part - any TRC-20 transfers decoded from the receipt logs (token, from, to, amount).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • txidstringrequired“64 hex char Tron transaction id”
  • tron_get_account

    “TRON account state read straight off our own node: TRX balance, whether the account is activated, energy and bandwidth (used / limit), whether it is a witness, and account age.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • addressstringrequired“TRON address, base58 (T...) or 41-hex”
  • tron_read_contract

    “Read-only (constant) call against any TRON contract, executed by our own node.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 2 required
    • contractstringrequired“Contract address (base58 or 41-hex)”
    • functionstringrequired“balanceOf | allowance | decimals | symbol | name | totalSupply, or a raw selector like 'foo(uint256)'”
    • argumentstring“TRON address argument (for balanceOf / allowance)”
    • argument2string“Second address argument (for allowance)”
    • parameterstring“Raw ABI-encoded parameter hex, for raw selectors”
    • output_typestring
  • tron_get_block

    “One Tron block by height or block id, read from our own node: producer, timestamp, transaction count split by contract type, and the tx ids in it.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • heightinteger“Block height”
    • block_idstring“Block id (64 hex chars); takes precedence over height”
  • tron_get_node_status

    “TRON node state from our own java-tron full node: tip height, finalized (solidity) height and how far solidity lags, peers, client version, transactions in the tip block.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • tron_get_contract

    “TRON contract metadata: name, creator, whether its ABI is published on chain, the function list, code hash and whether it looks like a TRC-20.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • addressstringrequired“TRON contract address”
  • tron_get_chain_economics

    “TRON chain economics straight off our node: energy price (sun per energy unit), transaction fee, account creation fee, witness pay per block, total energy and bandwidth limits, maintenance interval a…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • tron_list_witnesses

    “TRON super representatives and candidates: who is producing blocks, how many they produced, how many they missed, votes and websites - read from our own node.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“How many top producers to return (default 30)”
  • tron_list_proposals

    “Tron governance proposals: id, proposer, state, approvals, expiry and the parameters they would change.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“How many top proposals to return (default 20)”
  • xmr_get_recent_blocks

    “The most recent Monero blocks with the observed block interval.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“How many blocks (default 10, max 50)”
  • xmr_get_block

    “One Monero block header, by height or by block hash.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • heightinteger“Block height”
    • block_hashstring“64 hex chars; takes precedence over height”
  • xmr_get_node_status

    “Monero node state: height vs target, sync flag, difficulty, txpool size, database size, monerod version and peer counts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • xmr_get_fee_rates

    “Monero fee estimate per kB, split into ascending priority tiers, read from our own monerod.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • xmr_get_mempool_state

    “Monero mempool: pending transaction count, total bytes and fees, age of the oldest pending tx, double-spend/failing counts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • xmr_get_transaction

    “Look up one Monero transaction by txid: is it mined, in which block, how many confirmations, its size, output count and ring size.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • txidstringrequired“64 hex char Monero transaction id”
  • xmr_get_network_stats

    “Monero network-wide state: network hashrate, difficulty, emission and fees over the last 720 blocks, protocol version and the next hard fork.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • xmr_verify_payment

    “Verify one Monero payment cryptographically, using proof material only the recipient can provide.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 2 required
    • txidstringrequired“64 hex char Monero transaction id”
    • addressstringrequired“The Monero address that should have received the payment”
    • tx_keystring“Transaction key from your own wallet (get_tx_key)”
    • signaturestring“Transaction proof signature (get_tx_proof) instead of tx_key”
    • messagestring“Optional message the proof was signed over”
  • xmr_get_output_distribution

    “Monero output distribution: how many spendable outputs fall into each ring-size bucket, read from our own monerod.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • from_heightinteger“Start height; defaults to tip-5010”
    • to_heightinteger“End height; defaults to tip-5000”
  • xmr_merchant_report

    “Historical incoming-payment ledger for one Monero address, computed with a view key.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 2 required
    • addressstringrequired“Monero address to reconcile”
    • view_keystringrequired“64 hex char private view key (read-only, cannot spend)”
    • period_daysinteger“1-30 days window (default 7)”
    • include_pendingboolean“include pool/pending transfers (default true)”
    • limitinteger“max transfers returned, 1-2000 (default 500)”
  • xmr_wallet_balance

    “Balance for one Monero address using a view key: total, unlocked and pending XMR, with the scanned window and a completion flag.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • addressstringrequired“Monero address”
    • view_keystringrequired“64 hex char private view key”
    • lookback_daysinteger“rescan window in days, 1-3650 (default 30)”
  • xmr_mining_profitability

    “Mining profitability calculator using live chain difficulty and the Monero tail-emission reward: gross XMR per day/month, power cost, net USD profit, break-even XMR price, break-even electricity pric…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs
    • hashrate_hsnumber“hashrate in H/s”
    • hashrate_khsnumber“alternative: kH/s”
    • hashrate_mhsnumber“alternative: MH/s”
    • power_wattsnumber“rig power draw in watts”
    • power_cost_kwhnumber“electricity price per kWh (USD)”
    • xmr_price_usdnumber“XMR price in USD for profit calc”
    • hardware_cost_usdnumber“optional hardware cost for ROI”
    • service_fee_percentnumber“optional pool fee percent”
  • zec_get_recent_blocks

    “The most recent Zcash blocks.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • ninteger“How many recent blocks to return; default 5”
  • zec_get_pool_status

    “Zcash chain state plus the distribution of all six value pools, in one call.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • zec_get_transaction

    “Zcash transaction check by txid from our own Zebra node: confirmations, block height and time, whether it is in the active chain, size, and how much of it is transparent versus shielded.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • txidstringrequired“64 hex char Zcash transaction id”
  • zec_get_treestate

    “Zcash shielded commitment-tree state: the Sapling, Orchard and Ironwood anchor roots at a given block.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • block_hashstring“64 hex block hash”
    • heightinteger“Block height instead of a hash”
  • zec_get_network_stats

    “Zcash network and node state: mempool size and bytes, node version, difficulty, network hashrate, chain progress and disk, block subsidy, and the funding streams (including Zcash Community Grants).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
96% of 126
Tools with a description
100% of 65
Typical description length
604 characters

The tool set

Counted from the listing

Tools
65
Size of the list
about 16,955 tokens for an agent to load (characters ÷ 4)
Naming
65 of 65 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 65 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://web3.robotbase.cc/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "robotbase-web3": {
      "url": "https://web3.robotbase.cc/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "robotbase-web3": {
      "type": "http",
      "url": "https://web3.robotbase.cc/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"robotbase-web3","type":"http","url":"https://web3.robotbase.cc/mcp"}'
Claude Code
claude mcp add --transport http robotbase-web3 https://web3.robotbase.cc/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://web3.robotbase.cc/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint web3.robotbase.cc/mcpSession openedmatchesour test · 2026-10-24
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-24
Repository github.com/wygogogo19/robotbase-mcpOpens publiclymatchesapi.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.wygogogo19 · 4 servers
GitHub owner
a personal account (wygogogo19)
Repository
github.com/wygogogo19/robotbase-mcp
Stars
0
Repository age
31–90 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.wygogogo19/robotbase-web3

Answered from the data above

Is io.github.wygogogo19/robotbase-web3 safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.wygogogo19/robotbase-web3 need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.wygogogo19/robotbase-web3 been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of io.github.wygogogo19/robotbase-web3?

In github.com/wygogogo19/robotbase-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,133 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 65 tools, 0 resources, 0 prompts.
  4. 8,943 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-24; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
Python
api.github.com · 2026-10-24
Hosting type
remote (hosted by the publisher)
registry · 2026-10-24
MCP capability
tools
our test · 2026-10-24
Transport
streamable HTTP
registry · 2026-10-24
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-24
Lifecycle status
active
registry · 2026-10-24
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 0–9
api.github.com · 2026-10-24
Maintenance
active
api.github.com · 2026-10-24
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.wygogogo19/robotbase-web3: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.wygogogo19/robotbase-web3

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.wygogogo19/robotbase-web3)](https://protocolprobe.com/mcp/servers/io.github.wygogogo19/robotbase-web3)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology