Remote MCP · Endpoint

Sandboxd Code Run MCP server

Yes, as of 1 hour ago: the hostname does not resolve.

DownLast checked 1 hour ago

Server URL

https://sandboxd-code-run.saastemly.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.saastemly/sandboxd-code-run
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
78.6% from 14 checks
Described by its publisher as
Hosted one-shot code execution: send a snippet plus optional files, get stdout, stderr, exit...
Listing
From the official MCP registry (active).
Recent checks of Sandboxd Code Run
CheckedResultHandshake
1 hour agoFailed - the hostname does not resolve—
2 days agoFailed - the hostname does not resolve—
4 days agoFailed - the hostname does not resolve—
7 days agoHandshake completed71 ms
9 days agoHandshake completed86 ms
11 days agoHandshake completed56 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed52 ms
16 days agoHandshake completed192 ms
18 days agoHandshake completed261 ms
19 days agoHandshake completed291 ms
20 days agoHandshake completed52 ms
23 days agoHandshake completed50 ms
24 days agoHandshake completed112 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 Sandboxd Code Run and makes no claim about it beyond what these checks measured.