Reference Source · MCP server health

com.roboselect360/humanoid-robots

2 endpoints on the official MCP registry. Probed daily.

https://mcp-free.roboselect360.com/mcp

answered, tools listed

Last 30 probes
Last seen healthy2026-10-15
Completed sessions— of the last 7 probes · 95.5% of the last 30
Handshake latencymedian 409 ms, 95th 460 ms
Tools listed29
Tool contract8c10b279498f — last moved 2026-10-07 (1 added, against 2026-10-06)
Protocol answered2025-06-18
Transportstreamable-http

https://mcp.roboselect360.com/mcp

answered, tools listed

Last 30 probes
Last seen healthy2026-10-23
Completed sessions100% of the last 7 probes · 100% of the last 30
Handshake latencymedian 448 ms, 95th 459 ms
Tools listed30
Tool contract730d5857b4c0 — last moved 2026-10-22 (1 added, against 2026-10-21)
Protocol answered2025-06-18
Transportstreamable-http

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/com-roboselect360-humanoid-robots.svg)](https://referencesource.org/mcp-health/server/com-roboselect360-humanoid-robots/)

The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key. This entry publishes 2 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]