Bots St

bots.st/roboselect360-independent-humanoid-robot-intelli

RoboSelect360 - Independent Humanoid Robot Intelligence

Robot capability and hardware supply research

2057 ms

answered our call

State
Answered
Protocol
MCP 2025-06-18
Tools listed
30
Answered
3 of the last 3 calls

How to reach it

  • MCP, HTTPhttps://mcp.roboselect360.com/mcp

What it can do

ToolWhat it says it does
get_access_manifestWhat 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…
get_robot_capabilitiesWhat 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…
get_robot_supportAfter-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…
hardware_compare_robotsCompare 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_block_analysisAnalyse 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_get_dependency_profileGeopolitical 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_robotCommercial 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_get_robot_hardwareSemiconductor 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.
hardware_get_robot_signalsActive supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.
hardware_get_system_statusHealth 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_robotsList 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_list_signalsList 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.
mechanical_compare_robotsCompare 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_block_analysisAnalyse 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_get_dependency_profileGeopolitical 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_robotCommercial 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_get_robot_mechanicalMechanical 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_get_robot_signalsActive supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.
mechanical_get_system_statusHealth 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_robotsList 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_list_signalsList 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.
software_compare_robotsCompare 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_block_analysisAnalyse 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_get_dependency_profileJurisdiction 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_robotCommercial 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_get_robot_signalsActive supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.
software_get_robot_softwareSoftware 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_get_system_statusHealth 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_robotsList 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_list_signalsList software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

In its maker's words

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

Website
roboselect360.com
Publisher
roboselect360.com
Listed from
the official MCP Registry as com.roboselect360/humanoid-robots
Version
1.0.3, updated 15 Oct 2026
Kinds of work
Search and research, Finance and markets, Law, tax and government

The domain it lives on

roboselect360.com
registered 1 Feb 2026 (9 months ago), at OVH sas, its home page is a working site

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

WhenWhat happenedTime
Answered2057 ms
Answered2263 ms
Answered1310 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.