mcp-registry/app.robohub/robohub · v1.1.0
As of 2026-10-23 19:41 UTC, the Robohub MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 5 minutes.
Vendor-neutral catalog of 300+ commercial robots: search, compare specs, request vendor intros.
Claude Code
claude mcp add --transport http robohub-mcp-server https://robohub.app/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"robohub-mcp-server": {
"type": "http",
"url": "https://robohub.app/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 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 →
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 →
In the last 30 days: 0 tool(s) removed and 1 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.robohub%2Frobohub/fixes
{
"name": "compare_robots",
"description": "Side-by-side spec comparison of two robots by slug, plus RoboHub's editorial verdict when available.",
"inputSchema": {
"type": "object",
"required": [
"slug_a",
"slug_b"
],
"properties": {
"slug_a": {
"type": "string",
"description": "First robot slug."
},
"slug_b": {
"type": "string",
"description": "Second robot slug."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Compare two robots"
}{
"name": "get_robot",
"description": "Full catalog record for one robot by slug: description, specs, SDKs, use cases, verified manufacturer list prices (MSRP) where published, with their date and source; other robots are quote-only or have no public price (see price_provenance) and links.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Robot slug as returned by search_robots (e.g. 'unitree-g1')."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get robot details"
}{
"name": "list_categories",
"description": "All robot categories with counts and a few example robots each. Good first call to understand catalog coverage.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "List robot categories"
}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/app.robohub/robohub"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.robohub/robohub"}) over MCP.
request_vendor_intros ~494 tokenssearch_robots ~277 tokensget_robot ~127 tokenscompare_robots ~96 tokenslist_categories ~57 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%2Fapp.robohub%2Frobohub?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.robohub%2Frobohub?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.robohub%2Frobohub.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.robohub%2Frobohub.svg :target: https://glimind.com/server/mcp-registry%2Fapp.robohub%2Frobohub?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:be51066632642681…, first seen 2026-10-17, included at leaf 17027 of 54,154. Version history · verify what your client received.
Compare: most reliable data servers · most reliable retrieval servers · most reliable knowledge servers · most reliable other 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-23 19:41 UTC, the Robohub MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 5 minutes.
Robohub MCP server advertises 5 tools, including compare_robots, get_robot, list_categories, request_vendor_intros, search_robots.
Point your MCP client at this streamable-http endpoint: https://robohub.app/api/mcp
Glimind scanned all 5 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.