roboselect360
https://mcp.roboselect360.com/mcp ↗
Description
The independent teardown of the humanoid robot market: robots scored on viability, specs and pricing, down to hardware/mechanical/software BOMs and geopolitical supply-chain risk (rare earths, single-source chips). public tier: catalogue & profiles; deep BOM/risk on premium
What our measurements say
roboselect360 is a remote MCP server published at mcp.roboselect360.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 298 ms, placing it among the faster endpoints. It exposes a broad tool surface of 28 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Layer-specific naming (hardware/mechanical/software) enables precise tool selection.
- Descriptions explicitly state access rights requirements and use cases.
- Consistent structure across tools (e.g., _list_robots, _get_robot) aids pattern recognition.
Weaknesses
- Parameter schemas are not explicitly defined in descriptions.
- Some tools have overlapping functionality across layers (e.g., compare_robots variants).
- Technical jargon in descriptions (e.g., 'layer flag') may hinder agent understanding.
hardware_get_robot— Ambiguous 'layer flag' reference without contextmechanical_compare_robots— Redundant 'requires access on EVERY robot' phrasingsoftware_get_block_analysis— Unclear 'robot named' vs 'none' conditionget_access_manifest— Truncated description cuts off critical info
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · system moved to legacy mode with compliance score initialized
- 2026-09-11T07:35:54.413Z — complianceScore set to 100 · full compliance achieved in legacy era
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 74ms → warm 90ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.28.1
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/nicolas-grunder1-roboselect360)<a href="https://mcpmetrics.io/servers/nicolas-grunder1-roboselect360"><img src="https://mcpmetrics.io/badge/nicolas-grunder1/roboselect360/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see