mcpbeat Sign in

RotoSpider Layout MCP Server

answering

RotoSpider Layout is answering right now. Last checked 11 min ago. It exposes 2 tools.

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

Uptime history 15 days of history · worst day 99%
15 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
712 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 October 2026. No other catalogue keeps this.

27 Oct a tool description was rewritten check_mold_layout
27 Oct a tool changed the parameters it asks for check_mold_layout
27 Oct a tool changed version

RotoSpider Layout missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add rotospider-layout --transport http https://mcp.cuberithm.com/roto/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.cuberithm.com/roto/mcp
~/.codex/config.toml
[mcp_servers.rotospider-layout]
url = "https://mcp.cuberithm.com/roto/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "rotospider-layout": {
      "url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "rotospider-layout": {
      "type": "http",
      "url": "https://mcp.cuberithm.com/roto/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mold
check_mold_layout
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.
send
send_feedback
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.cuberithm.com/roto/mcp streamable-http answering 666 ms 11 min ago

Alternatives to RotoSpider Layout

same job, measured the same way
Fourward AI visibility tools
by fourwardhq

Score any website's AI search visibility out of 100 and see which of 20 AI crawlers can read it.

2 tools answering
MaxAEO AI Visibility MCP
by maxaeo

Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

71 installs/wk local only
A
AI Visibility Audit — Can AI crawlers read and cite your site?
by rowb-ai-visibility

One-call audit: robots.txt AI-bot rules, llms.txt, JSON-LD, meta tags, sitemap. Score plus fixes.

1 tools answering
Alice
by tranx

Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.

2 tools answering
GMaps Lead Finder
by gmapsleadfinder

Scrape Google Maps business leads, reviews, and photos via hosted Remote MCP.

10 tools answering
OSINT Toolbox
by renkagod

Run Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more OSINT tools locally

185 installs/wk local only
Litescrape
by litescrape

Google, Bing, DuckDuckGo and Google Maps search results, free without an API key.

112 installs/wk 6 tools answering
MCP Gtm Tech Stack Signal Scraper
by mambabuilt

Detects a company CRM, sequencer, and marketing automation from its public website. Clay-ready.

129 installs/wk local only

RotoSpider Layout — questions

Answers built from our own checks of this server.

What can RotoSpider Layout do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_mold_layout, send_feedback. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is RotoSpider Layout working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 712 ms. The bar chart above shows every period we have measured.
How do I connect RotoSpider Layout?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does RotoSpider Layout need an API key?
No. RotoSpider Layout completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is RotoSpider Layout?
It answers our handshake in 712 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.