Remote MCP · Endpoint

Seedance 3.0 MCP server

No. Seedance 3.0 answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://seedance30-mcp.yangvex-ops.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.mryangsd-netizen/seedance30
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Seedance 3.0 info MCP (seedance30.com): product, pricing URL, capabilities. No video gen.
Listing
From the official MCP registry (active).
Recent checks of Seedance 3.0
CheckedResultHandshake
13 minutes agoHandshake completed170 ms
10 days agoHandshake completed198 ms
10 days agoHandshake completed181 ms
11 days agoHandshake completed285 ms
13 days agoHandshake completed138 ms
14 days agoHandshake completed132 ms
14 days agoHandshake completed132 ms
15 days agoHandshake completed216 ms
17 days agoHandshake completed836 ms
19 days agoHandshake completed210 ms
21 days agoHandshake completed249 ms
24 days agoHandshake completed220 ms
26 days agoHandshake completed296 ms
28 days agoHandshake completed145 ms

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

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 Seedance 3.0 and makes no claim about it beyond what these checks measured.