Remote MCP · Endpoint

ce-net MCP server

No. ce-net answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://ce-net.com/mcp

The last check completed an MCP handshake.

Registry name
com.ce-net/ce-net
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.45 s
Tools exposed
303 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Connect your AI to your own devices, 3D printers, factory tools and a shared agent task pool.
Listing
From the official MCP registry (active).
Recent checks of ce-net
CheckedResultHandshake
4 hours agoHandshake completed1.45 s
10 days agoHandshake completed834 ms
11 days agoHandshake completed885 ms
11 days agoHandshake completed864 ms
13 days agoHandshake completed888 ms
14 days agoHandshake completed701 ms
15 days agoHandshake completed1.17 s
16 days agoHandshake completed498 ms
17 days agoHandshake completed782 ms
19 days agoHandshake completed584 ms
22 days agoHandshake completed460 ms
24 days agoHandshake completed496 ms
26 days agoHandshake completed494 ms
29 days agoHandshake completed517 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 ce-net and makes no claim about it beyond what these checks measured.