Remote MCP · Endpoint

Veedio Short-Video Planner MCP server

No. Veedio Short-Video Planner answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://www.veedio.co/api/mcp/public

The last check completed an MCP handshake.

Registry name
co.veedio.www/planner
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
95 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plan TikToks, Reels and Shorts: hook, timed beats, captions, CTA, plus the right Veedio tool page.
Listing
From the official MCP registry (active).
Recent checks of Veedio Short-Video Planner
CheckedResultHandshake
5 hours agoHandshake completed95 ms
9 days agoHandshake completed149 ms
10 days agoHandshake completed131 ms
11 days agoHandshake completed129 ms
12 days agoHandshake completed163 ms
14 days agoHandshake completed127 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed107 ms
17 days agoHandshake completed146 ms
19 days agoHandshake completed320 ms
21 days agoHandshake completed128 ms
24 days agoHandshake completed74 ms
26 days agoHandshake completed450 ms
28 days agoHandshake completed76 ms

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

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 Veedio Short-Video Planner and makes no claim about it beyond what these checks measured.