de en es ja ko ru zh

seedance-2-mcp

Name: seedance-2-mcp
Author: leonaiuv

by leonaiuv

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

seedance-2-mcp

npm version License: MIT

Un servidor MCP (Model Context Protocol) de código abierto y ejecución local que expone las capacidades de generación de video de Seedance 2.0 de Volcengine ARK a través de tres herramientas stdio para cualquier cliente MCP como Codex, Claude Desktop, Cursor, etc.

stdio puramente local, no requiere despliegue en la nube.
Desarrollado con Node.js + TypeScript, utilizando el SDK oficial @modelcontextprotocol/sdk.
Los usuarios solo necesitan configurar ARK_API_KEY en su propia máquina para invocar la generación de texto a video / imagen a video / referencia multimodal de Seedance 2.0.

Herramientas MCP proporcionadas

Herramienta	Función
`seedance_usage_guide`	Devuelve instrucciones de uso completas: flujo estándar, selección de modelo, tabla de parámetros, precauciones.
`seedance_create_task`	Envía una tarea de generación de video de Seedance 2.0, devuelve `task_id` inmediatamente, sin bloquear.
`seedance_check_task`	Consulta el estado de la tarea con `task_id`, devuelve `video_url` y la imagen del último fotograma opcional tras el éxito.

Para parámetros detallados, ver Detalles de las herramientas.

Related MCP server: Seedance MCP

Sugerencias de acceso rápido para agentes locales

Si estás utilizando Codex, Claude Desktop, Cursor u otro agente local compatible con MCP, puedes enviarle directamente el enlace a este repositorio y pedirle que lea esta sección.

你是一个本地开发 Agent。请帮我把这个仓库提供的 seedance-2-mcp 接入到当前 MCP 客户端中。

目标：
1. 读取仓库 README，理解这是一个 stdio MCP server，用于调用火山方舟 Seedance 2.0 视频生成 API。
2. 优先使用 npx 方式接入：command = "npx"，args = ["-y", "seedance-2-mcp"]。
3. 如果 npm 包暂不可用，或我明确想从源码运行，请 clone 本仓库，执行 npm install && npm run build，并将 MCP command 配为 "node"，args 配为 ["<仓库绝对路径>/dist/index.js"]。
4. 只向我索要或确认 ARK_API_KEY，不要把真实 API Key 写进仓库、README、示例文件或 git。
5. 根据我当前使用的客户端自动修改对应 MCP 配置：
   - Codex：修改 ~/.codex/config.toml
   - Claude Desktop：修改 claude_desktop_config.json
   - Cursor 或其他客户端：使用它们支持的 stdio MCP 配置格式
6. 配置完成后，提醒我重启或刷新 MCP 客户端，然后先调用 seedance_usage_guide，再按 create -> wait -> check 的流程生成视频。
7. 如果本机没有 Node.js >= 18 或 npx 不可用，请先指出缺失项，并给出最小安装建议。

重要约束：
- stdout 是 MCP JSON-RPC 通道，不要让 server 在 stdout 打调试日志。
- ARK_API_KEY 只能放在 MCP 客户端 env 配置或本机环境变量里。
- 生成的 video_url 通常会过期，任务成功后应提示我尽快下载。

También puedes decirle directamente al agente:

Lee este repositorio y ayúdame a configurar Seedance MCP siguiendo las "Sugerencias de acceso rápido para agentes locales" en el README. Proporcionaré la ARK_API_KEY.

Instalación

1. A través de `npx` (Recomendado - no requiere instalación manual)

Úsalo directamente en la configuración del cliente MCP:

npx -y seedance-2-mcp

Se descargará (o reutilizará la caché) la última versión en cada inicio.

2. Instalación global

npm install -g seedance-2-mcp

Después, simplemente usa seedance-2-mcp en la configuración del cliente.

3. Ejecución desde el código fuente (desarrolladores)

git clone https://github.com/seedance/seedance-2-mcp.git
cd seedance-2-mcp
npm install
npm run build
node dist/index.js

Requiere Node.js >= 18 (depende de fetch nativo).

Variables de entorno

Variable	Obligatorio	Descripción
`ARK_API_KEY`	Sí	API Key de Volcengine ARK. Visita https://console.volcengine.com/ark para obtenerla.
`ARK_BASE_URL`	No	Por defecto `https://ark.cn-beijing.volces.com/api/v3`. Se puede sobrescribir para el extranjero/proxy.

Copia .env.example a .env local solo como referencia de desarrollo; la ubicación donde realmente surte efecto es en el campo env de la configuración del cliente MCP, ya que el cliente inicia el MCP a través de un subproceso e inyecta las variables de entorno por sí mismo.

Si no se configura ARK_API_KEY al llamar a la herramienta, las dos herramientas que invocan la API real devolverán un error claro:

Missing ARK_API_KEY environment variable. Please set ARK_API_KEY to your Volcengine ARK API key.

Ejemplos de configuración del cliente

Codex (`~/.codex/config.toml`)

[mcp_servers.seedance-2-mcp]
command = "npx"
args = ["-y", "seedance-2-mcp"]
env = { "ARK_API_KEY" = "your_key_here" }

Claude Desktop (`claude_desktop_config.json`)

Ruta en macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Ruta en Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "seedance-2-mcp": {
      "command": "npx",
      "args": ["-y", "seedance-2-mcp"],
      "env": {
        "ARK_API_KEY": "your_key_here"
      }
    }
  }
}

Cursor / Otros clientes MCP

Configuración general para cualquier cliente que soporte stdio MCP:

{
  "command": "npx",
  "args": ["-y", "seedance-2-mcp"],
  "env": { "ARK_API_KEY": "your_key_here" }
}

Detalles de las herramientas

`seedance_usage_guide`

Sin parámetros. Devuelve instrucciones de uso completas en formato Markdown. Se recomienda llamar una vez antes de la primera llamada a seedance_create_task.

`seedance_create_task`

Envía una tarea de generación de video, devuelve task_id inmediatamente.

Parámetros de entrada:

Campo	Tipo	Por defecto	Descripción
`prompt`	string	— (Obligatorio)	Descripción en lenguaje natural. Si hay material de referencia, usa `[Image1]` / `[Video1]` / `[Audio1]` en el prompt.
`model`	enum	`doubao-seedance-2-0-260128`	`doubao-seedance-2-0-260128` (estándar, máxima calidad) / `doubao-seedance-2-0-fast-260128` (rápido).
`duration`	integer	`5`	Duración del video en segundos. `[4, 15]`.
`ratio`	enum	`16:9`	`21:9` / `16:9` / `4:3` / `1:1` / `3:4` / `9:16` / `adaptive`.
`resolution`	enum	`720p`	`480p` o `720p`.
`generate_audio`	boolean	`true`	Si se debe generar audio sincronizado (diálogo / efectos de sonido / BGM).
`watermark`	boolean	`true`	Si se debe añadir la marca de agua de la plataforma. Algunas cuentas podrían no poder desactivarla.
`web_search`	boolean	`false`	Si se habilita la mejora de búsqueda web para el prompt; solo disponible para entrada de texto puro, no se puede usar con image/video/audio simultáneamente.
`return_last_frame`	boolean	`false`	Si se devuelve la URL de la imagen del último fotograma, para empalme de segmentos.
`image_urls`	array	—	Máximo 9 elementos; cada uno `{ url, role? }`, `role` ∈ `reference_image` / `first_frame` / `last_frame`, por defecto `reference_image`.
`video_urls`	array	—	Máximo 3 elementos; cada uno `{ url, role? }`, `role` ∈ `reference_video`.
`audio_urls`	array	—	Máximo 3 elementos; cada uno `{ url, role? }`, `role` ∈ `reference_audio`. Debe acompañarse de image o video.

Reglas de validación:

duration debe ser un entero entre [4, 15].
image_urls ≤ 9, video_urls ≤ 3, audio_urls ≤ 3.
Se rechazará la combinación de solo texto + audio_urls (Seedance no lo soporta).
Se rechazará web_search=true junto con cualquier material de referencia (la mejora de búsqueda web solo soporta texto puro).

Retorno:

{
  "task_id": "cgt-2026xxxx-xxxxxx",
  "model": "doubao-seedance-2-0-260128",
  "duration": 5,
  "ratio": "16:9",
  "resolution": "720p",
  "raw": { /* 火山原始响应 */ }
}

`seedance_check_task`

Entrada { task_id: string }. Estados posibles:

running / queued / pending — Procesando. Se sugiere esperar 30-90 segundos antes de volver a llamar.
succeeded — Devuelve video_url, si return_last_frame=true también devuelve last_frame_url.
failed — Devuelve fail_reason (si existe).
cancelled / expired — Tarea cancelada o expirada.
Otros — Devuelve status y el payload original tal cual.

Flujo de llamada típico

client → seedance_usage_guide                                  ← 阅读规则
client → seedance_create_task { prompt, ... }                  ← 提交任务
                                                ↓
                                        task_id: cgt-...
                                                ↓
client → seedance_check_task { task_id }                       ← 30-90s 后轮询
                                ↓
                        status: running         （继续等待）
                                ↓
                        status: succeeded       ← 返回 video_url
                                ↓
                立刻下载 video_url（约 24h 内会过期）

Las tareas del modelo estándar de 15 segundos suelen tardar entre 2 y 5 minutos en completarse; la versión rápida será más corta.

Notas de seguridad

No escribas ARK_API_KEY en el repositorio git. Ponla en el campo env de la configuración del cliente MCP (como claude_desktop_config.json, ~/.codex/config.toml), o en las variables de entorno del shell.
Esta herramienta no imprimirá ARK_API_KEY en los registros o valores de retorno.
Las video_url y last_frame_url generadas por Volcengine son URLs temporales con firma, válidas por defecto durante 24 horas según las instrucciones oficiales de Volcengine; descarga los archivos lo antes posible después de que la tarea tenga éxito para evitar que el enlace expire.
Las image_urls / video_urls / audio_urls que proporciones deben ser direcciones HTTPS (o HTTP) accesibles desde la red pública; las rutas locales, direcciones de intranet o recursos que requieran inicio de sesión no pueden ser recuperados por el servidor de Volcengine.
Por favor, cumple con los términos de uso de Volcengine ARK y el modelo Seedance, no generes contenido ilegal, inapropiado para menores o que infrinja derechos de autor.

Desarrollo

npm install
npm run typecheck
npm run dev          # 用 tsx 直接跑 src/index.ts
npm run build        # 输出到 dist/
npm start            # node dist/index.js

Para depurar stdio MCP se recomienda:

npx -y @modelcontextprotocol/inspector npx -y seedance-2-mcp

O el código fuente local:

npx -y @modelcontextprotocol/inspector node dist/index.js

Estructura del proyecto

.
├── src/
│   ├── index.ts          # stdio MCP 入口（带 shebang）
│   ├── server.ts         # 注册 McpServer 和三个 tools
│   ├── seedance.ts       # 火山方舟 Seedance 2.0 REST API 客户端
│   ├── schema.ts         # zod 输入 schema
│   └── usageGuide.ts     # seedance_usage_guide 返回的文本
├── package.json
├── tsconfig.json
├── .env.example
├── .gitignore
├── LICENSE
└── README.md

Licencia

MIT © seedance-2-mcp contributors

Este proyecto no tiene relación oficial con ByteDance, Volcengine o Volcengine ARK. Los nombres "Seedance", "Doubao", "火山方舟", etc., son propiedad de sus respectivos titulares.

Available Tools

3 tools

seedance_check_taskCheck Seedance 2.0 task statusA

Read-onlyIdempotent

Query the status of a Seedance 2.0 task by task_id. Returns running / succeeded / failed / other. On success returns video_url (and last_frame_url if return_last_frame was true). Generated URLs expire within ~24h - download promptly.

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes	Seedance task id returned by seedance_create_task (e.g. cgt-...).

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnly and idempotent. Description adds URL expiration (~24h) and return format, which isn't in annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, no redundant or extraneous content. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Describes statuses and URL expiry without output schema. Adequate for a status check tool; could mention error handling but not required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with description for task_id. Description adds context that it's the ID from seedance_create_task, improving usability.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it queries status of a Seedance 2.0 task by task_id, lists possible statuses and success returns. Distinguishes from sibling tools (create and guide).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage after task creation but does not explicitly state when to use vs alternatives or mention polling patterns. No when-not or alternatives provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

seedance_create_taskCreate Seedance 2.0 video generation taskA

Submit a Seedance 2.0 video generation task to the Volcengine ARK API and return the task_id immediately. Does NOT wait for the video to render - poll seedance_check_task afterwards. Reference media URLs must be publicly reachable.

ParametersJSON Schema

Name	Required	Description	Default
`prompt`	Yes	Natural-language description of the desired video. Reference images / videos / audios with [Image1], [Video1], [Audio1] in 1-based order if you provided any.
`model`	No	Seedance 2.0 model id. doubao-seedance-2-0-260128 is the standard, highest-quality model. doubao-seedance-2-0-fast-260128 trades quality for latency.	doubao-seedance-2-0-260128
`duration`	No	Video length in seconds. Must be an integer in [4, 15].
`ratio`	No	Aspect ratio. Use 9:16 for vertical short-video, 16:9 for landscape. 'adaptive' lets the model pick the best fit when reference media is provided.	16:9
`resolution`	No	Output resolution. 720p is recommended; 480p is faster/cheaper.	720p
`generate_audio`	No	Whether to generate synchronized audio (dialogue, SFX, music). Set false for silent video.
`watermark`	No	Whether to add the platform watermark. Some accounts cannot disable this.
`web_search`	No	Enable prompt enhancement via web search. Text-only input is required when this is true.
`return_last_frame`	No	Return the last frame as an image URL alongside the video URL. Useful for chaining segments.
`image_urls`	No	Up to 9 reference images. Each item is { url, role? }. role defaults to 'reference_image'. Use 'first_frame' (and optionally 'last_frame') for image-to-video animation.
`video_urls`	No	Up to 3 reference videos. Each item is { url, role? }. role defaults to 'reference_video'.
`audio_urls`	No	Up to 3 reference audios. Each item is { url, role? }. role defaults to 'reference_audio'. Audio MUST be paired with at least one image or video reference.

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false, and the description confirms a mutation (creates a task). It adds context beyond annotations: the async nature ('Does NOT wait for the video to render') and the requirement for public URLs. However, it does not mention rate limits, error handling, or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences containing no fluff: first states core function, second explains async behavior with action, third adds constraint. Front-loaded with the most important information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and no output schema, the description covers the essential workflow and a key constraint (public URLs). It lacks details on error cases or the exact format of the returned task_id, but the async instruction is clear. Overall adequate but could be slightly more detailed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by emphasizing the async behavior and public URL requirement, which are not evident from individual parameter descriptions. It also clarifies the workflow (submit then poll).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Submit' and the resource 'Seedance 2.0 video generation task'. It specifies that it returns a task_id immediately and does not wait for rendering, distinguishing it from sibling tools like seedance_check_task that are used for polling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to poll seedance_check_task afterwards and notes that reference media URLs must be publicly reachable. It provides clear guidance on when to use this tool (to initiate a task) and what to do next (poll for results).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

seedance_usage_guideSeedance 2.0 usage guideA

Read-onlyIdempotent

Returns the canonical usage guide for the Seedance 2.0 MCP: standard create -> wait -> check workflow, model choices, parameter reference, and important caveats. Call this before your first seedance_create_task.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations (readOnlyHint, idempotentHint) already declare safe, idempotent behavior. The description adds that it returns a guide, but no additional behavioral traits beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. Front-loaded with key purpose and usage instruction. Highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema guide tool, the description fully explains its purpose, content, and when to use it. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so baseline is 4. The description adds meaning by explaining the tool's purpose and content, compensating for lack of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the canonical usage guide for Seedance 2.0 MCP, detailing workflow, model choices, parameters, and caveats. It distinguishes itself from sibling tools (check, create) by being the preliminary guide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit advice to call before first seedance_create_task provides clear context for use. No exclusions or alternatives are needed given its unique role as a guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv0.1.0May 2, 2026
- First observedseedance_check_task
- First observedseedance_create_task
- First observedseedance_usage_guide

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored 2026-05-02 19:30 across 3 tools

Disambiguation5/5

Each tool has a unique and clear purpose: creating a task, checking its status, and providing usage instructions. There is no overlap in functionality.

Naming Consistency4/5

All tools share the 'seedance_' prefix and follow a noun-based pattern (check_task, create_task, usage_guide), but 'usage_guide' is not a verb_noun like the others, causing minor inconsistency.

Tool Count5/5

With only 3 tools, the set is tightly scoped to the core workflow of generating and monitoring a video task, plus a guide. This is appropriate for the narrow domain.

Completeness4/5

The tools cover the essential create-and-check workflow, and the guide complements them. However, missing operations like task cancellation or listing are minor gaps but not critical for the basic use case.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

mcp-seedanceOAuth
io.github.AceDataCloud
MCP server for ByteDance Seedance AI video generation
Image & Video Processing Multimedia Processing Entertainment & Media
220
StoryStudioOAuth
io.github.HelloElo-Fr
AI image, video, voice and music generation over MCP, routed to Veo 3.1, Seedance 2.5 and more.
AI & Machine Learning Image & Video Processing Audio Processing
1
Treza A
io.github.treza-labs
Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.
AI & Machine Learning Image & Video Processing Payments & Billing
241
mcp-veoOAuth
io.github.AceDataCloud
MCP server for Google Veo AI video generation
Multimedia Processing Image & Video Processing Entertainment & Media
23

Related MCP Servers

Seedream/Seedance MCP Server
nsmao-com
A
license
C
quality
D
maintenance
Integrates Volcengine's Ark API to provide image and video generation and editing capabilities. It supports both local stdio and remote HTTP transport modes for flexible deployment and use.
Updated 7 months ago (2026-03-05 14:24 UTC)
8
24 npm
3
MIT
Seedance MCP
AI & Machine Learning Multimedia Processing Image & Video Processing
dpspace2050
F
license
A
quality
D
maintenance
Enables video generation using the Seedance 2.0 model through MCP, supporting both OpenAI and Volcengine API formats with tools for creating, monitoring, and downloading videos.
Updated 4 months ago (2026-06-12 11:12 UTC)
6
-
MathMind MCP Server
Multimedia Processing Image & Video Processing Audio Processing
Runninghcm
F
license
A
quality
D
maintenance
Provides a audio/video creation toolbox via MCP protocol, enabling natural language-based video editing tasks such as image-to-video, video merging, subtitle extraction, and more.
Updated a year ago (2025-08-09 17:53 UTC)
9
3
-
Seedance 2.5 MCP Server
AI & Machine Learning Image & Video Processing
Anil-matcha
A
license
Not graded
quality
B
maintenance
MCP server for generating Seedance 2.5 videos via MuAPI, enabling text-to-video, image-to-video, first/last frame, and omni reference workflows with 720p/480p resolution selection.
Updated 10 days ago (2026-09-28 12:58 UTC)
7
MIT

seedance-2-mcp

Herramientas MCP proporcionadas

Sugerencias de acceso rápido para agentes locales

Instalación

1. A través de npx (Recomendado - no requiere instalación manual)

2. Instalación global

3. Ejecución desde el código fuente (desarrolladores)

Variables de entorno

Ejemplos de configuración del cliente

Codex (~/.codex/config.toml)

Claude Desktop (claude_desktop_config.json)

Cursor / Otros clientes MCP

Detalles de las herramientas

seedance_usage_guide

seedance_create_task

seedance_check_task

Flujo de llamada típico

Notas de seguridad

Desarrollo

Estructura del proyecto

Licencia

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

1. A través de `npx` (Recomendado - no requiere instalación manual)

Codex (`~/.codex/config.toml`)

Claude Desktop (`claude_desktop_config.json`)

`seedance_usage_guide`

`seedance_create_task`

`seedance_check_task`