RoboHub Robot Catalog
REMOTE · ROBOHUB.APP · SCANNED SEP 22
Vendor-neutral catalog of 300+ commercial robots: search, compare specs, request vendor intros.
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 Security66
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 670 tokens (~134/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 RoboHub Robot Catalog MCP server?
RoboHub Robot Catalog is a hosted endpoint at https://robohub.app/api/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 · robohub.app
claude mcp add --transport http app-robohub-robohub 'https://robohub.app/api/mcp'
{
"mcpServers": {
"app-robohub-robohub": {
"url": "https://robohub.app/api/mcp"
}
}
} {
"servers": {
"app-robohub-robohub": {
"type": "http",
"url": "https://robohub.app/api/mcp"
}
}
} [mcp_servers.app-robohub-robohub] url = "https://robohub.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-robohub-robohub": {
"type": "remote",
"url": "https://robohub.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-robohub-robohub --url 'https://robohub.app/api/mcp' --transport streamable-http
mcp_servers:
app-robohub-robohub:
url: "https://robohub.app/api/mcp" {
"McpServers": {
"app-robohub-robohub": {
"Transport": "http",
"Url": "https://robohub.app/api/mcp"
}
}
} assistant mcp add app-robohub-robohub -t streamable-http -u 'https://robohub.app/api/mcp'
{
"mcpServers": {
"app-robohub-robohub": {
"type": "http",
"url": "https://robohub.app/api/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.
- 20 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “request_vendor_intros” rewrote its description, which is the text the model reads security
- “request_vendor_intros” reworded the description of “industry” cosmetic
- 6 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “request_vendor_intros” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 22 Sept 2026 · Probed https://robohub.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=robohub.app | CN=WR3,O=Google Trust Services,C=US | 10 Aug 2026 | 8 Nov 2026 | RSA 2048 | SHA256-RSA | f6bdfcf611fb216e0a19ef8ddf097586 |
| SANs: robohub.app, www.robohub.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of robohub.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| robohub.app. | present | 26299 | 8 | Verified |
| robohub.app. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://robohub.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://robohub.app/api/mcp | HTTPS enforced | 301 | https://robohub.app:443/api/mcp |
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 →
compare_robots Compare two robots ~51
Side-by-side spec comparison of two robots by slug, plus RoboHub's editorial verdict when available.
| Name | Type | Req | Description |
|---|---|---|---|
| slug_a | string | yes | First robot slug. |
| slug_b | string | yes | Second robot slug. |
No output schema declared.
No examples provided.
get_robot Get robot details ~55
Full catalog record for one robot by slug: description, specs, SDKs, use cases, pricing and links.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Robot slug as returned by search_robots (e.g. 'unitree-g1'). |
No output schema declared.
No examples provided.
list_categories List robot categories ~28
All robot categories with counts and a few example robots each. Good first call to understand catalog coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_vendor_intros Request vendor introductions ~239
Record a B2B sourcing request with RoboHub on behalf of the user, for manual review by RoboHub's team. Vendor-neutral and free for buyers. Requests from this server are unverified, so RoboHub sends the buyer no confirmation email and guarantees no reply window. Only call this with the user's explicit consent and their real contact details; submissions are rate limited per client and fabricated requests are discarded.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_range | string | yes | Approximate budget bracket in USD. |
| company | string | yes | Company name. |
| contact_name | string | yes | Full name of the contact person. |
| country | string | – | Country of deployment (optional). |
| string | yes | Work email address where the shortlist should be sent. | |
| industry | string | yes | Closest industry bucket for the deployment. |
| notes | string | – | Anything else relevant (optional). |
| robot_slug | string | – | Slug of a specific robot the user is interested in (optional). |
| timeline | string | yes | Deployment timeline. |
| use_case | string | yes | What the robots should do, with as much operational detail as possible (environment, scale, constraints). |
No output schema declared.
No examples provided.
search_robots Search robots ~137
Search RoboHub's catalog of commercial robots by free-text query and optional filters. Returns compact summaries with catalog URLs. Note: robots with unknown pricing are excluded when max_price_usd is set.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one category. |
| limit | number | – | Max results to return (default 10, max 25). |
| max_price_usd | number | – | Only robots with a known price at or below this USD amount. |
| query | string | – | Free-text search over name, manufacturer, category, use cases and description (e.g. 'warehouse pallet AMR', 'quadruped inspection'). |
No output schema declared.
No examples provided.
What is the RoboHub Robot Catalog MCP server?
RoboHub Robot Catalog is an MCP server listed in the public MCP registry as app.robohub/robohub. Vendor-neutral catalog of 300+ commercial robots: search, compare specs, request vendor intros. This page covers its hosted endpoint (https://robohub.app/api/mcp).
Is the RoboHub Robot Catalog MCP server safe to use?
RoboHub Robot Catalog scores 81 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 RoboHub Robot Catalog MCP server expose?
RoboHub Robot Catalog exposes 5 tools: search_robots, get_robot, compare_robots, list_categories, request_vendor_intros. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.
Does the RoboHub Robot Catalog MCP server require authentication?
No. We connected to RoboHub Robot Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RoboHub Robot Catalog MCP server still maintained?
RoboHub Robot Catalog is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.