Skip to content

RoboSelect360 - Independent Humanoid Robot Intelligence MCP server

com.roboselect360/humanoid-robotsroboselect360.comstreamable-httpv1.0.4Scanned

Humanoid robot intelligence: observed capabilities, BOM supply chain, pilot prep. Free and paid.

32 tools: 2 change things and 30 only read.

Tools: 0 delete, 0 irreversible, 2 write, 30 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server can do

The RoboSelect360 - Independent Humanoid Robot Intelligence MCP server is published by roboselect360.com, a domain the MCP Registry verified. It has 32 tools. It can create or change data (2 tools: prepare_pilot and build_pilot_decision_file), but cannot delete data. 30 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

32 tools

Changes things 2Claude Code: ask
  • build_pilot_decision_filePaid follow-up of prepare_pilot.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 robot and per task with every dated observation behind it (failures included, with source, control mode and power), the gaps to close and who can close them, operating conditions and integration, the pilot specification, the questions to ask the manufacturer and the integrator, and the pilot self-assessment grid. Never recommends, ranks or chooses a robot, and computes no cost: the buyer decides. Requires the decision file access right, separate from robot access; without it the call returns a refusal with the link to request it.

    Annotations the server declares

    • title: Pilot decision file (G.R.O.U.N.D., paid)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_pilotGuides a buyer, one question at a time, through the G.R.O.U.N.D.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Stateless: send back the dossier returned by the previous call, with the answer to the question asked; call with no dossier to start. action='sheet' returns the sheet built so far. Never recommends, ranks or names a robot and computes no cost. Free for everyone, no key and no account.

    Annotations the server declares

    • title: Prepare a pilot with G.R.O.U.N.D.
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 30Show 30 read-only tools
  • get_access_manifestWhat 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.No findings

    Why it is in this group

    • The name "get_access_manifest" says "get": a word for reading.
    Description, as the server wrote it
    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 rights by making calls that will be refused.

    Annotations the server declares

    • title: Your access manifest
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_robot_capabilitiesWhat 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 manufa…No findings

    Why it is in this group

    • The name "get_robot_capabilities" says "get": a word for reading.
    Description, as the server wrote it
    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, failures included, with source, conditions and control mode. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

    Annotations the server declares

    • title: Observed capabilities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_robot_supportAfter-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, availab…No findings

    Why it is in this group

    • The name "get_robot_support" says "get": a word for reading.
    Description, as the server wrote it
    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 in Europe, lifecycle, and the open questions to ask before signing. Every fact carries who states it, its evidence level, a verbatim quote and its source; unknowns are listed as unknown with their search date. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

    Annotations the server declares

    • title: After-sales support profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_compare_robotsCompare 2 to 5 robots side by side on semiconductor BOM, metrics, risk and geographic exposure.No findings

    Why it is in this group

    • The name "hardware_compare_robots" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare robots (semiconductor)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_block_analysisAnalyse one functional block of the semiconductor layer, for a single robot at a time.No findings

    Why it is in this group

    • The name "hardware_get_block_analysis" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Block analysis (semiconductor)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_dependency_profileGeopolitical and supply chain dependency analysis for one robot, built on its semiconductor BOM: geographic concentration, single-source exposure, export control.No findings

    Why it is in this group

    • The name "hardware_get_dependency_profile" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Semiconductor dependency profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_robotCommercial profile of one robot (specs, pricing, viability score), plus whether a per-robot semiconductor bill of materials exists for it.No findings

    Why it is in this group

    • The name "hardware_get_robot" says "get": a word for reading.
    Description, as the server wrote it
    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_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.

    Annotations the server declares

    • title: Robot profile (semiconductor coverage)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_robot_hardwareSemiconductor bill of materials for one robot: functional blocks, components, suppliers.No findings

    Why it is in this group

    • The name "hardware_get_robot_hardware" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Semiconductor BOM teardown
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_robot_signalsActive supply chain signals affecting one robot's semiconductor BOM.No findings

    Why it is in this group

    • The name "hardware_get_robot_signals" says "get": a word for reading.
    Description, as the server wrote it
    Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.

    Annotations the server declares

    • title: Robot signals (semiconductor)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_get_system_statusHealth of the SEMICONDUCTOR layer: profiles loaded, semiconductor signal counts, load errors.No findings

    Why it is in this group

    • The name "hardware_get_system_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Semiconductor layer status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_list_robotsList the robot catalogue with filters, including semiconductor-layer scope and payload.No findings

    Why it is in this group

    • The name "hardware_list_robots" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Robot catalogue (semiconductor filters)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hardware_list_signalsList semiconductor supply chain, performance and operational signals across the panel, with filters.No findings

    Why it is in this group

    • The name "hardware_list_signals" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Signal feed (semiconductor)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_compare_robotsCompare 2 to 5 robots side by side on mechanical BOM, specifications, risk and geographic exposure.No findings

    Why it is in this group

    • The name "mechanical_compare_robots" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare robots (mechanical)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_block_analysisAnalyse one mechanical block (actuation, structure, energy, perception), for a single robot at a time.No findings

    Why it is in this group

    • The name "mechanical_get_block_analysis" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Block analysis (mechanical)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_dependency_profileGeopolitical and supply chain dependency analysis for one robot, built on its mechanical BOM: geographic concentration, critical raw materials, single-source exposure.No findings

    Why it is in this group

    • The name "mechanical_get_dependency_profile" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mechanical dependency profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_robotCommercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status.No findings

    Why it is in this group

    • The name "mechanical_get_robot" says "get": a word for reading.
    Description, as the server wrote it
    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 capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.

    Annotations the server declares

    • title: Robot profile (mechanical coverage)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_robot_mechanicalMechanical bill of materials for one robot: motors, reducers, screws, bearings, batteries, structure, wiring.No findings

    Why it is in this group

    • The name "mechanical_get_robot_mechanical" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mechanical BOM teardown
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_robot_signalsActive supply chain signals affecting one robot's mechanical BOM.No findings

    Why it is in this group

    • The name "mechanical_get_robot_signals" says "get": a word for reading.
    Description, as the server wrote it
    Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.

    Annotations the server declares

    • title: Robot signals (mechanical)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_get_system_statusHealth of the MECHANICAL layer: mechanical profiles loaded, mechanical signal counts, load errors.No findings

    Why it is in this group

    • The name "mechanical_get_system_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mechanical layer status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_list_robotsList the robot catalogue with filters, including mechanical-profile status and payload.No findings

    Why it is in this group

    • The name "mechanical_list_robots" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Robot catalogue (mechanical filters)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • mechanical_list_signalsList mechanical supply chain, performance and operational signals across the panel, with filters.No findings

    Why it is in this group

    • The name "mechanical_list_signals" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Signal feed (mechanical)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_compare_robotsCompare 2 to 5 robots side by side on software BOM, TCO, jurisdiction exposure, lock-in and export control risk.No findings

    Why it is in this group

    • The name "software_compare_robots" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare robots (software)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_block_analysisAnalyse one software block (OS, middleware, runtime, control, fleet), for a single robot at a time.No findings

    Why it is in this group

    • The name "software_get_block_analysis" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Block analysis (software)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_dependency_profileJurisdiction and supply chain dependency analysis for one robot, built on its software stack: jurisdiction concentration, lock-in, export control, cloud dependency.No findings

    Why it is in this group

    • The name "software_get_dependency_profile" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Software dependency profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_robotCommercial profile of one robot (specs, pricing, viability score), plus its software tier and profile status.No findings

    Why it is in this group

    • The name "software_get_robot" says "get": a word for reading.
    Description, as the server wrote it
    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 capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.

    Annotations the server declares

    • title: Robot profile (software coverage)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_robot_signalsActive supply chain signals affecting one robot's software stack.No findings

    Why it is in this group

    • The name "software_get_robot_signals" says "get": a word for reading.
    Description, as the server wrote it
    Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.

    Annotations the server declares

    • title: Robot signals (software)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_robot_softwareSoftware bill of materials for one robot: OS, middleware, AI runtime, motion control, fleet management.No findings

    Why it is in this group

    • The name "software_get_robot_software" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Software BOM teardown
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_get_system_statusHealth of the SOFTWARE layer: software profiles loaded, software signal counts, load errors.No findings

    Why it is in this group

    • The name "software_get_system_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Software layer status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_list_robotsList the robot catalogue with filters, including software tier and software-profile status.No findings

    Why it is in this group

    • The name "software_list_robots" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Robot catalogue (software filters)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • software_list_signalsList software supply chain signals across the panel, with filters.No findings

    Why it is in this group

    • The name "software_list_signals" says "list": a word for reading.
    Description, as the server wrote it
    List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

    Annotations the server declares

    • title: Signal feed (software)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.roboselect360.com/mcp: tools/list returned 32 tools to an anonymous client, including prepare_pilot (write), build_pilot_decision_file (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 0 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 2.View diff
    • Tools that change things, listed without credentials: 0 to 2
  2. Tools2 added, 3 changed.+2 added~3 changedView diff
  3. Tools30 changed.~30 changedView diff

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__humanoid-robots__hardware_get_system_status",
      "mcp__humanoid-robots__hardware_list_robots",
      "mcp__humanoid-robots__hardware_get_robot",
      "mcp__humanoid-robots__hardware_list_signals",
      "mcp__humanoid-robots__hardware_get_robot_signals",
      "mcp__humanoid-robots__hardware_get_block_analysis",
      "mcp__humanoid-robots__hardware_compare_robots",
      "mcp__humanoid-robots__hardware_get_dependency_profile",
      "mcp__humanoid-robots__hardware_get_robot_hardware",
      "mcp__humanoid-robots__mechanical_get_system_status",
      "mcp__humanoid-robots__mechanical_list_robots",
      "mcp__humanoid-robots__mechanical_get_robot",
      "mcp__humanoid-robots__mechanical_list_signals",
      "mcp__humanoid-robots__mechanical_get_robot_signals",
      "mcp__humanoid-robots__mechanical_get_block_analysis",
      "mcp__humanoid-robots__mechanical_compare_robots",
      "mcp__humanoid-robots__mechanical_get_dependency_profile",
      "mcp__humanoid-robots__mechanical_get_robot_mechanical",
      "mcp__humanoid-robots__software_get_system_status",
      "mcp__humanoid-robots__software_list_robots",
      "mcp__humanoid-robots__software_get_robot",
      "mcp__humanoid-robots__software_list_signals",
      "mcp__humanoid-robots__software_get_robot_signals",
      "mcp__humanoid-robots__software_get_block_analysis",
      "mcp__humanoid-robots__software_compare_robots",
      "mcp__humanoid-robots__software_get_dependency_profile",
      "mcp__humanoid-robots__software_get_robot_software",
      "mcp__humanoid-robots__get_access_manifest",
      "mcp__humanoid-robots__get_robot_capabilities",
      "mcp__humanoid-robots__get_robot_support"
    ],
    "ask": [
      "mcp__humanoid-robots__prepare_pilot",
      "mcp__humanoid-robots__build_pilot_decision_file"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as humanoid-robots. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.roboselect360/humanoid-robots/verify?hash=745ff195a8de19c023c6dc9aeb1fa1fb7a818cca636c50494f826ae6792b9722" | jq -e '.changed == false'

Pinned hash 745ff195a8de, from Nov 9, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.roboselect360/humanoid-robots/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.roboselect360/humanoid-robots
[![Anlyon Radar](https://radar.anlyon.com/badge/com.roboselect360/humanoid-robots.svg)](https://radar.anlyon.com/servers/com.roboselect360/humanoid-robots)

Source: MCP Registry · repository. Synced Nov 9, 2026, 16:17 UTC.

RoboSelect360 - Independent Humanoid Robot Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server safe?

No scan can promise that. What its definitions show: 32 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server have?

32 tools: 2 write, 30 read. prepare_pilot, build_pilot_decision_file, hardware_get_system_status, hardware_list_robots, hardware_get_robot, hardware_list_signals, hardware_get_robot_signals, hardware_get_block_analysis and 24 more.

Does the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RoboSelect360 - Independent Humanoid Robot Intelligence MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.