Categories › Software Development › Hardware, IoT, embedded & 3D printing
Humanoid robot intelligence: observed capabilities, BOM supply chain, pilot prep. Free and paid.
Remote server: your requests and data go to mcp.roboselect360.com. Claude Code: claude mcp add --transport http roboselect360-independent-humanoid-robot https://mcp.roboselect360.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
hardware_get_system_status — Health of the SEMICONDUCTOR layer: profiles loaded, semiconductor signal counts, load errors. One status tool per layer - the three report dhardware_list_robots — List the robot catalogue with filters, including semiconductor-layer scope and payload. Returns the same catalogue as the mechanical and sofhardware_get_robot — Commercial profile of one robot (specs, pricing, viability score), plus whether a per-robot semiconductor bill of materials exists for it. Thardware_list_signals — List semiconductor supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an hardware_get_robot_signals — Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.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 athardware_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 listhardware_get_dependency_profile — Geopolitical and supply chain dependency analysis for one robot, built on its semiconductor BOM: geographic concentration, single-source exphardware_get_robot_hardware — Semiconductor bill of materials for one robot: functional blocks, components, suppliers. Requires an access right on the robot requested; wimechanical_get_system_status — Health of the MECHANICAL layer: mechanical profiles loaded, mechanical signal counts, load errors. One status tool per layer - the three repmechanical_list_robots — List the robot catalogue with filters, including mechanical-profile status and payload. Returns the same catalogue as the hardware and softwmechanical_get_robot — Commercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status. The commercial fields are identical imechanical_list_signals — List mechanical supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an accmechanical_get_robot_signals — Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.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 robotmechanical_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 mechanical_get_dependency_profile — Geopolitical and supply chain dependency analysis for one robot, built on its mechanical BOM: geographic concentration, critical raw materiamechanical_get_robot_mechanical — Mechanical bill of materials for one robot: motors, reducers, screws, bearings, batteries, structure, wiring. Requires an access right on thsoftware_get_system_status — Health of the SOFTWARE layer: software profiles loaded, software signal counts, load errors. One status tool per layer - the three report disoftware_list_robots — List the robot catalogue with filters, including software tier and software-profile status. Returns the same catalogue as the hardware and msoftware_get_robot — Commercial profile of one robot (specs, pricing, viability score), plus its software tier and profile status. The commercial fields are idensoftware_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 robotsoftware_get_robot_signals — Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.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 nasoftware_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 onsoftware_get_dependency_profile — Jurisdiction and supply chain dependency analysis for one robot, built on its software stack: jurisdiction concentration, lock-in, export cosoftware_get_robot_software — Software bill of materials for one robot: OS, middleware, AI runtime, motion control, fleet management. Requires an access right on the roboget_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, 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 custget_robot_support — After-sales support profile of one robot, for a buyer in Europe: warranty duration, start and exclusions, spare parts with dated offers (selprepare_pilot — Guides a buyer, one question at a time, through the G.R.O.U.N.D. method to a needs sheet for a first humanoid robot pilot: their need structbuild_pilot_decision_file — Paid follow-up of prepare_pilot. From the buyer's dossier (as returned by prepare_pilot) and 1 to 5 robots chosen by the buyer (robot_ids, fNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.