Skip to content

RotoSpider Layout MCP server

com.cuberithm.mcp/rotospider-layoutmcp.cuberithm.comstreamable-httpv2.0.0Scanned

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

2 tools: 1 do something that can't be undone and 1 change things.

Tools: 0 delete, 1 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RotoSpider Layout MCP server can do

The RotoSpider Layout MCP server is published by mcp.cuberithm.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (1 tool: check_mold_layout), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (send_feedback).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 2.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Can't be undone 1Claude Code: ask
  • send_feedbackRelay a user question, bug report, or suggestion to the maintainers.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send feedback to the RotoSpider maintainers
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 1Claude Code: ask
  • check_mold_layoutCheck whether molds fit together on a rotational-molding machine arm.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 4,022 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...hieved clearance, and the engine's reason when molds do not fit."

      What this check looks for
    Description, as the server wrote it
    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). 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 - horizontal usable envelope diameter after side trim (defaults to envelope). riser_heights_mm: Custom offset arm - available riser heights; the solver picks the best (or none). *_in: Decimal-inch aliases for the matching custom-arm and clearance *_mm arguments. max_load_weight_kg: Optional arm weight capacity; the solver loads molds only up to this total weight. clearance_target_mm: Target mold-to-mold clearance (default 300). clearance_min_mm: Minimum acceptable clearance (default 150). allow_overhang_within_envelope: Allow every mold shape to extend past the spider edge while its complete active shape remains inside the rotation envelope. Defaults to false. include_layout: Include request-relative mold placements. Use with response_api v1/v2/v3 to select the placement heading dialect. display_unit: 'mm' (default) or 'in'. Canonical result fields remain millimetres; 'in' adds a display projection rounded to 0.00001 in. response_api: Public placement dialect. Defaults to rotospider.layout-check.v1; request rotospider.layout-check.v2 for exact four-heading orient keys when layouts are included. Returns a summary sentence plus per-arm results: feasible, placed vs requested counts (per mold type when available), selected riser height, spider utilization, center-of-gravity offset, achieved clearance, and the engine's reason when molds do not fit.

    Annotations the server declares

    • title: Check mold layout on a rotomolding machine arm
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.cuberithm.com/roto/mcp: tools/list returned 2 tools to an anonymous client, including send_feedback (irreversible), check_mold_layout (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 4,022 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...hieved clearance, and the engine's reason when molds do not fit."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__rotospider-layout__check_mold_layout",
      "mcp__rotospider-layout__send_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rotospider-layout. Review it before you use it.

Capability tags behind 1 rule
  • mcp__rotospider-layout__send_feedback outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.cuberithm.mcp/rotospider-layout/verify?hash=d3a98661340814f3efe3f585a06a96757382f35cb5b52b7f204a02155d3c0f73" | jq -e '.changed == false'

Pinned hash d3a986613408, from Nov 13, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.cuberithm.mcp/rotospider-layout/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.cuberithm.mcp/rotospider-layout
[![Anlyon Radar](https://radar.anlyon.com/badge/com.cuberithm.mcp/rotospider-layout.svg)](https://radar.anlyon.com/servers/com.cuberithm.mcp/rotospider-layout)

Source: MCP Registry. Synced Oct 21, 2026, 17:53 UTC.

RotoSpider Layout MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RotoSpider Layout MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RotoSpider Layout MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RotoSpider Layout MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the RotoSpider Layout MCP server have?

2 tools: 1 irreversible, 1 write. send_feedback and check_mold_layout.

Does the RotoSpider Layout MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RotoSpider Layout MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the RotoSpider Layout MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.