Remote MCP · Endpoint

uxgen MCP server

No. uxgen answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://www.uxgen.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.uxgen/ecommerce-conversion
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.62 s
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ecommerce conversion for coding agents: AOV bundles, cart, upsell, imagery, page audit.
Listing
From the official MCP registry (active).
Recent checks of uxgen
CheckedResultHandshake
7 hours agoHandshake completed1.62 s
2 days agoHandshake completed1.82 s
4 days agoHandshake completed104 ms
5 days agoHandshake completed1.71 s
7 days agoHandshake completed169 ms
8 days agoHandshake completed2.62 s
9 days agoHandshake completed1.81 s
12 days agoHandshake completed1.87 s
13 days agoHandshake completed1.95 s
15 days agoHandshake completed2.13 s
16 days agoHandshake completed1.83 s
17 days agoHandshake completed1.90 s
19 days agoHandshake completed103 ms
19 days agoHandshake completed1.70 s
20 days agoHandshake completed102 ms
21 days agoHandshake completed123 ms
22 days agoHandshake completed1.60 s

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