roboselect360

The independent teardown of the humanoid robot market: robots scored on viability, specs and pricing, down to hardware/mechanical/software BOMs and…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

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 se
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 th
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 v

What data it sees

Do you need an account

No: the server works without sign-in

The independent teardown of the humanoid robot market: robots scored on viability, specs and pricing, down to hardware/mechanical/software BOMs and geopolitical supply-chain risk (rare earths, single-source chips). public tier: catalogue & profiles; deep BOM/risk on premium

How to connect

How to connect roboselect360 to Claude

The server address to paste into Claude settings:

https://roboselect360.run.tools

Open Claude (claude.ai or the desktop app).
Go to Settings → Connectors.
Click Add custom connector.
Paste the server address copied below into Remote MCP server URL and click Add.
In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect roboselect360 to ChatGPT

The server address to paste into ChatGPT settings:

https://roboselect360.run.tools

Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
Open Settings → Connectors and click Create.
Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect roboselect360 to Cursor

The server address to paste into Cursor settings:

https://roboselect360.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (9)

Raw names from tools/list. Only developers need these.

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.
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.
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.
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.
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.
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.