Official MCP RegistryListed
RoboSelect360 - Humanoid Robot Intelligence
Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key.
First seen 2 Oct 2026. Evidence as of 7 Oct 2026.
29
Tools
From an anonymous probe
1
Source listings
Each with its own history
2
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| get_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. | Read-only |
| get_robot_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. | Read-only |
| hardware_compare_robots | 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. | Read-only |
| hardware_get_block_analysis | 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. | Read-only |
| hardware_get_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. | Read-only |
| hardware_get_robot | 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. | Read-only |
| hardware_get_robot_hardware | 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. | Read-only |
| hardware_get_robot_signals | Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested. | Read-only |
| hardware_get_system_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. | Read-only |
| hardware_list_robots | 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. | Read-only |
| hardware_list_signals | 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. | Read-only |
| mechanical_compare_robots | 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. | Read-only |
| mechanical_get_block_analysis | 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. | Read-only |
| mechanical_get_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. | Read-only |
| mechanical_get_robot | 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. | Read-only |
| mechanical_get_robot_mechanical | 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. | Read-only |
| mechanical_get_robot_signals | Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested. | Read-only |
| mechanical_get_system_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. | Read-only |
| mechanical_list_robots | 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. | Read-only |
| mechanical_list_signals | 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. | Read-only |
| software_compare_robots | 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. | Read-only |
| software_get_block_analysis | 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. | Read-only |
| software_get_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. | Read-only |
| software_get_robot | 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. | Read-only |
| software_get_robot_signals | Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested. | Read-only |
| software_get_robot_software | 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. | Read-only |
| software_get_system_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. | Read-only |
| software_list_robots | 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. | Read-only |
| software_list_signals | List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot. | Read-only |
Change history
- get_robot_capabilities: tool added
- server instructions changed (+"One paid tool sits outside the three layers: get_robot_capabilities returns what a robot has actually been seen doing, capability by capability, with every dated observation behind it - failures included, never the manufacturer's claims taken as proof. It needs access to that robot, like the other paid tools.")
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.roboselect360/humanoid-robots | 2 Oct 2026 | 7 Oct 2026 | 1 |