accueil / serveurs / Géo & Temps / com.roboselect360/humanoid-robots
com.roboselect360/humanoid-robots
serveur MCP (Model Context Protocol) · RoboSelect360 1.30.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.roboselect360/humanoid-robots est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.roboselect360/humanoid-robots » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 29 outils
- get_access_manifest≈ 154 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_access_manifest", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_robot_capabilities≈ 205 tokens
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 the call returns a refusal naming that robot.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "get_robot_capabilities", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_compare_robots≈ 150 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_ids· string · requis
Exemple d'appel{"name": "hardware_compare_robots", "arguments": {"robot_ids": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_block_analysis≈ 156 tokens
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.
Paramètres, retour & exemple (2)
Paramètresblock_id· string · requisrobot_id· string · optionnel
Exemple d'appel{"name": "hardware_get_block_analysis", "arguments": {"block_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_dependency_profile≈ 151 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "hardware_get_dependency_profile", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_robot≈ 155 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "hardware_get_robot", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_robot_hardware≈ 163 tokens
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.
Paramètres, retour & exemple (2)
Paramètresrobot_id· string · requisblocks_only· boolean · optionnel
Exemple d'appel{"name": "hardware_get_robot_hardware", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_robot_signals≈ 161 tokens
Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.
Paramètres, retour & exemple (3)
Paramètreslayer· string · optionnelrobot_id· string · requisinclude_global· boolean · optionnel
Exemple d'appel{"name": "hardware_get_robot_signals", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_get_system_status≈ 120 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "hardware_get_system_status", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_list_robots≈ 280 tokens
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.
Paramètres, retour & exemple (8)
Paramètrespays· string · optionnellimit· integer · optionneloffset· integer · optionnelcategorie· string · optionnelmin_score· integer · optionnelmin_payload· number · optionnelscope_status· string · optionnelin_scope_only· boolean · optionnel
Exemple d'appel{"name": "hardware_list_robots", "arguments": {"pays": "texte", "limit": 1, "offset": 1, "categorie": "texte", "min_score": 1, "min_payload": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - hardware_list_signals≈ 273 tokens
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.
Paramètres, retour & exemple (9)
Paramètreslayer· string · optionnellimit· integer · optionneloffset· integer · optionnelregion· string · optionnelblock_id· string · optionnelactive_only· boolean · optionnelsignal_type· string · optionnelmin_severity· string · optionnelcomponent_type· string · optionnel
Exemple d'appel{"name": "hardware_list_signals", "arguments": {"layer": "texte", "limit": 1, "offset": 1, "region": "texte", "block_id": "texte", "active_only": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_compare_robots≈ 151 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_ids· string · requis
Exemple d'appel{"name": "mechanical_compare_robots", "arguments": {"robot_ids": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_block_analysis≈ 159 tokens
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.
Paramètres, retour & exemple (2)
Paramètresblock_id· string · requisrobot_id· string · optionnel
Exemple d'appel{"name": "mechanical_get_block_analysis", "arguments": {"block_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_dependency_profile≈ 152 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "mechanical_get_dependency_profile", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_robot≈ 146 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "mechanical_get_robot", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_robot_mechanical≈ 169 tokens
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.
Paramètres, retour & exemple (2)
Paramètresrobot_id· string · requisblocks_only· boolean · optionnel
Exemple d'appel{"name": "mechanical_get_robot_mechanical", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_robot_signals≈ 144 tokens
Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.
Paramètres, retour & exemple (2)
Paramètresrobot_id· string · requisinclude_global· boolean · optionnel
Exemple d'appel{"name": "mechanical_get_robot_signals", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_get_system_status≈ 120 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "mechanical_get_system_status", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_list_robots≈ 267 tokens
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.
Paramètres, retour & exemple (8)
Paramètrespays· string · optionnellimit· integer · optionneloffset· integer · optionnelstatus· string · optionnelcategorie· string · optionnelmin_score· integer · optionnelmin_payload· number · optionnelin_scope_only· boolean · optionnel
Exemple d'appel{"name": "mechanical_list_robots", "arguments": {"pays": "texte", "limit": 1, "offset": 1, "status": "texte", "categorie": "texte", "min_score": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - mechanical_list_signals≈ 257 tokens
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.
Paramètres, retour & exemple (8)
Paramètreslimit· integer · optionneloffset· integer · optionnelregion· string · optionnelblock_id· string · optionnelactive_only· boolean · optionnelsignal_type· string · optionnelmin_severity· string · optionnelcomponent_type· string · optionnel
Exemple d'appel{"name": "mechanical_list_signals", "arguments": {"limit": 1, "offset": 1, "region": "texte", "block_id": "texte", "active_only": true, "signal_type": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_compare_robots≈ 153 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_ids· string · requis
Exemple d'appel{"name": "software_compare_robots", "arguments": {"robot_ids": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_block_analysis≈ 158 tokens
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.
Paramètres, retour & exemple (2)
Paramètresblock_id· string · requisrobot_id· string · optionnel
Exemple d'appel{"name": "software_get_block_analysis", "arguments": {"block_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_dependency_profile≈ 150 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "software_get_dependency_profile", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_robot≈ 147 tokens
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.
Paramètres, retour & exemple (1)
Paramètresrobot_id· string · requis
Exemple d'appel{"name": "software_get_robot", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_robot_signals≈ 143 tokens
Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.
Paramètres, retour & exemple (2)
Paramètresrobot_id· string · requisinclude_global· boolean · optionnel
Exemple d'appel{"name": "software_get_robot_signals", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_robot_software≈ 166 tokens
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.
Paramètres, retour & exemple (2)
Paramètresrobot_id· string · requisblocks_only· boolean · optionnel
Exemple d'appel{"name": "software_get_robot_software", "arguments": {"robot_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_get_system_status≈ 118 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "software_get_system_status", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_list_robots≈ 267 tokens
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.
Paramètres, retour & exemple (8)
Paramètrespays· string · optionnellimit· integer · optionneloffset· integer · optionnelstatus· string · optionnelcategorie· string · optionnelmin_score· integer · optionnelin_scope_only· boolean · optionnelsoftware_tier· string · optionnel
Exemple d'appel{"name": "software_list_robots", "arguments": {"pays": "texte", "limit": 1, "offset": 1, "status": "texte", "categorie": "texte", "min_score": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - software_list_signals≈ 267 tokens
List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.
Paramètres, retour & exemple (9)
Paramètreslimit· integer · optionneldomain· string · optionneloffset· integer · optionnelblock_id· string · optionnelactive_only· boolean · optionnelsignal_type· string · optionneljurisdiction· string · optionnelmin_severity· string · optionnelcomponent_type· string · optionnel
Exemple d'appel{"name": "software_list_signals", "arguments": {"limit": 1, "domain": "texte", "offset": 1, "block_id": "texte", "active_only": true, "signal_type": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».