net.seedance2/seedance2
Seedance 2
Is the Seedance 2 MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-10.
Seedance 2.5 and 2.0 AI video, plus AI images, from Claude, ChatGPT, Codex and Cursor.
needs auth probed 2026-11-15 · unchanged since 2026-11-10 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in to connect this app."}}- Endpoint
- https://www.seedance2.net/mcp (streamable-http)
- Host
- www.seedance2.net
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.seedance2.net/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server www.seedance2.net, PKCE S256, grants authorization_code, refresh_token.
Scopes read canvas:write run.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/nereo-io/seedance2-plugin
- Website
- https://www.seedance2.net/seedance-mcp
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention seedance2 or seedance.
- Seedance 2.0 MCP io.github.rocnubie/seedance2video-mcp · not probed
- Клод Кот — генерация изображений и видео ai.klodkot/gen · needs auth
- Kubflow AI ai.kubflow/kubflow · needs auth
- Seedance by Ace Data Cloud io.github.AceDataCloud/mcp-seedance · needs auth
- StoryStudio io.github.HelloElo-Fr/storystudio · needs auth
- Dora AI Video io.github.Saga-Labs/dora-mcp · needs auth
- Popcraft io.github.popcraft-ai/popcraft-mcp · needs auth
- Zurelay com.zurelay/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.