# io.github.wygogogo19/robotbase-mcp (remote · robotbase.cc)

Read-only BTC/XMR/ZEC/DOGE/LTC chain data for AI agents (16 tools)

- Trust score: 59/100 (low)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `robotbase.cc`: 59/100 (this document), [markdown](https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase.md), [page](https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase)

## Channel facts

- Endpoint: `https://robotbase.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1256 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 7 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http wygogogo19-robotbase-mcp 'https://robotbase.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "wygogogo19-robotbase-mcp": {
      "url": "https://robotbase.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wygogogo19-robotbase-mcp": {
      "type": "http",
      "url": "https://robotbase.cc/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wygogogo19-robotbase-mcp]
url = "https://robotbase.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wygogogo19-robotbase-mcp": {
      "type": "remote",
      "url": "https://robotbase.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wygogogo19-robotbase-mcp --url 'https://robotbase.cc/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wygogogo19-robotbase-mcp:
    url: "https://robotbase.cc/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "wygogogo19-robotbase-mcp": {
      "Transport": "http",
      "Url": "https://robotbase.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wygogogo19-robotbase-mcp -t streamable-http -u 'https://robotbase.cc/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 59, −2)

- [security regression] Stability: 0.13 → fail
- [security regression] Tool “xmr_fee_estimate” was removed
- [security regression] Tool “xmr_last_block” was removed
- [security regression] Tool “xmr_mempool_stats” was removed
- [security regression] Tool “xmr_node_info” was removed
- [security regression] 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
- [functional] 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”
- [cosmetic] “chain_status” reworded the description of “chain”

### 2026-09-16 (score 61, +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.

### 2026-09-14 (score 60, 0)

- [security] 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
- [functional improvement] Schema quality: 88 → 76
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

### 2026-09-13 (score 60)

First indexed and scored.

## MCP tools (15)

### `list_chains` (~73 tokens)

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.

### `chain_status` (~107 tokens)

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.

Input parameters:

- `chain` (string, required): Chain id: btc / kas / zec / rvn / doge / ltc

### `zec_chain_info` (~95 tokens)

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).

### `zec_recent_blocks` (~67 tokens)

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.

Input parameters:

- `n` (integer): How many recent blocks to return; default 5

### `btc_fee_estimates` (~76 tokens)

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.

### `btc_mempool_summary` (~51 tokens)

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.

### `btc_tx_lookup` (~85 tokens)

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.

Input parameters:

- `txid` (string, required): Bitcoin transaction hash (64 hex chars)

### `btc_block_summary` (~84 tokens)

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.

Input parameters:

- `blockhash` (string): Block hash (optional; use instead of height)
- `height` (integer): Block height (optional)

### `btc_address_summary` (~119 tokens)

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.

Input parameters:

- `address` (string, required): Bitcoin mainnet address

### `kas_node_status` (~89 tokens)

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.

### `kas_pool_status` (~99 tokens)

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.

### `rvn_node_status` (~51 tokens)

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.

### `rvn_pool_status` (~91 tokens)

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.

### `utxo_chain_status` (~71 tokens)

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).

Input parameters:

- `chain` (string, required): doge or ltc

### `robotbase_services` (~56 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase#diagnostics

## Score history

- 2026-09-20: 59
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 61
- 2026-09-16: 61
- 2026-09-15: 60
- 2026-09-14: 60
- 2026-09-13: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://robotbase.cc/mcp
- Repository: https://github.com/wygogogo19/robotbase-mcp
- Website: https://robotbase.cc/mcp
- Changelog RSS feed: https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase.xml
- Changelog JSON feed: https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase.json
- HTML version of this page: https://verifymcp.io/servers/wygogogo19-robotbase-mcp/robotbase