Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AceDataCloud/SeedanceMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/acedatacloud/seedancemcp/seedance)<a href="https://agentmods.dev/mcp/acedatacloud/seedancemcp/seedance"><img src="https://agentmods.dev/badge/mcp/acedatacloud/seedancemcp/seedance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/acedatacloud/seedancemcp/seedance"><img src="https://agentmods.dev/badge/mcp/acedatacloud/seedancemcp/seedance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
seedance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"seedance": {
"command": "uvx",
"args": [
"--from",
"mcp-seedance==2026.10.19.3",
"mcp-seedance"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 10 lines scan A a1b2d22142f3
seedance is an MCP server published in the GitHub repository AceDataCloud/SeedanceMCP (20 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-20.
Other mcp servers, from other repositories
mcp-veo
MCP Server for Veo AI Video Generation via AceDataCloud API. Runs locally from the mcp-veo Python package. Needs 1 environment variable to run.
mcp-wan
MCP Server for Wan AI Video Generation via AceDataCloud API. Runs locally from the mcp-wan Python package. Needs 1 environment variable to run.
mcp-kling
MCP Server for Kling AI Video Generation via AceDataCloud API. Runs locally from the mcp-kling Python package. Needs 1 environment variable to run.
mcp-hailuo
MCP Server for Hailuo (MiniMax) AI Video Generation via AceDataCloud API. Runs locally from the mcp-hailuo Python package. Needs 1 environment variable to run.
mcp-luma
MCP Server for Luma AI Video Generation via AceDataCloud API. Runs locally from the mcp-luma Python package. Needs 1 environment variable to run.
mcp-sora
MCP Server for Sora AI Video Generation via AceDataCloud API. Runs locally from the mcp-sora Python package. Needs 1 environment variable to run.