Connect RoboSelect360 - Independent Humanoid Robot Intelligence and your agent gets 27 tools, among them hardware_compare_robots, hardware_get_block_analysis, hardware_get_dependency_profile. It answers at https://mcp.roboselect360.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: robot_ids |
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. Inputs: block_id, robot_id |
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. Inputs: robot_id |
hardware_get_robot | Commercial profile of one robot (specs, pricing, viability score), plus whether a semiconductor teardown exists for it. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference. Inputs: robot_id |
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. Inputs: robot_id, blocks_only |
hardware_get_robot_signals | Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested. Inputs: robot_id, include_global, layer |
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. |
hardware_list_robots | List the robot catalogue with filters, including semiconductor tier and payload. Returns the same catalogue as the mechanical and software variants - call one, not three. Pick this one to filter by semiconductor tier. Inputs: tier, categorie, pays, min_payload, min_score, in_scope_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. Inputs: signal_type, min_severity, block_id, component_type, region, layer |
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. Inputs: robot_ids |
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. Inputs: block_id, robot_id |
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. Inputs: robot_id |
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. Inputs: robot_id |
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. Inputs: robot_id, blocks_only |
mechanical_get_robot_signals | Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested. Inputs: robot_id, include_global |
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. |
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. Inputs: status, categorie, pays, min_payload, min_score, in_scope_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. Inputs: signal_type, min_severity, block_id, component_type, region, active_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. Inputs: robot_ids |
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. Inputs: block_id, robot_id |
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. Inputs: robot_id |
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. Inputs: robot_id |
software_get_robot_signals | Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested. Inputs: robot_id, include_global |
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. Inputs: robot_id, blocks_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. |
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. Inputs: status, categorie, pays, software_tier, min_score, in_scope_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. Inputs: signal_type, min_severity, block_id, component_type, domain, jurisdiction |
Every block below points at https://mcp.roboselect360.com/mcp. Pick your client and copy.
claude mcp add --transport http roboselect360-independent-humano https://mcp.roboselect360.com/mcp
{
"mcpServers": {
"roboselect360-independent-humano": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.roboselect360.com/mcp"]
}
}
}{
"mcpServers": {
"roboselect360-independent-humano": {
"url": "https://mcp.roboselect360.com/mcp"
}
}
}{
"servers": {
"roboselect360-independent-humano": {
"type": "http",
"url": "https://mcp.roboselect360.com/mcp"
}
}
}{
"context_servers": {
"roboselect360-independent-humano": {
"url": "https://mcp.roboselect360.com/mcp"
}
}
}{
"mcpServers": {
"roboselect360-independent-humano": {
"serverUrl": "https://mcp.roboselect360.com/mcp"
}
}
}{
"mcpServers": {
"roboselect360-independent-humano": {
"url": "https://mcp.roboselect360.com/mcp"
}
}
}name: RoboSelect360 - Independent Humanoid Robot Intelligence
version: 0.0.1
schema: v1
mcpServers:
- name: RoboSelect360 - Independent Humanoid Robot Intelligence
type: streamable-http
url: https://mcp.roboselect360.com/mcp{
"mcpServers": {
"roboselect360-independent-humano": {
"httpUrl": "https://mcp.roboselect360.com/mcp"
}
}
}{
"mcpServers": {
"roboselect360-independent-humano": {
"type": "http",
"url": "https://mcp.roboselect360.com/mcp"
}
}
}{
"mcpServers": {
"roboselect360-independent-humano": {
"url": "https://mcp.roboselect360.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.roboselect360.com%2Fmcp&type=streamable_http&id=roboselect360-independent-humano&name=RoboSelect360%20-%20Independent%20Humanoid%20Robot%20Intelligence
It answered our last check on 18 October 2026 in 193 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by roboselect360.com and served from mcp.roboselect360.com, the vendor's own domain: https://mcp.roboselect360.com/mcp.
27, as returned by the server's own tools/list on 31 August 2026: hardware_compare_robots, hardware_get_block_analysis, hardware_get_dependency_profile, hardware_get_robot, hardware_get_robot_hardware, hardware_get_robot_signals, hardware_get_system_status, hardware_list_robots, and 19 more.
It answered our last check on 18 October 2026 in 193 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.roboselect360.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.roboselect360. Endpoint host: mcp.roboselect360.com. ARD identifier: urn:air:com.roboselect360:mcp:humanoid-robots.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.