RoboSelect360 - Humanoid Robot Intelligence — MCP server · Wellknown
RoboSelect360 - Humanoid Robot Intelligence
MCP serverMCP
Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key.
by com.roboselect360v1.0.2
Observed by Wellknown
Evidence
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
30-day availability1/1 checks ok
30 days agotoday
Endpoints
https://mcp-free.roboselect360.com/mcpmcp streamable http · checked on a schedule
Registry facts
Not distributed through a package registry we index.
when
check
result
http
latency
detail
4 h ago
mcp initialize
ok
200
67 ms
server RoboSelect360 Global 1.28.1 · protocol 2025-06-18 · 28 tools
Tools observed via MCP handshake
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
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,
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 a
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 l
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 whe
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 missin
hardware_get_dependency_profile — Geopolitical and supply chain dependency analysis for one robot, built on its semiconductor BOM: geographic concentration, single-source exposure, export contro
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 re
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
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
Declared by sources
What the publisher says
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
kind ← Official MCP Registry
name ← Official MCP Registry
summary ← Official MCP Registry
version ← Official MCP Registry
description ← Official MCP Registry
publisherName ← Official MCP Registry
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
6 h ago · declared · summary → "Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key."
6 h ago · declared · description → "Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key."
6 h ago · declared · publisherName → "com.roboselect360"
6 h ago · declared · version → "1.0.2"
6 h ago · declared · protocols → ["mcp"]
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_robo
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 leas
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 lea
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 mi
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 ex
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; w
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
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 -
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 g
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
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;
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 depende
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
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 ca
SvGrid
Live
Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.