RoboSelect360 - Independent Humanoid Robot Intelligence

com.roboselect360/humanoid-robotsVersion 1.0.4

Humanoid robot intelligence: observed capabilities, BOM supply chain, pilot prep. Free and paid.

Status

Responds183 msNov 14, 2026, 14:13 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:13 UTC
Latency: 183 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.roboselect360.com/mcpResponds183 msNov 14, 2026, 14:13 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: humanoid-robots
Remote MCP server URL: https://mcp.roboselect360.com/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"humanoid-robots","type":"http","url":"https://mcp.roboselect360.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

32 tools

Tools of RoboSelect360 - Independent Humanoid Robot Intelligence
	Description		Read-only	Idempotent	Open world
`build_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, from list_robots), returns the full pre-pilot decision file in markdown: decision memo, the robots' announced facts, an evidence matrix per robot and per task with every dated observation behind it (failures included, with source, control mode and power), the gaps to close and who can close them, operating conditions and integration, the pilot specification, the questions to ask the manufacturer and the integrator, and the pilot self-assessment grid. Never recommends, ranks or chooses a robot, and computes no cost: the buyer decides. Requires the decision file access right, separate from robot access; without it the call returns a refusal with the link to request it.	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, from list_robots), returns the full pre-pilot decision file in markdown: decision memo, the robots' announced facts, an evidence matrix per robot and per task with every dated observation behind it (failures included, with source, control mode and power), the gaps to close and who can close them, operating conditions and integration, the pilot specification, the questions to ask the manufacturer and the integrator, and the pilot self-assessment grid. Never recommends, ranks or chooses a robot, and computes no cost: the buyer decides. Requires the decision file access right, separate from robot access; without it the call returns a refusal with the link to request it.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`get_robot_support`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`hardware_get_robot_signals`Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.	Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`mechanical_get_robot_signals`Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.	Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`prepare_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 structured, what the market has proven on their task (counted across the panel, no robot named), and the vigilance points their answers trigger. Stateless: send back the dossier returned by the previous call, with the answer to the question asked, as {question: <question id>, value: <choice code or free text>} (unknown: true for "I don't know", task: <n> for a task question); call with no dossier to start. action='sheet' returns the sheet built so far. Never recommends, ranks or names a robot and computes no cost. Free for everyone, no key and no account.	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 structured, what the market has proven on their task (counted across the panel, no robot named), and the vigilance points their answers trigger. Stateless: send back the dossier returned by the previous call, with the answer to the question asked, as {question: <question id>, value: <choice code or free text>} (unknown: true for "I don't know", task: <n> for a task question); call with no dossier to start. action='sheet' returns the sheet built so far. Never recommends, ranks or names a robot and computes no cost. Free for everyone, no key and no account.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	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. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.	No	Yes	Yes	No
`software_get_robot_signals`Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.	Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 9, 2026
Updated: Nov 9, 2026
Website: https://roboselect360.com/⁠ (opens in a new tab)
Repository: https://github.com/Roboselect360/roboselect360-mcp⁠ (opens in a new tab)
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing