RoboSelect360 - Independent Humanoid Robot Intelligence
REMOTE · MCP.ROBOSELECT360.COM
Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2726 tokens (~90/item across 30 items; 30 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_robot_support” 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 5 Nov 2026 · Probed https://mcp.roboselect360.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roboselect360.com | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dd8f293660c5782313808d5bd33ca778 |
| SANs: roboselect360.com, *.roboselect360.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.roboselect360.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roboselect360.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.roboselect360.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.roboselect360.com/mcp | HTTPS enforced | 301 | https://mcp.roboselect360.com/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 →
get_access_manifest Your access manifest ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_robot_capabilities Observed capabilities ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
get_robot_support After-sales support profile ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
hardware_compare_robots Compare robots (semiconductor) ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_ids | string | yes | – |
No output schema declared.
No examples provided.
hardware_get_block_analysis Block analysis (semiconductor) ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_id | string | yes | – |
| robot_id | string | – | – |
No output schema declared.
No examples provided.
hardware_get_dependency_profile Semiconductor dependency profile ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
hardware_get_robot Robot profile (semiconductor coverage) ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
hardware_get_robot_hardware Semiconductor BOM teardown ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks_only | boolean | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
hardware_get_robot_signals Robot signals (semiconductor) ~54
Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.
| Name | Type | Req | Description |
|---|---|---|---|
| include_global | boolean | – | – |
| layer | string | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
hardware_get_system_status Semiconductor layer status ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hardware_list_robots Robot catalogue (semiconductor filters) ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categorie | string | – | – |
| in_scope_only | boolean | – | – |
| limit | integer | – | – |
| min_payload | number | – | – |
| min_score | integer | – | – |
| offset | integer | – | – |
| pays | string | – | – |
| scope_status | string | – | – |
No output schema declared.
No examples provided.
hardware_list_signals Signal feed (semiconductor) ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| block_id | string | – | – |
| component_type | string | – | – |
| layer | string | – | – |
| limit | integer | – | – |
| min_severity | string | – | – |
| offset | integer | – | – |
| region | string | – | – |
| signal_type | string | – | – |
No output schema declared.
No examples provided.
mechanical_compare_robots Compare robots (mechanical) ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_ids | string | yes | – |
No output schema declared.
No examples provided.
mechanical_get_block_analysis Block analysis (mechanical) ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_id | string | yes | – |
| robot_id | string | – | – |
No output schema declared.
No examples provided.
mechanical_get_dependency_profile Mechanical dependency profile ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
mechanical_get_robot Robot profile (mechanical coverage) ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
mechanical_get_robot_mechanical Mechanical BOM teardown ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks_only | boolean | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
mechanical_get_robot_signals Robot signals (mechanical) ~47
Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.
| Name | Type | Req | Description |
|---|---|---|---|
| include_global | boolean | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
mechanical_get_system_status Mechanical layer status ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mechanical_list_robots Robot catalogue (mechanical filters) ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categorie | string | – | – |
| in_scope_only | boolean | – | – |
| limit | integer | – | – |
| min_payload | number | – | – |
| min_score | integer | – | – |
| offset | integer | – | – |
| pays | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
mechanical_list_signals Signal feed (mechanical) ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| block_id | string | – | – |
| component_type | string | – | – |
| limit | integer | – | – |
| min_severity | string | – | – |
| offset | integer | – | – |
| region | string | – | – |
| signal_type | string | – | – |
No output schema declared.
No examples provided.
software_compare_robots Compare robots (software) ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_ids | string | yes | – |
No output schema declared.
No examples provided.
software_get_block_analysis Block analysis (software) ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_id | string | yes | – |
| robot_id | string | – | – |
No output schema declared.
No examples provided.
software_get_dependency_profile Software dependency profile ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
software_get_robot Robot profile (software coverage) ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
software_get_robot_signals Robot signals (software) ~47
Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.
| Name | Type | Req | Description |
|---|---|---|---|
| include_global | boolean | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
software_get_robot_software Software BOM teardown ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks_only | boolean | – | – |
| robot_id | string | yes | – |
No output schema declared.
No examples provided.
software_get_system_status Software layer status ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
software_list_robots Robot catalogue (software filters) ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categorie | string | – | – |
| in_scope_only | boolean | – | – |
| limit | integer | – | – |
| min_score | integer | – | – |
| offset | integer | – | – |
| pays | string | – | – |
| software_tier | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
software_list_signals Signal feed (software) ~108
List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| block_id | string | – | – |
| component_type | string | – | – |
| domain | string | – | – |
| jurisdiction | string | – | – |
| limit | integer | – | – |
| min_severity | string | – | – |
| offset | integer | – | – |
| signal_type | string | – | – |
No output schema declared.
No examples provided.
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.
remote · mcp.roboselect360.com
claude mcp add --transport http com-roboselect360-humanoid-robots 'https://mcp.roboselect360.com/mcp'
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.