# RotoSpider Layout (remote · mcp.cuberithm.com)

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

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mcp.cuberithm.com`: 58/100 (this document), [markdown](https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp.md), [page](https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp)

## Channel facts

- Endpoint: `https://mcp.cuberithm.com/roto/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 52/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1328 tokens (~664/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RotoSpider Layout MCP server?

RotoSpider Layout is a hosted endpoint at https://mcp.cuberithm.com/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.

### Claude

```bash
claude mcp add --transport http com-cuberithm-mcp-rotospider-layout 'https://mcp.cuberithm.com/roto/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cuberithm-mcp-rotospider-layout": {
      "url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cuberithm-mcp-rotospider-layout": {
      "type": "http",
      "url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cuberithm-mcp-rotospider-layout]
url = "https://mcp.cuberithm.com/roto/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cuberithm-mcp-rotospider-layout": {
      "type": "remote",
      "url": "https://mcp.cuberithm.com/roto/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cuberithm-mcp-rotospider-layout --url 'https://mcp.cuberithm.com/roto/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cuberithm-mcp-rotospider-layout:
    url: "https://mcp.cuberithm.com/roto/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cuberithm-mcp-rotospider-layout": {
      "Transport": "http",
      "Url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cuberithm-mcp-rotospider-layout -t streamable-http -u 'https://mcp.cuberithm.com/roto/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cuberithm-mcp-rotospider-layout": {
      "type": "http",
      "url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 57, +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.

### 2026-10-20 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 56)

First indexed and scored.

## MCP tools (2)

### `check_mold_layout` (~970 tokens)

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).…

Input parameters:

- `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, required)
- `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`

### `send_feedback` (~61 tokens)

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.

Input parameters:

- `contact` (string)
- `message` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp#diagnostics

## Score history

- 2026-10-23: 58
- 2026-10-22: 57
- 2026-10-21: 57
- 2026-10-20: 56
- 2026-10-19: 56

## Common questions

### What is the RotoSpider Layout MCP server?

RotoSpider Layout is an MCP server listed in the public MCP registry as com.cuberithm.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.cuberithm.com/roto/mcp).

### Is the RotoSpider Layout MCP server safe to use?

RotoSpider Layout scores 58 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 RotoSpider Layout MCP server expose?

RotoSpider Layout exposes 2 tools: check_mold_layout, send_feedback. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.

### Does the RotoSpider Layout MCP server require authentication?

No. We connected to RotoSpider Layout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RotoSpider Layout MCP server still maintained?

RotoSpider Layout is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.cuberithm.com/roto/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-cuberithm-mcp-rotospider-layout/roto-mcp