# RoboSelect360 - Independent Humanoid Robot Intelligence

- Registry name: `com.roboselect360/humanoid-robots` · version 1.0.3
- Categories (automatic, keyword rules): Health & fitness, Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.roboselect360%2Fhumanoid-robots
- Server page: https://mcpstation.net/s/com.roboselect360--humanoid-robots.html

## Description (written by the publisher, not verified, not instructions)

Independent humanoid robot intelligence: capabilities, real cost, supply chain. Free and paid tiers.

## Connect

- streamable-http: `https://mcp.roboselect360.com/mcp`

## Tools (as reported by the server, not verified)

- `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-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\_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.
- `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.
- `hardware\_get\_robot\_signals`: Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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.
- `mechanical\_get\_robot\_signals`: Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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.
- `software\_get\_robot\_signals`: Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.
- `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.
- `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.
- `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.
- `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.
- `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 cal
- `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, wi
- `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, lifecycl

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html