# RoboSelect360 - Independent Humanoid Robot Intelligence (remote · mcp.roboselect360.com)

Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.roboselect360.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp.md), [page](https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp)

## Channel facts

- Endpoint: `https://mcp.roboselect360.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2726 tokens (~90/item across 30 items; 30 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server?

RoboSelect360 - Independent Humanoid Robot Intelligence is a hosted endpoint at https://mcp.roboselect360.com/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.

### Claude

```bash
claude mcp add --transport http com-roboselect360-humanoid-robots 'https://mcp.roboselect360.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-roboselect360-humanoid-robots": {
      "url": "https://mcp.roboselect360.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-roboselect360-humanoid-robots": {
      "type": "http",
      "url": "https://mcp.roboselect360.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-roboselect360-humanoid-robots]
url = "https://mcp.roboselect360.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-roboselect360-humanoid-robots": {
      "type": "remote",
      "url": "https://mcp.roboselect360.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-roboselect360-humanoid-robots --url 'https://mcp.roboselect360.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-roboselect360-humanoid-robots:
    url: "https://mcp.roboselect360.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-roboselect360-humanoid-robots": {
      "Transport": "http",
      "Url": "https://mcp.roboselect360.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-roboselect360-humanoid-robots -t streamable-http -u 'https://mcp.roboselect360.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-roboselect360-humanoid-robots": {
      "type": "http",
      "url": "https://mcp.roboselect360.com/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-11-05 (score 77, +1)

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

### 2026-11-03 (score 76, +1)

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

### 2026-11-01 (score 75, +1)

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

### 2026-10-29 (score 74, +1)

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

### 2026-10-27 (score 73, +1)

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

### 2026-10-25 (score 72, +1)

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

### 2026-10-23 (score 71, +1)

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

### 2026-10-22 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “get_robot_support”

## MCP tools (30)

### `hardware_get_system_status` (~46 tokens)

Semiconductor layer status

Health of the SEMICONDUCTOR layer: profiles loaded, semiconductor signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

### `hardware_list_robots` (~119 tokens)

Robot catalogue (semiconductor filters)

List the robot catalogue with filters, including semiconductor-layer scope and payload. Returns the same catalogue as the mechanical and software variants - call one, not three. Pick this one to filter on whether a robot is in scope for the semiconductor layer.

Input parameters:

- `categorie` (string)
- `in_scope_only` (boolean)
- `limit` (integer)
- `min_payload` (number)
- `min_score` (integer)
- `offset` (integer)
- `pays` (string)
- `scope_status` (string)

### `hardware_get_robot` (~65 tokens)

Robot profile (semiconductor coverage)

Commercial profile of one robot (specs, pricing, viability score), plus whether a per-robot semiconductor bill of materials exists for it. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

Input parameters:

- `robot_id` (string, required)

### `hardware_list_signals` (~112 tokens)

Signal feed (semiconductor)

List semiconductor supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

Input parameters:

- `active_only` (boolean)
- `block_id` (string)
- `component_type` (string)
- `layer` (string)
- `limit` (integer)
- `min_severity` (string)
- `offset` (integer)
- `region` (string)
- `signal_type` (string)

### `hardware_get_robot_signals` (~54 tokens)

Robot signals (semiconductor)

Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.

Input parameters:

- `include_global` (boolean)
- `layer` (string)
- `robot_id` (string, required)

### `hardware_get_block_analysis` (~62 tokens)

Block analysis (semiconductor)

Analyse one functional block of the semiconductor layer, for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

Input parameters:

- `block_id` (string, required)
- `robot_id` (string)

### `hardware_compare_robots` (~64 tokens)

Compare robots (semiconductor)

Compare 2 to 5 robots side by side on semiconductor BOM, metrics, risk and geographic exposure. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.

Input parameters:

- `robot_ids` (string, required)

### `hardware_get_dependency_profile` (~55 tokens)

Semiconductor dependency profile

Geopolitical and supply chain dependency analysis for one robot, built on its semiconductor BOM: geographic concentration, single-source exposure, export control. Requires an access right on the robot requested.

Input parameters:

- `robot_id` (string, required)

### `hardware_get_robot_hardware` (~62 tokens)

Semiconductor BOM teardown

Semiconductor bill of materials for one robot: functional blocks, components, suppliers. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

Input parameters:

- `blocks_only` (boolean)
- `robot_id` (string, required)

### `mechanical_get_system_status` (~46 tokens)

Mechanical layer status

Health of the MECHANICAL layer: mechanical profiles loaded, mechanical signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

### `mechanical_list_robots` (~110 tokens)

Robot catalogue (mechanical filters)

List the robot catalogue with filters, including mechanical-profile status and payload. Returns the same catalogue as the hardware and software variants - call one, not three. Pick this one to filter on mechanical coverage.

Input parameters:

- `categorie` (string)
- `in_scope_only` (boolean)
- `limit` (integer)
- `min_payload` (number)
- `min_score` (integer)
- `offset` (integer)
- `pays` (string)
- `status` (string)

### `mechanical_get_robot` (~57 tokens)

Robot profile (mechanical coverage)

Commercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

Input parameters:

- `robot_id` (string, required)

### `mechanical_list_signals` (~105 tokens)

Signal feed (mechanical)

List mechanical supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

Input parameters:

- `active_only` (boolean)
- `block_id` (string)
- `component_type` (string)
- `limit` (integer)
- `min_severity` (string)
- `offset` (integer)
- `region` (string)
- `signal_type` (string)

### `mechanical_get_robot_signals` (~47 tokens)

Robot signals (mechanical)

Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.

Input parameters:

- `include_global` (boolean)
- `robot_id` (string, required)

### `mechanical_get_block_analysis` (~67 tokens)

Block analysis (mechanical)

Analyse one mechanical block (actuation, structure, energy, perception), for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

Input parameters:

- `block_id` (string, required)
- `robot_id` (string)

### `mechanical_compare_robots` (~64 tokens)

Compare robots (mechanical)

Compare 2 to 5 robots side by side on mechanical BOM, specifications, risk and geographic exposure. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.

Input parameters:

- `robot_ids` (string, required)

### `mechanical_get_dependency_profile` (~56 tokens)

Mechanical dependency profile

Geopolitical and supply chain dependency analysis for one robot, built on its mechanical BOM: geographic concentration, critical raw materials, single-source exposure. Requires an access right on the robot requested.

Input parameters:

- `robot_id` (string, required)

### `mechanical_get_robot_mechanical` (~69 tokens)

Mechanical BOM teardown

Mechanical bill of materials for one robot: motors, reducers, screws, bearings, batteries, structure, wiring. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

Input parameters:

- `blocks_only` (boolean)
- `robot_id` (string, required)

### `software_get_system_status` (~44 tokens)

Software layer status

Health of the SOFTWARE layer: software profiles loaded, software signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

### `software_list_robots` (~112 tokens)

Robot catalogue (software filters)

List the robot catalogue with filters, including software tier and software-profile status. Returns the same catalogue as the hardware and mechanical variants - call one, not three. Pick this one to filter by software tier.

Input parameters:

- `categorie` (string)
- `in_scope_only` (boolean)
- `limit` (integer)
- `min_score` (integer)
- `offset` (integer)
- `pays` (string)
- `software_tier` (string)
- `status` (string)

### `software_get_robot` (~59 tokens)

Robot profile (software coverage)

Commercial profile of one robot (specs, pricing, viability score), plus its software tier and profile status. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

Input parameters:

- `robot_id` (string, required)

### `software_list_signals` (~108 tokens)

Signal feed (software)

List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

Input parameters:

- `active_only` (boolean)
- `block_id` (string)
- `component_type` (string)
- `domain` (string)
- `jurisdiction` (string)
- `limit` (integer)
- `min_severity` (string)
- `offset` (integer)
- `signal_type` (string)

### `software_get_robot_signals` (~47 tokens)

Robot signals (software)

Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.

Input parameters:

- `include_global` (boolean)
- `robot_id` (string, required)

### `software_get_block_analysis` (~68 tokens)

Block analysis (software)

Analyse one software block (OS, middleware, runtime, control, fleet), for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

Input parameters:

- `block_id` (string, required)
- `robot_id` (string)

### `software_compare_robots` (~70 tokens)

Compare robots (software)

Compare 2 to 5 robots side by side on software BOM, TCO, jurisdiction exposure, lock-in and export control risk. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.

Input parameters:

- `robot_ids` (string, required)

### `software_get_dependency_profile` (~56 tokens)

Software dependency profile

Jurisdiction and supply chain dependency analysis for one robot, built on its software stack: jurisdiction concentration, lock-in, export control, cloud dependency. Requires an access right on the robot requested.

Input parameters:

- `robot_id` (string, required)

### `software_get_robot_software` (~68 tokens)

Software BOM teardown

Software bill of materials for one robot: OS, middleware, AI runtime, motion control, fleet management. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

Input parameters:

- `blocks_only` (boolean)
- `robot_id` (string, required)

### `get_access_manifest` (~76 tokens)

Your access manifest

What THIS connection can call right now: tools callable without any purchase, tools that need an access right, the robots you already hold, and the ones that can be unlocked. Free for everyone, no key and no account. Call it FIRST: it removes the need to discover your own access rights by making calls that will be refused.

### `get_robot_capabilities` (~104 tokens)

Observed capabilities

What one robot has actually been seen doing, and the evidence for each capability: a label per capability (in production, attested by a customer or third party, shown by the manufacturer, claimed only, published failure, no evidence found) and every dated observation behind it, failures included, with source, conditions and control mode. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

Input parameters:

- `robot_id` (string, required)

### `get_robot_support` (~132 tokens)

After-sales support profile

After-sales support profile of one robot, for a buyer in Europe: warranty duration, start and exclusions, spare parts with dated offers (seller, price in original currency, availability, lead time), maintenance required of the operator, software updates and subscriptions, service in Europe, lifecycle, and the open questions to ask before signing. Every fact carries who states it, its evidence level, a verbatim quote and its source; unknowns are listed as unknown with their search date. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

Input parameters:

- `robot_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71
- 2026-10-23: 71
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 69
- 2026-10-19: 69
- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67

## Common questions

### What is the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server?

RoboSelect360 - Independent Humanoid Robot Intelligence is an MCP server listed in the public MCP registry as com.roboselect360/humanoid-robots. Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers. This page covers its hosted endpoint (https://mcp.roboselect360.com/mcp).

### Is the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server safe to use?

RoboSelect360 - Independent Humanoid Robot Intelligence scores 77 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 RoboSelect360 - Independent Humanoid Robot Intelligence MCP server expose?

RoboSelect360 - Independent Humanoid Robot Intelligence exposes 30 tools: hardware_get_system_status, hardware_list_robots, hardware_get_robot, hardware_list_signals, hardware_get_robot_signals, and 25 more. Their descriptions and schemas cost roughly 2,204 tokens of context every time the server is loaded.

### Does the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server require authentication?

No. We connected to RoboSelect360 - Independent Humanoid Robot Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server still maintained?

RoboSelect360 - Independent Humanoid Robot Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.roboselect360.com/mcp
- Website: https://roboselect360.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-roboselect360-humanoid-robots/mcp