Remote MCP · Endpoint
Velox TriFit: Virtual Try-On API MCP server
No. Velox TriFit: Virtual Try-On API answered an MCP handshake 56 minutes ago.
UpLast checked 56 minutes ago
Server URL
https://studio.v3lox.com/partner/trifit/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Velox-XR/velox-trifit-developer
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 423 ms
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Virtual try-on (VTO) API docs and SDK examples; OAuth account/guest photo uploads and try-ons.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 56 minutes ago | Handshake completed | 423 ms |
| 1 day ago | Handshake completed | 479 ms |
| 4 days ago | Handshake completed | 417 ms |
| 6 days ago | Handshake completed | 452 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 Velox TriFit: Virtual Try-On API and makes no claim about it beyond what these checks measured.