# com.roboselect360/humanoid-robots

Market & supply-chain intelligence on 34 humanoid robots: scores, specs, pricing. No key.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** com.roboselect360
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp-free.roboselect360.com/mcp
- **Source:** https://mcp-free.roboselect360.com/mcp
- **Endpoint health:** reachable (last checked 2026-09-26T07:36:57.588Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 28 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-07T13:01:27.614Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

28 declared. Observed from a live `tools/list` probe.
- `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 
- `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

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"humanoid-robots\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp-free.roboselect360.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.roboselect360%2Fhumanoid-robots
- Install plan: https://forgeregistry.com/api/v1/packages/com.roboselect360%2Fhumanoid-robots/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.roboselect360%2Fhumanoid-robots
- HTML page: https://forgeregistry.com/registry/com.roboselect360%2Fhumanoid-robots
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.