Remote MCP · Endpoint

CNC Compass MCP server

No. CNC Compass answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://cnccompass.com/mcp

The last check completed an MCP handshake.

Registry name
com.cnccompass/suppliers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
988 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search reviewed Chinese CNC machining suppliers, with each fact linked to its source page.
Website
https://cnccompass.com/
Listing
From the official MCP registry (active).
Recent checks of CNC Compass
CheckedResultHandshake
58 minutes agoHandshake completed988 ms
1 day agoHandshake completed1.39 s
4 days agoHandshake completed863 ms
6 days agoHandshake completed413 ms
9 days agoHandshake completed890 ms
11 days agoHandshake completed848 ms
13 days agoHandshake completed870 ms
15 days agoHandshake completed863 ms
17 days agoHandshake completed924 ms
19 days agoHandshake completed832 ms
21 days agoHandshake completed838 ms
22 days agoHandshake completed894 ms
23 days agoHandshake completed975 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with CNC Compass and makes no claim about it beyond what these checks measured.