Remote MCP · Endpoint
varg how to MCP server
No. varg how to answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.varg.ai/how-to
The last check completed an MCP handshake.
- Registry name
- ai.varg/how-to
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 125 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 5 checks
- Described by its publisher as
- Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.
- Website
- https://varg.ai/how-to
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 125 ms |
| 1 day ago | Handshake completed | 142 ms |
| 2 days ago | Handshake completed | 114 ms |
| 2 days ago | Handshake completed | 112 ms |
| 4 days ago | Handshake completed | 139 ms |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 5.
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 varg how to and makes no claim about it beyond what these checks measured.