RoboSelect360 - Independent Humanoid Robot Intelligence

安装

选择你使用的 AI 应用，然后复制设置。

通过 4/4 项检查 · 你的提问会经过开发者的服务器（mcp.roboselect360.com） · ✓ 命令已检查 2026年11月13日

claude mcp add --transport http --scope user humanoid-robots https://mcp.roboselect360.com/mcp

{
  "mcpServers": {
    "humanoid-robots": {
      "url": "https://mcp.roboselect360.com/mcp"
    }
  }
}

{
  "servers": {
    "humanoid-robots": {
      "type": "http",
      "url": "https://mcp.roboselect360.com/mcp"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月9日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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 the same server.

• hardware_list_robots

  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.

• hardware_get_robot

  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. Also returns observed_capabiliti

• 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 least one robot.

• 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 when none is.

• 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 missing the call returns a refusal naming it, and compares nothing.

• hardware_get_dependency_profile

  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.

• 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 returns a refusal naming that robot.

• 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, not the same server.

• 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 one, not three. Pick this one to filter on mechanical coverage.

• 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_robot variants - the layer flag is the only difference. Also returns observed_capabilities: the evidence label per capabilit

• 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 least one robot.

• 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 least one robot when none is.

• 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 missing the call returns a refusal naming it, and compares nothing.

• 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 exposure. Requires an access right on the robot requested.

• 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; without it the call returns a refusal naming that robot.

• 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 the same server.

• 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 - call one, not three. Pick this one to filter by software tier.

• 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 get_robot variants - the layer flag is the only difference. Also returns observed_capabilities: the evidence label per ca

• 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 one robot when none is.

• 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; if one is missing the call returns a refusal naming it, and compares nothing.

• 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 dependency. Requires an access right on the robot requested.

• 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 it the call returns a refusal naming that robot.

• 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 can be unlocked. Free for everyone, no key and no account. Call it FIRST: it removes the need to discover your own access

• get_robot_capabilities

  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, f

• get_robot_support

  After-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

• prepare_pilot

  Guides a buyer, one question at a time, through the G.R.O.U.N.D. method to a needs sheet for a first humanoid robot pilot: their need structured, what the market has proven on their task (counted across the panel, no robot named), and the vigilance points their answers trigger. S

• build_pilot_decision_file

  Paid follow-up of prepare_pilot. From the buyer's dossier (as returned by prepare_pilot) and 1 to 5 robots chosen by the buyer (robot_ids, from list_robots), returns the full pre-pilot decision file in markdown: decision memo, the robots' announced facts, an evidence matrix per r

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 roboselect360.com 验证（注册中心会核实域名所有权）

• ✓ 通过

  仍在维护

  代码最后更新于5天前

• – 不适用

  有许可证

  不适用：由 roboselect360.com 的所有者自己运行的云端服务器，你不会运行仓库里的代码

• ✓ 通过

  端点有响应

  在 333 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 32 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 19776 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 19776 个服务器的 89% 更新
• 基础检查结果等于或优于此分类中其他 19776 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

作者：koala73·广泛使用·★ 9.1万·今天更新

在云端运行✓ 服务方 · worldmonitor.app

接入方法

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

作者：ruvnet·广泛使用·↓ 1.4万/周·★ 8.2万·14个月前更新

在你的电脑上运行

安装

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

作者：windmill-labs·广泛使用·★ 1.9万·前天更新

在云端运行

接入方法

作者的 README

https://mcp.roboselect360.com/mcp

npx -y mcp-remote https://mcp.roboselect360.com/mcp