Skip to content
External endpointresponds

Zhihuo RotoSpider Layout

Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.

Endpoint URL
https://mcp.zhihuo.net/roto/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:09 AM UTC
Check
MCP initialize · 8s limit
Latency
579 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
net.zhihuo.mcp/rotospider-layout

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
rotospider_mcp
Version
1.2.0
Capability keys
experimental, prompts, resources, tools
Tool names
check_mold_layout, send_feedback
Instructions excerpt

RotoSpider Layout: check whether a set of rotational-molding molds can be mounted together on a machine arm/spider, using the real RotoSpider geometric layout engine (rotation envelope, dead height, mold-to-mold clearance, offset-arm risers, ring arrangements) - the engine behind https://www.rotospider.com/. Use `check_mold_layout` for any 'can these molds share an arm / which machine takes this mold / how many fit on the spider' question. Each mold is length_mm+width_mm+height_mm (box/frame), diameter_mm+height_mm (cylinder/tank), or an exact published shape with length_mm, width_mm, height_mm, geometry_asset_id, and geometry_asset_revision. The equivalent explicit *_in fields accept decimal inches. Never mix the _mm and _in alias for one value. Pass `machine` (public-sample straight-arm presets: VI-3-1500 (sample geometry), VI-3-2500 (sample geometry), Duroline (sample geometry), CS-10000 (sample geometry), CS-25000 (sample geometry)) or pass NO machine to scan all presets and learn

Reported Aug 17, 2026, 05:09 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 738ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 776ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 529ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 579ms