Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
RoboSelect360 - Humanoid Robot Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
29
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http roboselect360-humanoid-robot-intelligence-mcp https://mcp-free.roboselect360.com/mcp
# 2 — ask your agent for something these tools do
# hardware_get_system_status, hardware_list_robots, hardware_get_robot and 26 more
RoboSelect360 - Humanoid Robot Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ROAll 1 server
roboselect3601 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http roboselect360-humanoid-robot-intelligence-mcp https://mcp-free.roboselect360.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_status | string | no | — |
| categorie | string | no | — |
| pays | string | no | — |
| min_payload | number | no | — |
| min_score | integer | no | — |
| in_scope_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signal_type | string | no | — |
| min_severity | string | no | — |
| block_id | string | no | — |
| component_type | string | no | — |
| region | string | no | — |
| layer | string | no | — |
| active_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| include_global | boolean | no | — |
| layer | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_id | string | yes | — |
| robot_id | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_ids | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| blocks_only | boolean | no | — |
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| categorie | string | no | — |
| pays | string | no | — |
| min_payload | number | no | — |
| min_score | integer | no | — |
| in_scope_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signal_type | string | no | — |
| min_severity | string | no | — |
| block_id | string | no | — |
| component_type | string | no | — |
| region | string | no | — |
| active_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| include_global | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_id | string | yes | — |
| robot_id | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_ids | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| blocks_only | boolean | no | — |
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| categorie | string | no | — |
| pays | string | no | — |
| software_tier | string | no | — |
| min_score | integer | no | — |
| in_scope_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signal_type | string | no | — |
| min_severity | string | no | — |
| block_id | string | no | — |
| component_type | string | no | — |
| domain | string | no | — |
| jurisdiction | string | no | — |
| active_only | boolean | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| include_global | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| block_id | string | yes | — |
| robot_id | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_ids | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
| blocks_only | boolean | no | — |
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 parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot_id | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RoboSelect360 - Humanoid Robot Intelligence or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
1.0.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RoboSelect360 - Humanoid Robot Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.