RoboSelect360 - Humanoid Robot Intelligence MCP Server

by roboselect360 Your server? Claim it

answering

RoboSelect360 - Humanoid Robot Intelligence is answering right now. Last checked 13 min ago. It exposes 28 tools.

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

Uptime history 52 days of history · worst day 95%

52 days agonow

94.5%

Uptime 24h

86 of 91 checks

Tools

read from the server

263 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 49

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 August 2026. No other catalogue keeps this.

21 Sep 2 tool descriptions were rewritten hardware_get_robot, hardware_list_robots

21 Sep a tool changed the parameters it asks for hardware_list_robots

3 Sep a tool appeared get_access_manifest

19 Aug 18 tool descriptions were rewritten hardware_compare_robots, hardware_get_block_analysis, hardware_get_dependency_profile and 15 more

18 Aug 18 tools appeared hardware_compare_robots, hardware_get_block_analysis, hardware_get_dependency_profile and 15 more

15 Aug 9 tool descriptions were rewritten hardware_get_robot, hardware_get_system_status, hardware_list_robots and 6 more

RoboSelect360 - Humanoid Robot Intelligence does not always answer

Over the last week it answered 98.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.humanoid-robots]
url = "https://mcp-free.roboselect360.com/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 28

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hardware

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

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.

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.

hardware_get_robot_signals

Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.

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_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.

mechanical

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

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.

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.

mechanical_get_robot_signals

Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.

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_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.

software

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

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.

software_get_robot_signals

Active supply chain signals affecting one robot's software stack. 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.

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_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.

access

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 rights by making calls that will be refused.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp-free.roboselect360.com/mcp	streamable-http	answering	227 ms	13 min ago

Alternatives to RoboSelect360 - Humanoid Robot Intelligence

same job, measured the same way

Santiment

by santiment

Crypto market intelligence: social sentiment, on-chain, trending narratives & analyst insights.

8 tools answering

Kresmion

by kresmion

Prediction markets, on-chain flows, ETF flows, equities and macro intelligence for AI agents.

answering

Cryptodata MCP

by kota1026

CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence...

26 installs/wk local only

Instinct

by mspmcp

MSP market intelligence for AI assistants: profiles, tech, maturity scores, and change signals.

answering

Competitive Intelligence

by atul0016

Competitive pricing, ads, SEO moves, launches, reviews, and daily market briefs.

35 installs/wk local only

HostingBrain Intelligence

by hostingbrain

Market research on European hosting and domains: ownership, structure, pricing, technology adoption.

35 tools answering

Fia Signals MCP

by odds7

Crypto market intelligence: regime detection, funding rates, liquidations, prices, signals.

8 tools answering

Noesis — Solana On-Chain Intelligence

by rengon0x

Solana on-chain intelligence — token scans, wallet profiling, bundle detection, 19 MCP tools.

answering

RoboSelect360 - Humanoid Robot Intelligence — questions

Answers built from our own checks of this server.

What can RoboSelect360 - Humanoid Robot Intelligence do?

It exposes 28 tools, read directly from the server on our last check. Among them: get_access_manifest, hardware_compare_robots, hardware_get_block_analysis, hardware_get_dependency_profile, hardware_get_robot, hardware_get_robot_hardware and 22 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is RoboSelect360 - Humanoid Robot Intelligence mostly used for?

Its tools cluster around hardware, mechanical and software. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is RoboSelect360 - Humanoid Robot Intelligence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 86 of 91 checks got a reply (94.5%), average response time 263 ms. The bar chart above shows every period we have measured.

How do I connect RoboSelect360 - Humanoid Robot Intelligence?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RoboSelect360 - Humanoid Robot Intelligence need an API key?

No. RoboSelect360 - Humanoid Robot Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 28 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RoboSelect360 - Humanoid Robot Intelligence?

It answers our handshake in 263 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.