RoboSelect360 - Independent Humanoid Robot Intelligence

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

• 接続方法: クラウドで動く
• トランスポート: Streamable HTTP
• カテゴリ: その他
• 入力が必要なもの：X-API-Key

インストール

使っているAIアプリを選んで、設定をコピーしてください。

必要なもの

• クラウドで動くインストール不要。インターネット経由でつながります

どのアプリを使っていますか？

claude mcp add --transport http humanoid-robots https://mcp.roboselect360.com/mcp --header 'X-API-Key: your-value'

{
  "mcpServers": {
    "humanoid-robots": {
      "url": "https://mcp.roboselect360.com/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

{
  "servers": {
    "humanoid-robots": {
      "type": "http",
      "url": "https://mcp.roboselect360.com/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

• X-API-Key 秘密 HTTP header
  Optional RoboSelect360 key. Without it, the free tools are open; with it, the robots you have purchased are unlocked.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが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月10日にチェック

• ✓ 合格

  作者とリポジトリが一致

  レジストリ名はドメイン roboselect360.com で確認済みです（レジストリがドメインの所有を確認しています）

• … 未チェック

  今もメンテナンスされている

  このリポジトリはまだGitHubから読み取っていません

• … 未チェック

  ライセンスがある

  このリポジトリはまだGitHubから読み取っていません

• ✓ 合格

  エンドポイントが応答する

  333ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  32件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

その他のほかのサーバーとの比較i

• このカテゴリのほかの19013件のうち0%よりスターが多い
• このカテゴリのほかの19013件のうち98%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの19013件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

作者のREADME

https://mcp.roboselect360.com/mcp

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