Remote MCP · Endpoint

CADProps MCP server

No. CADProps answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://www.cadprops.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.cadprops/cadprops
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
233 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fast multi-format CAD previews, geometry checks and conversion; measure and share in the workspace.
Listing
From the official MCP registry (active).
Recent checks of CADProps
CheckedResultHandshake
19 minutes agoHandshake completed233 ms
9 days agoHandshake completed289 ms
9 days agoHandshake completed216 ms
11 days agoHandshake completed255 ms
12 days agoHandshake completed434 ms
13 days agoHandshake completed315 ms
14 days agoHandshake completed198 ms
15 days agoHandshake completed200 ms
16 days agoHandshake completed251 ms
19 days agoHandshake completed247 ms
21 days agoHandshake completed273 ms
24 days agoHandshake completed1.43 s
26 days agoHandshake completed256 ms
28 days agoHandshake completed193 ms

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

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