Is SeedanceMCP safe to use?

SeedanceMCP has an HVTrust score of 54.0/100 (Grade C), ranked #819 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SeedanceMCP?

SeedanceMCP scores 54.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under MCP Servers.

SeedanceMCP

AceDataCloud/SeedanceMCP

MCP server for ByteDance Seedance video generation via Ace Data Cloud.

MCP Servers Python Listed MIT

Is SeedanceMCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.5 / 10

Provenance None

Signed commits 35%

Last push 22d ago

Compare SeedanceMCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: SeedanceMCP scores 54.0/100 (Grade C), ranked #819 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 35% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How SeedanceMCP compares in MCP Servers

Bars show each HVTrust score; the tick marks SeedanceMCP’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

SeedanceMCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.4 / 25

2.9 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.9 / 20

0.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.6 below avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 197 spots (#1007 → #810)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for SeedanceMCP View MCP Servers Report missing data

38.8

Activity sub-score · out of 100

#460

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-04

22 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #816

Analysis

Activity Inputs

38.8 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

21.9 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

35%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about SeedanceMCP

Public trust evidence for SeedanceMCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does SeedanceMCP publish package provenance?

No published build provenance is currently detected for SeedanceMCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does SeedanceMCP have an OpenSSF Scorecard?

SeedanceMCP has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is SeedanceMCP actively maintained?

Maintained. Last push was 22 days ago.

What license does SeedanceMCP use?

SeedanceMCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are SeedanceMCP's commits signed?

35% of the last 100 commits to SeedanceMCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

SeedanceMCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to SeedanceMCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

Maintain SeedanceMCP?

For maintainers

HVTrust scores SeedanceMCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 197 spots (#1007 → #810)

2026-09-23

HVTrust Changed

HVTrust up 29.4pts (24.8 → 54.2)

2026-09-22

Newly Listed

First tracked at rank #1007

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 13 spots (#733 → #746)

2026-09-14

Rank Moved

Rank dropped 16 spots (#696 → #712)

2026-09-12

Rank Moved

Rank dropped 14 spots (#676 → #690)

2026-09-11

Rank Moved

Rank dropped 12 spots (#664 → #676)

2026-09-10

Rank Moved

Rank dropped 14 spots (#650 → #664)

2026-09-08

Rank Moved

Rank dropped 15 spots (#632 → #647)

2026-09-07

Rank Moved

Rank dropped 47 spots (#585 → #632)

2026-09-06

Rank Moved

Rank dropped 11 spots (#574 → #585)

2026-09-05

Rank Moved

Rank dropped 80 spots (#494 → #574)

2026-09-03

Rank Moved

Rank dropped 21 spots (#464 → #485)

2026-09-02

Rank Moved

Rank rose 45 spots (#509 → #464)

2026-09-01

Rank Moved

Rank dropped 14 spots (#495 → #509)

2026-08-31

Rank Moved

Rank dropped 31 spots (#464 → #495)

2026-08-30

Rank Moved

Rank rose 11 spots (#475 → #464)

2026-08-29

Rank Moved

Rank dropped 71 spots (#404 → #475)

2026-08-27

Rank Moved

Rank dropped 11 spots (#398 → #409)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 322 spots (#720 → #398)

2026-08-26

HVTrust Changed

HVTrust up 23.9pts (34.7 → 58.6)

2026-08-22

Rank Moved

Rank rose 22 spots (#745 → #723)

2026-08-16

Rank Moved

Rank dropped 10 spots (#733 → #743)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → none

2026-08-10

Rank Moved

Rank dropped 38 spots (#703 → #741)

2026-08-08

Newly Listed

First tracked at rank #703

GitHub → PyPI: mcp-seedance

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/seedancemcp.svg)](https://hvtracker.net/agents/seedancemcp)
            
HTML:
            <a href="https://hvtracker.net/agents/seedancemcp"><img src="https://hvtracker.net/badge/seedancemcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON