Remote MCP · Endpoint

AI3D Studio MCP server

No. AI3D Studio answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ai3d.studio/mcp

The last check completed an MCP handshake.

Registry name
studio.ai3d/ai3d-studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
612 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Generate 3D models from images or text with AI, then retexture or convert them to STL, 3MF or OBJ.
Listing
From the official MCP registry (active).
Recent checks of AI3D Studio
CheckedResultHandshake
1 hour agoHandshake completed612 ms
1 day agoHandshake completed1.44 s
2 days agoHandshake completed385 ms
2 days agoHandshake completed622 ms
4 days agoHandshake completed1.99 s
7 days agoHandshake completed607 ms
9 days agoHandshake completed278 ms
12 days agoHandshake completed435 ms
14 days agoHandshake completed1.65 s
16 days agoHandshake completed1.67 s
18 days agoHandshake completed2.87 s
20 days agoHandshake completed2.28 s
22 days agoHandshake completed1.57 s
24 days agoHandshake completed941 ms
25 days agoHandshake completed158 ms

The last 15 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 AI3D Studio and makes no claim about it beyond what these checks measured.