Remote MCP · Endpoint

Alto MCP server

No. Alto answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://alto.video/api/mcp

The last check completed an MCP handshake.

Registry name
video.alto/alto
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
414 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Send a finished video with one tracked link per recipient, and see who watched and how far.
Website
https://alto.video/docs/cli-and-mcp
Listing
From the official MCP registry (active).
Recent checks of Alto
CheckedResultHandshake
1 hour agoHandshake completed414 ms
2 days agoHandshake completed433 ms
5 days agoHandshake completed614 ms
7 days agoHandshake completed422 ms
9 days agoHandshake completed293 ms
11 days agoHandshake completed603 ms
13 days agoHandshake completed540 ms
15 days agoHandshake completed344 ms
16 days agoHandshake completed444 ms
18 days agoHandshake completed341 ms
19 days agoHandshake completed334 ms
20 days agoHandshake completed377 ms
23 days agoHandshake completed460 ms
24 days agoHandshake completed118 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Alto and makes no claim about it beyond what these checks measured.