io.github.wygogogo19/robotbase-mcp
REMOTE · ROBOTBASE.CC · SCANNED SEP 20
Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1256 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 7 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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'
{
"mcpServers": {
"wygogogo19-robotbase-mcp": {
"url": "https://robotbase.cc/mcp"
}
}
} {
"servers": {
"wygogogo19-robotbase-mcp": {
"type": "http",
"url": "https://robotbase.cc/mcp"
}
}
} [mcp_servers.wygogogo19-robotbase-mcp] url = "https://robotbase.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wygogogo19-robotbase-mcp": {
"type": "remote",
"url": "https://robotbase.cc/mcp",
"enabled": true
}
}
} openclaw mcp add wygogogo19-robotbase-mcp --url 'https://robotbase.cc/mcp' --transport streamable-http
mcp_servers:
wygogogo19-robotbase-mcp:
url: "https://robotbase.cc/mcp" {
"McpServers": {
"wygogogo19-robotbase-mcp": {
"Transport": "http",
"Url": "https://robotbase.cc/mcp"
}
}
} assistant mcp add wygogogo19-robotbase-mcp -t streamable-http -u 'https://robotbase.cc/mcp'
{
"mcpServers": {
"wygogogo19-robotbase-mcp": {
"type": "http",
"url": "https://robotbase.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 −2
- Stability: 0.13 → fail ▼ security
- Tool “xmr_fee_estimate” was removed ▼ security
- Tool “xmr_last_block” was removed ▼ security
- Tool “xmr_mempool_stats” was removed ▼ security
- Tool “xmr_node_info” was removed ▼ security
- Tool “xmr_tx_lookup” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “btc_tx_lookup” rewrote its description, which is the text the model reads security
- Tool “chain_status” rewrote its description, which is the text the model reads security
- Tool “list_chains” rewrote its description, which is the text the model reads security
- Tool “robotbase_services” rewrote its description, which is the text the model reads security
- Tool “utxo_chain_status” rewrote its description, which is the text the model reads security
- Server version: 0.3.0 → 0.4.0 functional
- New tool “kas_node_status” functional
- New tool “kas_pool_status” functional
- New tool “rvn_node_status” functional
- New tool “rvn_pool_status” functional
- “chain_status” reworded the description of “chain” cosmetic
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “btc_address_summary” rewrote its description, which is the text the model reads security
- Tool “btc_block_summary” rewrote its description, which is the text the model reads security
- Tool “btc_fee_estimates” rewrote its description, which is the text the model reads security
- Tool “btc_mempool_summary” rewrote its description, which is the text the model reads security
- Tool “btc_tx_lookup” rewrote its description, which is the text the model reads security
- Tool “chain_status” rewrote its description, which is the text the model reads security
- Tool “list_chains” rewrote its description, which is the text the model reads security
- Tool “robotbase_services” rewrote its description, which is the text the model reads security
- Tool “utxo_chain_status” rewrote its description, which is the text the model reads security
- Tool “xmr_fee_estimate” rewrote its description, which is the text the model reads security
- Tool “xmr_last_block” rewrote its description, which is the text the model reads security
- Tool “xmr_mempool_stats” rewrote its description, which is the text the model reads security
- Tool “xmr_node_info” rewrote its description, which is the text the model reads security
- Tool “xmr_tx_lookup” rewrote its description, which is the text the model reads security
- Tool “zec_chain_info” rewrote its description, which is the text the model reads security
- Tool “zec_recent_blocks” rewrote its description, which is the text the model reads security
- Schema quality: 88 → 76 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “btc_address_summary” reworded the description of “address” cosmetic
- “btc_block_summary” reworded the description of “blockhash” cosmetic
- “btc_block_summary” reworded the description of “height” cosmetic
- “btc_tx_lookup” reworded the description of “txid” cosmetic
- “chain_status” reworded the description of “chain” cosmetic
- “utxo_chain_status” reworded the description of “chain” cosmetic
- “xmr_tx_lookup” reworded the description of “txid” cosmetic
- “zec_recent_blocks” reworded the description of “n” cosmetic
- 13 Sept 26 60
First indexed and scored.
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 20 Sept 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 | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 20a94bc3942b857f13d8c97268722a10 |
| 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. | present | 12593 | 13 | Verified |
| robotbase.cc. | absent | 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 | Served over HTTP | 200 |
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 →
btc_address_summary ~119
Balance and activity of a Bitcoin address: confirmed/unconfirmed balance, UTXO count and total, tx count, last 10 transactions. Supports P2PKH (1…), P2SH (3…), bech32 (bc1q…), bech32m (bc1p…). When to use: how much BTC this address holds, whether it received funds, how active it is. Note: ultra-active addresses such as exchange cold wallets may return a degraded response under index load.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin mainnet address |
No output schema declared.
No examples provided.
btc_block_summary ~84
Bitcoin block summary: tx count, size, weight, block time, confirmations; omit parameters for the current chain tip. When to use: how many transactions the latest block holds, or an overview of a given height or block hash.
| Name | Type | Req | Description |
|---|---|---|---|
| blockhash | string | – | Block hash (optional; use instead of height) |
| height | integer | – | Block height (optional) |
No output schema declared.
No examples provided.
btc_fee_estimates ~76
Recommended Bitcoin fees: rates (BTC/kvB) for 1/2/3/6/12/24-block confirmation targets, plus the mempool minimum fee. When to use: how much fee to pay, or what gets a fast confirmation. Do not use: overall congestion level → btc_mempool_summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
btc_mempool_summary ~51
Bitcoin mempool overview: pending tx count, bytes used, minimum fee, total fees, capacity limit. When to use: is the network congested right now, or how big the backlog is.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
btc_tx_lookup ~85
Look up a Bitcoin transaction by txid: confirmed or not, block height, confirmations, size, input/output summary. When to use: the user gives a 64-hex BTC txid and asks whether it confirmed or which block it is in. Do not use: other chains → chain_status.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Bitcoin transaction hash (64 hex chars) |
No output schema declared.
No examples provided.
chain_status ~107
Run-time status of one chain's node: block height, sync progress, connected peers, mempool tx count, client version. When to use: whether a given chain's node is synced, healthy or lagging. Do not use: fees → btc_fee_estimates; address balance → btc_address_summary; pool detail → kas_pool_status / rvn_pool_status.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain id: btc / kas / zec / rvn / doge / ltc |
No output schema declared.
No examples provided.
kas_node_status ~89
Kaspa node status: network height, DAA score, difficulty, network hashrate, DAG tips, block reward, 10 BPS cadence, next halving and the hashport ports this node serves. When to use: how high and how healthy the Kaspa node is, or the halving schedule. Do not use: our own pool's miners/blocks → kas_pool_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kas_pool_status ~99
RobotBase Kaspa solo hashport: tier state, pool hashrate, connected miners, accepted shares, blocks found, uptime, share difficulty, the last block found (hash, blue score, age) and stale/invalid counts. When to use: is the KAS hashport live, who is mining on it, did it ever find a real mainnet block. Do not use: chain-level hashrate → kas_node_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_chains ~73
Every chain this service supports (BTC/KAS/ZEC/RVN/DOGE/LTC) with live availability and block height. When to use: the user asks which chains you support, which nodes are online, or how high each chain is. Do not use: for detail on one chain, use chain_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
robotbase_services ~56
Live availability of every service behind the RobotBase gateway: the chain nodes, hashport engines, Web3 Agent Hub, AITOKENS and MCP itself. When to use: an overall health check, or which services are down.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rvn_node_status ~51
Ravencoin node status: height, sync state, network hashrate, difficulty and client version. When to use: whether the RVN node is synced and how big the network is right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rvn_pool_status ~91
RobotBase Ravencoin solo hashport: engine state, pool hashrate, connected miners, shares, share difficulty, the Stratum endpoint, fee and the per-miner independent coinbase payout mode. When to use: is the RVN hashport open, is anyone mining, what endpoint do I point a GPU rig at. Do not use: node-level data → rvn_node_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
utxo_chain_status ~71
Node status for DOGE or LTC (height, sync progress, peers, mempool tx count). When to use: Dogecoin or Litecoin node progress. For BTC/KAS/ZEC/RVN use chain_status (any chain in one call).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | doge or ltc |
No output schema declared.
No examples provided.
zec_chain_info ~95
Zcash mainnet info including the supply of all six value pools (transparent/sprout/sapling/orchard/lockbox/ironwood) — i.e. shielded-pool state. When to use: how much ZEC sits in the shielded/sapling/orchard pools, or privacy-pool size. Do not use: whether the ZEC node is synced → chain_status(zec).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zec_recent_blocks ~67
Height, hash, block time and difficulty of the most recent N Zcash blocks (N ≤ 20). When to use: check whether ZEC is producing blocks normally, and at what interval.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | How many recent blocks to return; default 5 |
No output schema declared.
No examples provided.
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. Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 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 59 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 15 tools: list_chains, chain_status, zec_chain_info, zec_recent_blocks, btc_fee_estimates, and 10 more. Their descriptions and schemas cost roughly 1,214 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 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.