Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.zhihuo.net/roto/mcp2 tools · 1608mscheck_mold_layoutCheck whether molds fit together on a rotational-molding machine arm.
Every answer comes from the deterministic RotoSpider geometric layout
engine: rotation-envelope and dead-height checks, pairwise mold-to-mold
clearance, offset-arm riser selection, and ring arrangements for 3+
identical mold…Check whether molds fit together on a rotational-molding machine arm. Every answer comes from the deterministic RotoSpider geometric layout engine: rotation-envelope and dead-height checks, pairwise mold-to-mold clearance, offset-arm riser selection, and ring arrangements for 3+ identical mold…
| Parameter | Type | Description |
|---|---|---|
| molds* | array | — |
| machine | string | — |
| arm_type | string | — |
| spider_diameter_mm | — | — |
| envelope_diameter_mm | — | — |
| dead_height_mm | — | — |
| offset_spider_y_mm | — | — |
| offset_horz_diameter_mm | — | — |
| riser_heights_mm | — | — |
| spider_diameter_in | — | — |
| envelope_diameter_in | — | — |
| dead_height_in | — | — |
| offset_spider_y_in | — | — |
| offset_horz_diameter_in | — | — |
| riser_heights_in | — | — |
| max_load_weight_kg | number | — |
| clearance_target_mm | — | — |
| clearance_min_mm | — | — |
| allow_overhang_within_envelope | boolean | — |
| include_layout | boolean | — |
| clearance_target_in | — | — |
| clearance_min_in | — | — |
| display_unit | string | — |
| response_api | string | — |
send_feedbackRelay a user question, bug report, or suggestion to the maintainers.
Args:
message: The user's feedback text (required).
contact: Optional reply address the user volunteers.Relay a user question, bug report, or suggestion to the maintainers. Args: message: The user's feedback text (required). contact: Optional reply address the user volunteers.
| Parameter | Type | Description |
|---|---|---|
| message* | string | — |
| contact | string | — |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.