Remote MCP · Endpoint

Viddler MCP server

No. Viddler answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.viddler.com/mcp

The last check completed an MCP handshake.

Registry name
com.viddler/viddler-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
180 ms
Tools exposed
12 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Official Viddler MCP: list videos, manage access control, pull proof-of-viewing analytics.
Listing
From the official MCP registry (active).
Recent checks of Viddler
CheckedResultHandshake
1 hour agoHandshake completed180 ms
2 days agoHandshake completed199 ms
4 days agoHandshake completed161 ms
5 days agoHandshake completed189 ms
7 days agoHandshake completed157 ms
8 days agoHandshake completed588 ms
9 days agoFailed - the request timed out—
12 days agoHandshake completed143 ms
13 days agoHandshake completed203 ms
15 days agoHandshake completed152 ms
16 days agoHandshake completed257 ms
17 days agoHandshake completed137 ms
18 days agoHandshake completed131 ms
19 days agoHandshake completed145 ms
20 days agoHandshake completed134 ms
21 days agoHandshake completed174 ms
22 days agoHandshake completed363 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Viddler and makes no claim about it beyond what these checks measured.