aviutl2-mcp (sima05020/aviutl2-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

aviutl2-mcp

Enables LLMs to create, edit, and manage AviUtl2 video projects, with optional real-time control via a native bridge plugin.

→ sima05020/aviutl2-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

sima05020

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes19 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_environment

AviUtl2 のインストール状態 (本体パス・バージョン・データフォルダ・導入済みプラグイン/スクリプト数・起動中かどうか) を返す。最初に一度呼ぶことを推奨。

list_assets

AviUtl2 のデータフォルダにある拡張要素を一覧する。kind: scripts(スクリプト) / plugins(プラグイン) / figures(図形SVG) / transitions(シーンチェンジPNG) / fonts / aliases(エイリアス)

read_docs

本体付属のドキュメントを読む。doc: readme(aviutl2.txt 全体説明・オブジェクト/制御文字の仕様) / lua(lua.txt スクリプト(.anm2等)のLua仕様) / style(style.conf レイアウト設定の雛形)。offset/limit は行単位。

create_project

空の AviUtl2 プロジェクトファイルを作成する。パスは .aup2 で終わること。AviUtl2 本体・データフォルダ内には作成できない。

read_project

.aup2 を解析して JSON で返す (シーン設定・全オブジェクトのレイヤー/フレーム範囲/エフェクトとパラメータ)。GUI で作った既存プロジェクトからパラメータの書式を学ぶのにも使える。

add_objects

プロジェクトにオブジェクト (動画/画像/音声/テキスト/任意エフェクト構成) を追加する。同一レイヤー・同一シーン内でフレーム範囲が重なると AviUtl2 上で正しく扱えないので重ねないこと。frame_end は終了フレーム(含む)。

update_object

既存オブジェクトのレイヤー/フレーム範囲/エフェクトパラメータを変更する。object_index は read_project が返す index。effect_index を指定してそのエフェクトの params をマージ更新する。

delete_object

オブジェクトを削除する。以降のオブジェクトの index は詰められる。

update_scene

シーンの解像度・フレームレート・名前などを変更する (video.width / video.height / video.rate / audio.rate / name など)。

launch_aviutl2

AviUtl2 を起動する。project_path を指定するとそのプロジェクトを開く。注意: 既に AviUtl2 で同じプロジェクトを開いている場合、外部で編集した内容は取り込まれない (再度開き直す必要がある)。

install_script
uninstall_script
package_scripts
install_live_bridge
live_status

起動中のAviUtl2にブリッジプラグイン経由で接続できるか確認する(ping)。live_*系ツールを使う前に呼ぶこと。

live_get_state

起動中のAviUtl2から現在編集中シーンの設定と全オブジェクト(エイリアス形式)をリアルタイムに取得する。

live_add_object
live_update_object
live_delete_object

layer/frame_startで対象オブジェクトを特定して削除する。

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highadm-zip@0.5.18GHSA-xcpc-8h2w-3j85

adm-zip: Crafted ZIP file triggers 4GB memory allocation

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAVIUTL2_DATA_DIRデータフォルダ（既定 C:\ProgramData\aviutl2）
configAVIUTL2_EXE_DIRaviutl2.exe のあるフォルダ（自動検出に失敗する場合）
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/19 tools missing one or more hints — get_environment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_assets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_docs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — uninstall_script deletes at line 503 (fs.unlinkSync(target))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Production dependencies are patched

0 critical, 1 high severity in production deps — adm-zip@0.5.18 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sima05020/aviutl2-mcp?variant=verified)](https://m8ven.ai/mcp/sima05020/aviutl2-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1df51fc59c9ceedc09db2115c9545f5478a2416e
code hash: 9d95384db6d3fd8272343ea806fb5857235be77b03dfb7667bee584f2032deea
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client