Remote MCP · Endpoint
com.clientvo/site MCP server
No. com.clientvo/site answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://clientvo.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.clientvo/site
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.18 s
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Clientvo: the site's own MCP server — dataset; every answer cites the site.
- Website
- https://clientvo.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.18 s |
| 19 hours ago | Handshake completed | 821 ms |
| 2 days ago | Handshake completed | 609 ms |
| 3 days ago | Handshake completed | 761 ms |
| 4 days ago | Handshake completed | 510 ms |
| 5 days ago | Handshake completed | 888 ms |
| 6 days ago | Handshake completed | 605 ms |
| 8 days ago | Handshake completed | 1.23 s |
| 10 days ago | Handshake completed | 1.07 s |
| 13 days ago | Handshake completed | 2.19 s |
| 15 days ago | Handshake completed | 793 ms |
| 17 days ago | Handshake completed | 764 ms |
| 19 days ago | Handshake completed | 677 ms |
| 21 days ago | Handshake completed | 845 ms |
| 23 days ago | Handshake completed | 1.39 s |
| 25 days ago | Handshake completed | 692 ms |
| 27 days ago | Handshake completed | 882 ms |
| 28 days ago | Handshake completed | 865 ms |
| 29 days ago | Handshake completed | 1.57 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.clientvo/site and makes no claim about it beyond what these checks measured.