Zhihuo RotoSpider Layout
REMOTE · MCP.ZHIHUO.NET · SCANNED AUG 4
Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
Available components
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 →
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 2 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 Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1123 tokens (~561/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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.zhihuo.net
claude mcp add --transport http net-zhihuo-mcp-rotospider-layout https://mcp.zhihuo.net/roto/mcp
[mcp_servers.net-zhihuo-mcp-rotospider-layout] url = "https://mcp.zhihuo.net/roto/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-zhihuo-mcp-rotospider-layout": {
"type": "remote",
"url": "https://mcp.zhihuo.net/roto/mcp",
"enabled": true
}
}
} openclaw mcp add net-zhihuo-mcp-rotospider-layout --url https://mcp.zhihuo.net/roto/mcp --transport streamable-http
mcp_servers:
net-zhihuo-mcp-rotospider-layout:
url: "https://mcp.zhihuo.net/roto/mcp" {
"mcpServers": {
"net-zhihuo-mcp-rotospider-layout": {
"type": "http",
"url": "https://mcp.zhihuo.net/roto/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: Zhihuo RotoSpider Layout → rotospider_mcp security
- 2 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_mold_layout” rewrote its description, which is the text the model reads security
- Server version: 1.0.5 → 1.0.6 functional
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 52
First indexed and scored.
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 4 Aug 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 | 13 Jun 2026 | 11 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 51a77d6ec339910d9bca78337513c3c9b64 |
| 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 |
DNSSEC insecure
Validation of mcp.zhihuo.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| zhihuo.net. | absent | 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 |
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.
check_mold_layout ~788
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}. 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). 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). dead_height_mm: Custom straight arm - unusable center height between the upper and lower spider surfaces. offset_spider_y_mm: Custom offset arm - spider Y offset from the spider center to the sphere center (required for custom offset). offset_horz_diameter_mm: Custom offset arm -…
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — | — |
| 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 | — | — | — |
| 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.