Remote MCP · Endpoint

CutOptim Engine MCP server

No. CutOptim Engine answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://api.cutoptim.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cutoptim/engine
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API.
Listing
From the official MCP registry (active).
Recent checks of CutOptim Engine
CheckedResultHandshake
42 minutes agoHandshake completed303 ms
3 days agoHandshake completed317 ms
13 days agoHandshake completed298 ms
13 days agoHandshake completed323 ms
15 days agoHandshake completed299 ms
15 days agoHandshake completed304 ms
17 days agoHandshake completed294 ms
18 days agoHandshake completed293 ms
18 days agoHandshake completed297 ms
20 days agoHandshake completed313 ms
22 days agoHandshake completed593 ms
25 days agoHandshake completed431 ms
27 days agoHandshake completed292 ms

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

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 CutOptim Engine and makes no claim about it beyond what these checks measured.