io.github.wygogogo19/robotbase-mcp
REMOTE · ROBOTBASE.CC
Agent MCP: 65 tools — 5-chain verification, risk, prediction & crypto trends, 17 web tools.
Available components
Last scanned (11 days ago)
Scores higher than 0% of remote servers
Unreachable. Last reached 24 Oct 2026.
Category Crypto and Web3
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 12268 tokens (~188/item across 65 items; 65 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management16
- Stability check failed: schema churn in the 30 days we've observed: 21 tool removals, 0 breaking changes, 0 auth/transport breaks, 61 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "web_monitor_delete" implies "delete" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 −65
- Server version: 0.32.0 → 0.32.2 functional
- 23 Oct 26 0
- Tool “cyberlibrary_book_meta” was removed ▼ security
- Tool “cyberlibrary_catalog_index” was removed ▼ security
- Tool “cyberlibrary_cite” was removed ▼ security
- Tool “cyberlibrary_fulltext_search” was removed ▼ security
- Tool “cyberlibrary_get_chapter” was removed ▼ security
- Tool “cyberlibrary_get_chunks” was removed ▼ security
- Tool “cyberlibrary_get_markdown” was removed ▼ security
- Tool “cyberlibrary_get_toc” was removed ▼ security
- Tool “cyberlibrary_language_shard” was removed ▼ security
- Tool “cyberlibrary_rag_context” was removed ▼ security
- Tool “cyberlibrary_search” was removed ▼ security
- Tool “cyberlibrary_search_books” was removed ▼ security
- Tool “cyberlibrary_search_passages” was removed ▼ security
- Tool “cyberlibrary_semantic_search” was removed ▼ security
- Tool “cyberlibrary_service_info” was removed ▼ security
- Tool “cyberlibrary_verify_quote” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: robotbase-mcp → robotbase-mcp-web3 security
- Tool “web_monitor_list” rewrote its description, which is the text the model reads security
- Tool “web_act” rewrote its description, which is the text the model reads security
- Tool “web_crawl” rewrote its description, which is the text the model reads security
- Tool “web_extract” rewrote its description, which is the text the model reads security
- Tool “web_feed” rewrote its description, which is the text the model reads security
- Tool “web_fetch” rewrote its description, which is the text the model reads security
- Tool “web_map” rewrote its description, which is the text the model reads security
- Tool “web_metadata” rewrote its description, which is the text the model reads security
- Tool “web_screenshot” rewrote its description, which is the text the model reads security
- Tool “web_search” rewrote its description, which is the text the model reads security
- Schema quality: 13635 → 15224 ▼ functional
- Schema quality: 13635 → 12268 ▲ functional
- Server version: 0.31.0 → 0.32.0 functional
- Server version: 0.27.4 → 0.31.0 functional
- New tool “crypto_trending” functional
- New tool “prediction_market_odds” functional
- New tool “web_crawl_async” functional
- New tool “web_crawl_job” functional
- New tool “web_diff” functional
- New tool “web_extract_schema” functional
- New tool “web_monitor_delete” functional
- New tool “web_monitor_list” functional
- New tool “web_monitor_set” functional
- “web_monitor_list” added an optional parameter “include_diff” cosmetic
- “web_monitor_list” added an optional parameter “monitor_id” cosmetic
- 22 Oct 26 0
- Server version: 0.27.1 → 0.27.4 functional
- 21 Oct 26 0
- Server version: 0.27.0 → 0.27.1 functional
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “web_act” rewrote its description, which is the text the model reads security
- Tool “web_crawl” rewrote its description, which is the text the model reads security
- Tool “web_extract” rewrote its description, which is the text the model reads security
- Tool “web_feed” rewrote its description, which is the text the model reads security
- Tool “web_fetch” rewrote its description, which is the text the model reads security
- Tool “web_map” rewrote its description, which is the text the model reads security
- Tool “web_metadata” rewrote its description, which is the text the model reads security
- Tool “web_screenshot” rewrote its description, which is the text the model reads security
- Tool “web_search” rewrote its description, which is the text the model reads security
- Server version: 0.25.3 → 0.27.0 functional
- Server version: 0.25.2 → 0.25.3 functional
- 19 Oct 26 +6
- HTTPS: fail → unverified ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “web_search” rewrote its description, which is the text the model reads security
- Tool “cyberlibrary_search_books” rewrote its description, which is the text the model reads security
- Schema quality: 170 → 188 ▼ functional
- Schema quality: 9545 → 12587 ▼ functional
- Schema quality: 9545 → 10766 ▼ functional
- “cyberlibrary_search_books” made “lang” required, so existing callers break ▼ functional
- Server version: 0.22.0 → 0.25.2 functional
- Server version: 0.15.0 → 0.22.0 functional
- Server version: 0.13.1 → 0.15.0 functional
- New tool “cyberlibrary_search” functional
- New tool “web_act” functional
- New tool “web_crawl” functional
- New tool “web_extract” functional
- New tool “cyberlibrary_rag_context” functional
- New tool “cyberlibrary_search_passages” functional
- New tool “cyberlibrary_semantic_search” functional
- New tool “web_feed” functional
- New tool “web_fetch_batch” functional
- New tool “web_map” functional
- New tool “web_metadata” functional
- New tool “web_screenshot” functional
- New tool “cyberlibrary_get_chunks” functional
- New tool “cyberlibrary_verify_quote” functional
- New tool “web_fetch” functional
- New tool “web_search” functional
- “web_fetch” added an optional parameter “ocr” cosmetic
- “cyberlibrary_search_books” reworded the description of “lang” cosmetic
- “eth_get_logs” reworded the description of “from_block” cosmetic
- Tool “broadcast_raw_transaction” changed its title: Broadcast Raw Transaction cosmetic
- Tool “btc_get_address” changed its title: Btc Get Address cosmetic
- Tool “btc_get_block” changed its title: Btc Get Block cosmetic
- Tool “btc_get_fee_rates” changed its title: Btc Get Fee Rates cosmetic
- Tool “btc_get_mempool_state” changed its title: Btc Get Mempool State cosmetic
- Tool “btc_get_network_stats” changed its title: Btc Get Network Stats cosmetic
- Tool “btc_get_transaction” changed its title: Btc Get Transaction cosmetic
- Tool “chain_status” changed its title: Chain Status cosmetic
- Tool “cyberlibrary_book_meta” changed its title: Cyberlibrary Book Meta cosmetic
- Tool “cyberlibrary_catalog_index” changed its title: Cyberlibrary Catalog Index cosmetic
- Tool “cyberlibrary_cite” changed its title: Cyberlibrary Cite cosmetic
- Tool “cyberlibrary_fulltext_search” changed its title: Cyberlibrary Fulltext Search cosmetic
- Tool “cyberlibrary_get_chapter” changed its title: Cyberlibrary Get Chapter cosmetic
- Tool “cyberlibrary_get_chunks” changed its title: Cyberlibrary Get Chunks cosmetic
- Tool “cyberlibrary_get_markdown” changed its title: Cyberlibrary Get Markdown cosmetic
- Tool “cyberlibrary_get_toc” changed its title: Cyberlibrary Get Toc cosmetic
- Tool “cyberlibrary_language_shard” changed its title: Cyberlibrary Language Shard cosmetic
- Tool “cyberlibrary_search_books” changed its title: Cyberlibrary Search Books cosmetic
- Tool “cyberlibrary_service_info” changed its title: Cyberlibrary Service Info cosmetic
- Tool “cyberlibrary_verify_quote” changed its title: Cyberlibrary Verify Quote cosmetic
- Tool “eth_get_account” changed its title: Eth Get Account cosmetic
- Tool “eth_get_block” changed its title: Eth Get Block cosmetic
- Tool “eth_get_fee_rates” changed its title: Eth Get Fee Rates cosmetic
- Tool “eth_get_logs” changed its title: Eth Get Logs cosmetic
- Tool “eth_get_transaction” changed its title: Eth Get Transaction cosmetic
- Tool “eth_read_contract” changed its title: Eth Read Contract cosmetic
- Tool “list_chains” changed its title: List Chains cosmetic
- Tool “robotbase_capabilities” changed its title: Robotbase Capabilities cosmetic
- Tool “robotbase_services” changed its title: Robotbase Services cosmetic
- Tool “tron_check_address_risk” changed its title: Tron Check Address Risk cosmetic
- Tool “tron_get_account” changed its title: Tron Get Account cosmetic
- Tool “tron_get_block” changed its title: Tron Get Block cosmetic
- Tool “tron_get_chain_economics” changed its title: Tron Get Chain Economics cosmetic
- Tool “tron_get_contract” changed its title: Tron Get Contract cosmetic
- Tool “tron_get_current_block” changed its title: Tron Get Current Block cosmetic
- Tool “tron_get_node_status” changed its title: Tron Get Node Status cosmetic
- Tool “tron_get_transaction” changed its title: Tron Get Transaction cosmetic
- Tool “tron_list_proposals” changed its title: Tron List Proposals cosmetic
- Tool “tron_list_witnesses” changed its title: Tron List Witnesses cosmetic
- Tool “tron_read_contract” changed its title: Tron Read Contract cosmetic
- Tool “tron_verify_usdt_transfer” changed its title: Tron Verify Usdt Transfer cosmetic
- Tool “web_fetch” changed its title: Web Fetch cosmetic
- Tool “web_search” changed its title: Web Search cosmetic
- Tool “xmr_get_block” changed its title: Xmr Get Block cosmetic
- Tool “xmr_get_fee_rates” changed its title: Xmr Get Fee Rates cosmetic
- Tool “xmr_get_mempool_state” changed its title: Xmr Get Mempool State cosmetic
- Tool “xmr_get_network_stats” changed its title: Xmr Get Network Stats cosmetic
- Tool “xmr_get_node_status” changed its title: Xmr Get Node Status cosmetic
- Tool “xmr_get_output_distribution” changed its title: Xmr Get Output Distribution cosmetic
- Tool “xmr_get_recent_blocks” changed its title: Xmr Get Recent Blocks cosmetic
- Tool “xmr_get_transaction” changed its title: Xmr Get Transaction cosmetic
- Tool “xmr_merchant_report” changed its title: Xmr Merchant Report cosmetic
- Tool “xmr_mining_profitability” changed its title: Xmr Mining Profitability cosmetic
- Tool “xmr_verify_payment” changed its title: Xmr Verify Payment cosmetic
- Tool “xmr_wallet_balance” changed its title: Xmr Wallet Balance cosmetic
- Tool “zec_get_network_stats” changed its title: Zec Get Network Stats cosmetic
- Tool “zec_get_pool_status” changed its title: Zec Get Pool Status cosmetic
- Tool “zec_get_recent_blocks” changed its title: Zec Get Recent Blocks cosmetic
- Tool “zec_get_transaction” changed its title: Zec Get Transaction cosmetic
- Tool “zec_get_treestate” changed its title: Zec Get Treestate cosmetic
- 18 Oct 26 0
- Tool “base_check_contract_risk” was removed ▼ security
- Tool “base_get_balance” was removed ▼ security
- Tool “base_get_transaction” was removed ▼ security
- Tool “base_read_contract” was removed ▼ security
- Tool “sol_check_token_safety” was removed ▼ security
- Tool “sol_get_account” was removed ▼ security
- Tool “sol_get_balance” was removed ▼ security
- Tool “sol_get_transaction” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “tron_get_contract” rewrote its description, which is the text the model reads security
- Schema quality: 7833 → 9545 ▼ functional
- Tool coverage: 95% → 89% ▼ functional
- Server version: 0.12.5 → 0.13.1 functional
- Server version: 0.12.2 → 0.12.5 functional
- New tool “cyberlibrary_book_meta” functional
- New tool “cyberlibrary_catalog_index” functional
- New tool “cyberlibrary_cite” functional
- New tool “cyberlibrary_fulltext_search” functional
- New tool “cyberlibrary_get_chapter” functional
- New tool “cyberlibrary_get_markdown” functional
- New tool “cyberlibrary_get_toc” functional
- New tool “cyberlibrary_language_shard” functional
- New tool “cyberlibrary_search_books” functional
- New tool “cyberlibrary_service_info” functional
- New tool “xmr_merchant_report” functional
- New tool “xmr_mining_profitability” functional
- New tool “xmr_wallet_balance” functional
- New tool “base_get_balance” functional
- New tool “base_get_transaction” functional
- New tool “base_read_contract” functional
- New tool “sol_get_account” functional
- New tool “sol_get_balance” functional
- New tool “sol_get_transaction” functional
- “chain_status” reworded the description of “chain” cosmetic
- 17 Oct 26 0
- Tool “eth_get_block” rewrote its description, which is the text the model reads security
- Tool “eth_get_logs” rewrote its description, which is the text the model reads security
- Tool “eth_get_transaction” rewrote its description, which is the text the model reads security
- Server version: 0.12.0 → 0.12.2 functional
- “base_check_contract_risk” added an optional parameter “address” cosmetic
- “sol_check_token_safety” added an optional parameter “address” cosmetic
- “base_check_contract_risk” reworded the description of “contract” cosmetic
- “sol_check_token_safety” reworded the description of “mint” cosmetic
- “base_check_contract_risk” made “contract” optional cosmetic
- “sol_check_token_safety” made “mint” optional cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://robotbase.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=robotbase.cc | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 60447526cf6ab2960ea247fa7cc50202 |
| SANs: robotbase.cc, *.robotbase.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of robotbase.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | DS published | 12593 | 13 | Verified |
| robotbase.cc. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://robotbase.cc/mcp | Verified | 200 | |
| http (plaintext) | http://robotbase.cc/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
xmr_get_mempool_state Xmr Get Mempool State ~120
Monero mempool: pending transaction count, total bytes and fees, age of the oldest pending tx, double-spend/failing counts. When to use: is the network quiet or piling up, and roughly how long a new transaction waits. Do not use: for fees (xmr_get_fee_rates) or for a specific payment (xmr_get_transaction). Returns: pending_txs, bytes_total, fee_total_xmr, oldest_pending_age_s, double_spends, failing, tx_size_median_bytes, congestion verdict.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xmr_get_network_stats Xmr Get Network Stats ~144
Monero network-wide state: network hashrate, difficulty, emission and fees over the last 720 blocks, protocol version and the next hard fork. When to use: macro questions about the Monero network - how much hashrate secures it, what is being issued, and which protocol version is active. Do not use: for our node's own health (xmr_get_node_status). Returns: height, network_hashrate_hs, difficulty, block_size/weight median and limit, emission_last_720_blocks_xmr, fees_last_720_blocks_xmr, hard_fork_version, next_fork_earliest_height, client_version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xmr_get_node_status Xmr Get Node Status ~146
Monero node state: height vs target, sync flag, difficulty, txpool size, database size, monerod version and peer counts. When to use: whether the XMR node is synced and healthy, or how big its chain and txpool are. Do not use: for fees call xmr_get_fee_rates; for one transaction call xmr_get_transaction; for network-wide numbers call xmr_get_network_stats. RobotBase does not index Monero wallets or ring signatures. Returns: height, target_height, synced, status, network, difficulty, txpool_txs, database_size_gb, block_size_limit, version, incoming_connections / outgoing_connections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xmr_get_output_distribution Xmr Get Output Distribution ~206
Monero output distribution: how many spendable outputs fall into each ring-size bucket, read from our own monerod. This is the anonymity-set side of Monero that free explorers rarely expose. When to use: reasoning about Monero privacy - how large the spendable-output set is at a given height. Do not use: to guess a 'privacy score' (we return raw counts only). Boundary: monerod's distribution data lags the chain tip by roughly 5,000 blocks, so the default range is 5,010 to 5,000 blocks back and the response states the real height and the lag. Returns: tip_height, queried_range, data_lags_tip_by_blocks, start_height, outputs_before_start, distribution[] with the raw per-bucket counts.
| Name | Type | Req | Description |
|---|---|---|---|
| from_height | integer | – | Start height; defaults to tip-5010 |
| to_height | integer | – | End height; defaults to tip-5000 |
No output schema declared.
No examples provided.
xmr_get_recent_blocks Xmr Get Recent Blocks ~110
The most recent Monero blocks with the observed block interval. When to use: checking that XMR is producing blocks normally and at roughly the 120s target. Do not use: for one specific block (xmr_get_block). Returns: tip_height, avg_block_interval_s, target_interval_s, blocks[] {height, hash, timestamp, tx_count, reward_xmr, difficulty, weight}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many blocks (default 10, max 50) |
No output schema declared.
No examples provided.
xmr_get_transaction Xmr Get Transaction ~177
Look up one Monero transaction by txid: is it mined, in which block, how many confirmations, its size, output count and ring size. When to use: did this XMR transfer get into a block, and how deep is it now. Do not use: to learn the amount or the sender/recipient - Monero hides those by design and no third party can recover them; only the recipient (or a holder of the tx key) can prove a payment. Returns: found, confirmed, in_mempool, block_height, block_timestamp, confirmations, double_spend_seen, size_bytes, inputs, outputs, ring_size_per_input, tx_version, unlock_time, and explicitly the list of fields not disclosed by the protocol.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | 64 hex char Monero transaction id |
No output schema declared.
No examples provided.
xmr_merchant_report Xmr Merchant Report ~256
Historical incoming-payment ledger for one Monero address, computed with a view key. Returns per-day counts and totals, the largest common amounts, confirmations, unlocked flags and a completion flag for a 1-30 day window. When to use: a merchant or treasury needs to reconcile what actually arrived over a period, not just one txid - the thing a block explorer cannot do for Monero because amounts are hidden. Do not use: to check a single payment when you already have a tx key (xmr_verify_payment), or for balances (xmr_wallet_balance). Returns: tx_count, received_total_xmr, daily[], top_amounts[], transfers[], window.complete. The view key can read but never spend; it is used in a single-use view-only wallet and discarded.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Monero address to reconcile |
| include_pending | boolean | – | include pool/pending transfers (default true) |
| limit | integer | – | max transfers returned, 1-2000 (default 500) |
| period_days | integer | – | 1-30 days window (default 7) |
| view_key | string | yes | 64 hex char private view key (read-only, cannot spend) |
No output schema declared.
No examples provided.
xmr_mining_profitability Xmr Mining Profitability ~252
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 price and hardware ROI days. When to use: decide whether a given hashrate is worth running at a power price, or to explain why XMR mining economics changed. Do not use: for pool share accounting (this service runs no pool) or price prediction. Returns: network{}, gross_xmr{}, power{}, usd{}, profitable, roi_days, break-even fields.
| Name | Type | Req | Description |
|---|---|---|---|
| hardware_cost_usd | number | – | optional hardware cost for ROI |
| hashrate_hs | number | – | hashrate in H/s |
| hashrate_khs | number | – | alternative: kH/s |
| hashrate_mhs | number | – | alternative: MH/s |
| power_cost_kwh | number | – | electricity price per kWh (USD) |
| power_watts | number | – | rig power draw in watts |
| service_fee_percent | number | – | optional pool fee percent |
| xmr_price_usd | number | – | XMR price in USD for profit calc |
No output schema declared.
No examples provided.
xmr_verify_payment Xmr Verify Payment ~299
Verify one Monero payment cryptographically, using proof material only the recipient can provide. Give it a txid plus either the transaction key (from your own wallet: get_tx_key <txid>) or a transaction proof signature (get_tx_proof), and it returns whether that transaction really pays the given address, for how much, and how many confirmations. When to use: a merchant or agent needs to confirm an XMR payment arrived before releasing value, without trusting a block explorer - and for Monero there is no other way, because amounts and both counterparties are hidden by the protocol. Do not use: to discover payments you cannot already prove (RobotBase does not index Monero wallets, and no third party can enumerate your incoming payments), or for TRC-20 USDT settlement (that is tron_verify_usdt_transfer). Returns: verified, confirmations, received_xmr, received_atomic, in_pool. Neither the tx key nor the proof can be used to spend funds or to scan other payments.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Monero address that should have received the payment |
| message | string | – | Optional message the proof was signed over |
| signature | string | – | Transaction proof signature (get_tx_proof) instead of tx_key |
| tx_key | string | – | Transaction key from your own wallet (get_tx_key) |
| txid | string | yes | 64 hex char Monero transaction id |
No output schema declared.
No examples provided.
xmr_wallet_balance Xmr Wallet Balance ~177
Balance for one Monero address using a view key: total, unlocked and pending XMR, with the scanned window and a completion flag. When to use: an agent or merchant wants to know how much an address holds right now, or whether incoming funds have unlocked, without running a wallet. Do not use: for payment proof (xmr_verify_payment) or history (xmr_merchant_report). Returns: balance_xmr, unlocked_xmr, pending_xmr, scanned_to_height, chain_tip, complete. View key can read but never spend and is discarded after the call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Monero address |
| lookback_days | integer | – | rescan window in days, 1-3650 (default 30) |
| view_key | string | yes | 64 hex char private view key |
No output schema declared.
No examples provided.
zec_get_network_stats Zec Get Network Stats ~164
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). When to use: macro questions about Zcash - how much hashrate secures it, whether our node is caught up, what the block subsidy and funding allocations currently are. Do not use: for shielded-pool supplies (zec_get_pool_status) or our node's own sync state (zec_get_pool_status / chain_status). Returns: mempool, network, difficulty, network_hashrate_hs, blockchain, height, verification_progress, size_on_disk_gb, block_reward_zec, funding_streams[], lockbox_streams[].
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zec_get_pool_status Zec Get Pool Status ~140
Zcash chain state plus the distribution of all six value pools, in one call. When to use: how much ZEC sits in each shielded pool, the shielded share of supply, and whether the ZEC node is caught up. Do not use: we do not index Zcash transactions or wallets; for node peers and disk usage call chain_status. Returns: blocks/headers/estimated_height/chain_supply/difficulty/size_on_disk_gb, node_value_pools, pools[] with {pool, balance, share_of_supply_pct, delta_1h, delta_24h}, shielded_total, shielded_pct.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zec_get_recent_blocks Zec Get Recent Blocks ~95
The most recent Zcash blocks. When to use: checking whether ZEC is producing blocks normally and at what interval. Do not use: for shielded-pool supply (that is zec_get_pool_status). Returns: for the last N blocks (default 5, max 20): height, hash, time, difficulty.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | How many recent blocks to return; default 5 |
No output schema declared.
No examples provided.
zec_get_transaction Zec Get Transaction ~214
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. When to use: did this ZEC payment land, how deep is it, and does it involve shielded inputs/outputs. Do not use: to learn shielded amounts or parties - shielded values are hidden by the protocol and only a viewing key held by a party to the transaction can read them; this tool reports the shielded *shape* (spend/output/action counts) and says so explicitly rather than guessing. Returns: found, confirmations, block_height, block_hash, block_time, in_active_chain, size_bytes, transparent{inputs, outputs, total_output_zec}, shielded{sapling_spends, sapling_outputs, orchard_actions}, has_shielded_component, not_disclosed_by_protocol[].
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | 64 hex char Zcash transaction id |
No output schema declared.
No examples provided.
zec_get_treestate Zec Get Treestate ~137
Zcash shielded commitment-tree state: the Sapling, Orchard and Ironwood anchor roots at a given block. When to use: shielded-pool depth - how the shielded sets advance over time, or the anchor a wallet or prover needs to recognise. Do not use: for pool supplies (zec_get_pool_status) or a transaction (zec_get_transaction). Returns: block_hash, height, time, pools{sapling, orchard, ironwood}{final_root, final_state}.
| Name | Type | Req | Description |
|---|---|---|---|
| block_hash | string | – | 64 hex block hash |
| height | integer | – | Block height instead of a hash |
No output schema declared.
No examples provided.
How do I install the io.github.wygogogo19/robotbase-mcp server?
io.github.wygogogo19/robotbase-mcp is a hosted endpoint at https://robotbase.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · robotbase.cc
claude mcp add --transport http wygogogo19-robotbase-mcp 'https://robotbase.cc/mcp'
What is the io.github.wygogogo19/robotbase-mcp server?
io.github.wygogogo19/robotbase-mcp is listed in the public MCP registry as io.github.wygogogo19/robotbase-mcp. Agent MCP: 65 tools, 5-chain verification, risk, prediction & crypto trends, 17 web tools. This page covers its hosted endpoint (https://robotbase.cc/mcp).
Is the io.github.wygogogo19/robotbase-mcp server safe to use?
io.github.wygogogo19/robotbase-mcp scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.wygogogo19/robotbase-mcp server expose?
io.github.wygogogo19/robotbase-mcp exposes 65 tools: web_search, web_fetch, web_screenshot, web_map, web_fetch_batch, and 60 more. Their descriptions and schemas cost roughly 12,107 tokens of context every time the server is loaded.
Does the io.github.wygogogo19/robotbase-mcp server require authentication?
No. We connected to io.github.wygogogo19/robotbase-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.wygogogo19/robotbase-mcp server still maintained?
io.github.wygogogo19/robotbase-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.wygogogo19/robotbase-mcp server?
VerifyMCP ran 12 checks on io.github.wygogogo19/robotbase-mcp, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.wygogogo19/robotbase-mcp: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.