mcp-registry/io.github.wygogogo19/robotbase-mcp · v0.25.3
As of 2026-10-20 06:12 UTC, the Wygogogo19 Robotbase MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 15 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.
72 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 →
11 parameter(s) across 7 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 →
Loading this server's tool list costs an agent ~15,788 tokens before any work — more than 90% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,365 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: 32 tool(s) removed and 27 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. 7 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": "eth_get_block",
"description": "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. When to use: block-level context - how full is Ethereum right now, when a block was produced, what the base fee was, or which builder produced it. Do not use: for a transaction (eth_get_transaction) or for fees across blocks (eth_get_fee_rates). Returns: found, number, hash, parent_hash, timestamp, age_s, tx_count, gas_used, gas_limit, gas",
"inputSchema": {
"type": "object",
"properties": {
"height": {
"description": "Block number (integer or hex), or a tag like latest / finalized / safe",
"type": "string"
},
"block_hash": {
"type": "string",
"description": "0x + 64 hex block hash; takes precedence"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Eth Get Block"
}{
"name": "eth_get_logs",
"description": "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). When to use: find transfers or contract events in a window - 'who moved this token in the last N blocks', or watch a contract's activity without an indexer. Do not use: for a single transaction (eth_get_transaction) or to scan huge ranges (max 1000 blocks per call, results truncated with a flag). Returns: filter, matched, returned, trun",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Max logs to return (default 50)"
},
"topic0": {
"type": "string",
"description": "Optional event signature hash filter"
},
"address": {
"type": "string",
"description": "Optional contract address filter"
},
"to_block": {
"description": "Integer or hex or tag; defaults to latest",
"type": "string"
},
"from_block": {
"description": "Integer or hex or tag; defaults to 50 blocks back",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Eth Get Logs"
}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 tokensxmr_mining_profitability ~346 tokenstron_read_contract ~344 tokensweb_act ~342 tokenscyberlibrary_get_chunks ~318 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:8f4454df986970e9…, first seen 2026-10-19, included at leaf 26558 of 31,172. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable devops servers · most reliable knowledge servers · most reliable search 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-20 06:12 UTC, the Wygogogo19 Robotbase MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 15 outages in 90 days, with a median recovery of 7 minutes.
Wygogogo19 Robotbase MCP server advertises 72 tools, including broadcast_raw_transaction, btc_get_address, btc_get_block, btc_get_fee_rates, btc_get_mempool_state.
Point your MCP client at this streamable-http endpoint: https://robotbase.cc/mcp
Glimind scanned all 72 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.