RoboSelect360 - Humanoid Robot Intelligence MCP server

• get_access_manifestFree

  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.

• hardware_compare_robotsFree

  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.

• hardware_get_block_analysisFree

  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.

• hardware_get_dependency_profileFree

  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.

• hardware_get_robotFree

  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.

• hardware_get_robot_hardwareFree

  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.

• hardware_get_robot_signalsFree

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

• hardware_get_system_statusFree

  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_robotsFree

  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.

• hardware_list_signalsFree

  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.

• mechanical_compare_robotsFree

  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.

• mechanical_get_block_analysisFree

  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.

• mechanical_get_dependency_profileFree

  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.

• mechanical_get_robotFree

  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.

• mechanical_get_robot_mechanicalFree

  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.

• mechanical_get_robot_signalsFree

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

• mechanical_get_system_statusFree

  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_robotsFree

  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.

• mechanical_list_signalsFree

  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.

• software_compare_robotsFree

  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.

• software_get_block_analysisFree

  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.

• software_get_dependency_profileFree

  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.

• software_get_robotFree

  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.

• software_get_robot_signalsFree

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

• software_get_robot_softwareFree

  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.

• software_get_system_statusFree

  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_robotsFree

  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.

• software_list_signalsFree

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

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1314ms20/20
• Tool poisoning28 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

RoboSelect360 - Humanoid Robot Intelligence: common questions

Is RoboSelect360 - Humanoid Robot Intelligence MCP server safe?

With care: it is graded C, so read the findings first (67/100). Read the RoboSelect360 - Humanoid Robot Intelligence safety report

How do I install RoboSelect360 - Humanoid Robot Intelligence?

It runs remotely at mcp-free.roboselect360.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does RoboSelect360 - Humanoid Robot Intelligence need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is RoboSelect360 - Humanoid Robot Intelligence maintained?

The latest release is v1.0.2.

Is RoboSelect360 - Humanoid Robot Intelligence up?

100% of our last 20 checks got an answer. We check remote servers about four times a day.