Remote MCP · Endpoint

OrbitStudio MCP server

No. OrbitStudio answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://orbitstudio-api-597899603925.europe-west1.run.app/mcp?via=mcp

The last check completed an MCP handshake.

Registry name
com.orbitstudio3d/orbitstudio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
514 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find craters, mountains and landing sites on the Moon, Mars and more to 3D print in OrbitStudio.
Listing
From the official MCP registry (active).
Recent checks of OrbitStudio
CheckedResultHandshake
18 minutes agoHandshake completed514 ms
10 days agoHandshake completed502 ms
10 days agoHandshake completed511 ms
11 days agoHandshake completed558 ms
13 days agoHandshake completed501 ms
14 days agoHandshake completed544 ms
14 days agoHandshake completed587 ms
15 days agoHandshake completed549 ms
17 days agoHandshake completed501 ms
19 days agoHandshake completed655 ms
21 days agoHandshake completed548 ms
24 days agoHandshake completed563 ms
26 days agoHandshake completed565 ms
28 days agoHandshake completed549 ms

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

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