Remote MCP · Endpoint

RotoSpider Layout MCP server

No. RotoSpider Layout answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://mcp.cuberithm.com/roto/mcp

The last check completed an MCP handshake.

Registry name
com.cuberithm.mcp/rotospider-layout
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
669 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
Listing
From the official MCP registry (active).
Recent checks of RotoSpider Layout
CheckedResultHandshake
57 minutes agoHandshake completed669 ms
3 days agoHandshake completed666 ms
12 days agoHandshake completed635 ms
13 days agoHandshake completed637 ms
15 days agoHandshake completed635 ms
15 days agoHandshake completed637 ms
17 days agoHandshake completed642 ms
18 days agoHandshake completed684 ms
18 days agoHandshake completed651 ms
20 days agoHandshake completed725 ms
22 days agoHandshake completed628 ms
25 days agoHandshake completed763 ms
27 days agoHandshake completed641 ms
29 days agoHandshake completed650 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with RotoSpider Layout and makes no claim about it beyond what these checks measured.