Remote MCP · Endpoint

ScriptCompiler MCP server

No. ScriptCompiler answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://mcp.scriptcompiler.com/mcp

The last check completed an MCP handshake.

Registry name
com.scriptcompiler/scriptcompiler
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
584 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Create motion and play it on The Handy, Autoblow, VacuGlide, Kiiroo, OSSM and Lovense toys.
Listing
From the official MCP registry (active).
Recent checks of ScriptCompiler
CheckedResultHandshake
37 minutes agoHandshake completed584 ms
3 days agoHandshake completed2.50 s
13 days agoHandshake completed196 ms
13 days agoHandshake completed190 ms
15 days agoHandshake completed224 ms
16 days agoHandshake completed178 ms
17 days agoHandshake completed183 ms
18 days agoHandshake completed71 ms
18 days agoHandshake completed164 ms
20 days agoHandshake completed240 ms
22 days agoHandshake completed159 ms
25 days agoHandshake completed178 ms
27 days agoHandshake completed172 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 ScriptCompiler and makes no claim about it beyond what these checks measured.