Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BeatDesign

MCPB · BEATDESIGN-0.2.1.MCPB

Local-first open-source AI media workbench with Canvas, video editor, Assets, and MCP tools.

−3 this week 52 Trust /100

Last scanned (5 hours ago)

Scores higher than 84% of MCPB servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security24
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 27 of 27 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 7 of 27 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 66 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 802 tokens (~40/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed mcpb/https://github.com/BeatAPI/BeatDesign/releases/download/v0.2.1/beatdesign-0.2.1.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 27 packages
Packages resolved 27
Deprecated 1
Stale 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~802 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bdesign_asset_get ~35

Read one project Asset by stable assetId.

NameTypeReqDescription
assetIdstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_asset_import ~46

Import a local image, video, or audio file into the project Asset library from an absolute path.

NameTypeReqDescription
filePathstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_asset_list ~33

List Assets that belong to a project.

NameTypeReqDescription
limitinteger––
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_canvas_apply ~61

Apply incremental Canvas operations. Raw document replacement is not exposed.

NameTypeReqDescription
commandIdstring––
expectedRevision–––
idempotencyKeystring––
operationsarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_canvas_get ~28

Read the Canvas document and revision for a project.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_canvas_search ~58

Search Canvas nodes by name, prompt, result text, model, kind, or media type.

NameTypeReqDescription
kindstring––
projectIdstringyes–
querystring––
typestring––

No output schema declared.

No examples provided.

bdesign_editor_diagnostics ~35

Diagnose gaps, overlaps, missing media, duration mismatches, and tiny clips.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_editor_edit ~71

Apply incremental timeline operations such as add, trim, split, move, remove, audio updates, and Takes.

NameTypeReqDescription
commandIdstring––
expectedRevision–––
idempotencyKeystring––
operationsarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_editor_get ~26

Read the current Editor timeline and revision.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_editor_history ~35

Read persisted command receipts for timeline and Canvas changes.

NameTypeReqDescription
limitinteger––
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_editor_snapshot ~44

Resolve the active timeline clips at a time. This is semantic inspection, not a pixel screenshot.

NameTypeReqDescription
projectIdstringyes–
timenumberyes–

No output schema declared.

No examples provided.

bdesign_editor_view ~39

Build an Editor deep link for a time and return its semantic snapshot.

NameTypeReqDescription
projectIdstringyes–
timenumber––

No output schema declared.

No examples provided.

bdesign_generation_history ~32

List generation history for a project.

NameTypeReqDescription
limitinteger––
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_generation_model_get ~30

Read one logical model, including defaults and accepted parameters.

NameTypeReqDescription
modelIdstringyes–

No output schema declared.

No examples provided.

bdesign_generation_models ~28

List logical generation models and their current parameter/reference capabilities.

NameTypeReqDescription
kindstring––

No output schema declared.

No examples provided.

bdesign_generation_status ~44

Read and, when possible, refresh one generation task.

NameTypeReqDescription
generationIdstringyes–
projectIdstring––
refreshboolean––

No output schema declared.

No examples provided.

bdesign_generation_submit ~73

Submit an asset-first image, video, or analysis generation. Outputs are recorded as reusable Assets.

NameTypeReqDescription
modestringyes–
modelIdstringyes–
parametersobject––
projectIdstringyes–
promptstringyes–
referencesarray––

No output schema declared.

No examples provided.

bdesign_project_create ~25

Create a new local BeatDesign project.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

bdesign_project_get ~36

Read one project with its Canvas and Editor documents.

NameTypeReqDescription
includeAssetsboolean––
projectIdstringyes–

No output schema declared.

No examples provided.

bdesign_project_list ~23

List local BeatDesign projects.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

Install

How do I install the BeatDesign MCP server?

BeatDesign ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · beatdesign-0.2.1.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Common questions

What is the BeatDesign MCP server?

BeatDesign is an MCP server listed in the public MCP registry as io.github.erickkkyt/beatdesign. Local-first open-source AI media workbench with Canvas, video editor, Assets, and MCP tools. This page covers its MCPB bundle (https://github.com/BeatAPI/BeatDesign/releases/download/v0.2.1/beatdesign-0.2.1.mcpb).

Is the BeatDesign MCP server safe to use?

BeatDesign scores 52 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the BeatDesign MCP server expose?

BeatDesign exposes 20 tools: bdesign_project_list, bdesign_project_get, bdesign_project_create, bdesign_asset_list, bdesign_asset_get, and 15 more. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.

What licence is the BeatDesign MCP server under?

BeatDesign declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.