Remote MCP · Endpoint

3dCMS MCP server

No. 3dCMS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://3dcms.info/mcp

The last check completed an MCP handshake.

Registry name
info.3dcms/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build a real 3D website by chatting: pages, models and text in space, published to a live URL.
Listing
From the official MCP registry (active).
Recent checks of 3dCMS
CheckedResultHandshake
1 hour agoHandshake completed112 ms
2 days agoHandshake completed1.08 s
4 days agoHandshake completed41 ms
5 days agoHandshake completed75 ms
7 days agoHandshake completed50 ms
8 days agoHandshake completed423 ms
9 days agoHandshake completed47 ms
12 days agoHandshake completed46 ms
13 days agoHandshake completed87 ms
15 days agoHandshake completed56 ms
16 days agoHandshake completed604 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed52 ms
20 days agoHandshake completed60 ms
20 days agoHandshake completed48 ms
21 days agoHandshake completed61 ms
22 days agoHandshake completed210 ms

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

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