mcp-registry/io.github.wygogogo19/robotbase-mcp · v0.12.2
As of 2026-10-18 05:02 UTC, the Wygogogo19 Robotbase MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 7 minutes.
Read-only MCP for BTC, ETH, XMR and ZEC: fees, nodes, p2pool, shielded pools.
Claude Code
claude mcp add --transport http wygogogo19-robotbase-mcp-server https://robotbase.cc/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"wygogogo19-robotbase-mcp-server": {
"type": "http",
"url": "https://robotbase.cc/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
45 of 45 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
45 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,586 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 24 tool(s) removed and 9 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp/fixes
{
"name": "base_check_contract_risk",
"description": "Base (EVM) token and contract risk screen: honeypot, transfer taxes, verified source, backdoors and liquidity lock. When to use: before an agent trades, quotes or accepts a token on Base, or when an address shows up in an AgentKit / onchain-agent flow and you need the hard facts first - can it be sold, what does the exit cost, who can change the rules. Do not use: for Solana mints (that is sol_check_token_safety) or for TRON addresses (tron_check_address_risk); it does not simulate a live sell. ",
"inputSchema": {
"type": "object",
"anyOf": [
{
"required": [
"contract"
]
},
{
"required": [
"address"
]
}
],
"properties": {
"address": {
"type": "string",
"description": "Alias for `contract` - accepted so a generic agent can pass `address`."
},
"contract": {
"type": "string",
"description": "Base ERC-20 / contract address (0x + 40 hex). Preferred name."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "btc_get_address",
"description": "Balance and activity of a Bitcoin address, with no key involved. When to use: reconciling a merchant wallet, or checking whether an address received funds and how active it is. Do not use: we do not label or risk-score addresses; for a single payment use btc_get_transaction. Returns: address, confirmed/unconfirmed balance, utxo count and total, tx count, last 10 transactions. Supports P2PKH (1..), P2SH (3..), bech32 (bc1q..), bech32m (bc1p..). Ultra-active addresses may return a degraded=true re",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Bitcoin mainnet address"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "btc_get_block",
"description": "Bitcoin block summary by height or hash; omit both for the chain tip. When to use: an overview of a block, or confirming which block a payment landed in. Do not use: to fetch a single payment (that is btc_get_transaction). Returns: hash, height, time, txs, size, weight, confirmations, previousblockhash.",
"inputSchema": {
"type": "object",
"properties": {
"height": {
"type": "integer",
"description": "Block height (optional)"
},
"blockhash": {
"type": "string",
"description": "Block hash (optional; use instead of height)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.wygogogo19/robotbase-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.wygogogo19/robotbase-mcp"}) over MCP.
eth_read_contract ~367 tokenstron_read_contract ~344 tokensxmr_verify_payment ~310 tokenseth_get_logs ~286 tokensbase_check_contract_risk ~254 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.wygogogo19%2Frobotbase-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:724dead069942fd0…, first seen 2026-10-17, included at leaf 17664 of 20,401. Version history · verify what your client received.
Compare: most reliable security servers · most reliable data servers · most reliable other servers · most reliable devops servers · most reliable blockchain servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 05:02 UTC, the Wygogogo19 Robotbase MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 7 minutes.
Wygogogo19 Robotbase MCP server advertises 45 tools, including base_check_contract_risk, broadcast_raw_transaction, btc_get_address, btc_get_block, btc_get_fee_rates.
Point your MCP client at this streamable-http endpoint: https://robotbase.cc/mcp
Glimind scanned all 45 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.