Zhihuo RotoSpider Layout
REMOTE · MCP.ZHIHUO.NET
Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
Available components
Last scanned (22 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Moved to com.cuberithm.mcp/rotospider-layout at https://mcp.cuberithm.com/roto/mcp (RotoSpider Layout). This address keeps working.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1348 tokens (~674/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Oct 26 0
- Tool “check_mold_layout” rewrote its description, which is the text the model reads security
- Server version: 2.0.0 → 1.2.1 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Tool “check_mold_layout” rewrote its description, which is the text the model reads security
- Server version: 1.2.1 → 2.0.0 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- Server version: 1.2.0 → 1.2.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.zhihuo.net/roto/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.zhihuo.net | CN=YE2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 652d79865f6b5849f2560849105ff0a8744 |
| SANs: mcp.zhihuo.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zhihuo.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| zhihuo.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zhihuo.net/roto/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zhihuo.net/roto/mcp | HTTPS enforced | 308 | https://mcp.zhihuo.net/roto/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_mold_layout ~990
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 molds. It never returns a physically invalid layout. Args: molds: List of mold objects. Use one explicit unit convention: Box/frame mold: {"length_mm": L, "width_mm": W, "height_mm": H}. Cylinder/tank mold: {"diameter_mm": D, "height_mm": H}. Exact L, slope, triangle, frustum, or complex mold: measured length_mm+width_mm+height_mm plus the complete geometry_asset_id+geometry_asset_revision returned by the geometry WebAPI or another trusted publisher. Decimal-inch aliases are length_in, width_in, height_in, and diameter_in. Each value is converted once to canonical micrometres; do not give both aliases for the same value. Optional per mold: "name", "weight_kg", "quantity" (default 1; use 0 to retain the mold type without requesting a copy). machine: Public-sample straight-arm preset. Available models are listed in the tool description. Leave empty AND give no explicit geometry to scan all presets ("which machine can take these molds?"). arm_type: 'straight' (dual spiders) or 'offset' (single-spider offset/L arm). Empty = both. spider_diameter_mm: Custom machine - spider (mounting plate) diameter. Giving this plus envelope_diameter_mm switches to custom-machine mode instead of presets. envelope_diameter_mm: Custom machine - rotation envelope diameter (for offset arms: the vertical envelope diameter).…
| Name | Type | Req | Description |
|---|---|---|---|
| allow_overhang_within_envelope | boolean | – | – |
| arm_type | string | – | – |
| clearance_min_in | – | – | – |
| clearance_min_mm | – | – | – |
| clearance_target_in | – | – | – |
| clearance_target_mm | – | – | – |
| dead_height_in | – | – | – |
| dead_height_mm | – | – | – |
| display_unit | string | – | – |
| envelope_diameter_in | – | – | – |
| envelope_diameter_mm | – | – | – |
| include_layout | boolean | – | – |
| machine | string | – | – |
| max_load_weight_kg | number | – | – |
| molds | array | yes | – |
| offset_horz_diameter_in | – | – | – |
| offset_horz_diameter_mm | – | – | – |
| offset_spider_y_in | – | – | – |
| offset_spider_y_mm | – | – | – |
| response_api | string | – | – |
| riser_heights_in | – | – | – |
| riser_heights_mm | – | – | – |
| spider_diameter_in | – | – | – |
| spider_diameter_mm | – | – | – |
No output schema declared.
No examples provided.
send_feedback ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Zhihuo RotoSpider Layout MCP server?
Zhihuo RotoSpider Layout is a hosted endpoint at https://mcp.zhihuo.net/roto/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.zhihuo.net
claude mcp add --transport http net-zhihuo-mcp-rotospider-layout 'https://mcp.zhihuo.net/roto/mcp'
What is the Zhihuo RotoSpider Layout MCP server?
Zhihuo RotoSpider Layout is an MCP server listed in the public MCP registry as net.zhihuo.mcp/rotospider-layout. Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how. This page covers its hosted endpoint (https://mcp.zhihuo.net/roto/mcp).
Is the Zhihuo RotoSpider Layout MCP server safe to use?
Zhihuo RotoSpider Layout scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zhihuo RotoSpider Layout MCP server expose?
Zhihuo RotoSpider Layout exposes 2 tools: check_mold_layout, send_feedback. Their descriptions and schemas cost roughly 1,051 tokens of context every time the server is loaded.
Does the Zhihuo RotoSpider Layout MCP server require authentication?
No. We connected to Zhihuo RotoSpider Layout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zhihuo RotoSpider Layout MCP server still maintained?
Zhihuo RotoSpider Layout is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Zhihuo RotoSpider Layout MCP server?
VerifyMCP ran 12 checks on Zhihuo RotoSpider Layout, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Zhihuo RotoSpider Layout: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.