# RoboHub Robot Catalog (remote · robohub.app)

Vendor-neutral catalog of 300+ commercial robots: search, compare specs, request vendor intros.

- Trust score: 68/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `robohub.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/app-robohub-robohub/api-mcp.md), [page](https://verifymcp.io/servers/app-robohub-robohub/api-mcp)

## Channel facts

- Endpoint: `https://robohub.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 66/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 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 638 tokens (~127/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-robohub-robohub https://robohub.app/api/mcp
```

### Codex

```toml
[mcp_servers.app-robohub-robohub]
url = "https://robohub.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-robohub-robohub": {
      "type": "remote",
      "url": "https://robohub.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-robohub-robohub --url https://robohub.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-robohub-robohub:
    url: "https://robohub.app/api/mcp"
```

### Other

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

## 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-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (5)

### `search_robots` (~137 tokens)

Search robots

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.

Input parameters:

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

### `get_robot` (~55 tokens)

Get robot details

Full catalog record for one robot by slug: description, specs, SDKs, use cases, pricing and links.

Input parameters:

- `slug` (string, required): Robot slug as returned by search_robots (e.g. 'unitree-g1').

### `compare_robots` (~51 tokens)

Compare two robots

Side-by-side spec comparison of two robots by slug, plus RoboHub's editorial verdict when available.

Input parameters:

- `slug_a` (string, required): First robot slug.
- `slug_b` (string, required): Second robot slug.

### `list_categories` (~28 tokens)

List robot categories

All robot categories with counts and a few example robots each. Good first call to understand catalog coverage.

### `request_vendor_intros` (~235 tokens)

Request vendor introductions

Submit a B2B sourcing request to RoboHub on behalf of the user. Within 48 hours RoboHub replies by email with a free shortlist of 2-4 matching robots, indicative pricing and warm vendor introductions. Vendor-neutral and free for buyers. Only call this with the user's explicit consent and their real contact details.

Input parameters:

- `budget_range` (string, required): Approximate budget bracket in USD.
- `company` (string, required): Company name.
- `contact_name` (string, required): Full name of the contact person.
- `country` (string): Country of deployment (optional).
- `email` (string, required): Work email address where the shortlist should be sent.
- `industry` (string, required): Industry, e.g. 'logistics', 'agriculture', 'security', 'hospitality'.
- `notes` (string): Anything else relevant (optional).
- `robot_slug` (string): Slug of a specific robot the user is interested in (optional).
- `timeline` (string, required): Deployment timeline.
- `use_case` (string, required): What the robots should do, with as much operational detail as possible (environment, scale, constraints).

## Diagnostics

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

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 67
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://robohub.app/api/mcp
- Website: https://robohub.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-robohub-robohub/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-robohub-robohub/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-robohub-robohub/api-mcp
