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.

NoaCG Broadcast Graphics and Playout

NPM · @NOACG/CLI

Make broadcast graphics for NoaCG Studio and play them out live on CasparCG, OBS, vMix or OGraf.

Available components

−2 this week 79 Trust /100

Last scanned (3 hours ago)

Scores higher than 67% of npm 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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.31.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 39 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to NoaCG/NoaCG-Studio). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability32
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 618 tokens (~88/item across 7 items; 1 tools + 6 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 25 Oct 26 +1

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

  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 23 Oct 26 +1

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

  • 21 Oct 26 −5
    • CVE-2026-111771 affects this package: high ▼ security
    • CVE-2026-111768 affects this package: high ▼ security
    • CVE-2026-111769 affects this package: high ▼ security
    • CVE-2026-111767 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 +1

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

  • 18 Oct 26 +6
    • Stability: 0.50 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • CVE-2026-104850 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 0 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.12.2 → 0.12.3 functional
  • 17 Oct 26 +6
    • Known CVEs: unverified → fail ▼ security
    • Dependency health: unverified → 0.83 ▲ functional
  • 16 Oct 26 −5
    • Stability: 0.43 → unverified ▼ security
    • Known CVEs: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 0 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 101 → 88 ▲ functional
    • Package version: 0.11.0 → 0.12.2 functional
    • Package version: 0.11.0 → 0.12.1 functional
    • Package version: 0.11.0 → 0.12.0 functional
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 25 Oct 2026 · Analysed npm/@noacg/cli@0.12.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo NoaCG/NoaCG-Studio
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/NoaCG/NoaCG-Studio/.github/workflows/release-cli.yml@refs/heads/main
Rekor log index 3307733780
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:3a9d16e0bc4697ae66a1a57533b2c7c2c313b614b45c69fa955c8152fb7c69a869dcba728c0fa4237142285c6053c304608e2ad15b4710a9b80d15db6

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 106 packages
Packages resolved 106
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~585 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
noacg ~585

NoaCG Studio broadcast graphics (lower third, scoreboard, ticker, countdown, any on-air graphic; SPX / CasparCG / OGraf packages): make, check and deliver them. The verbs of the `noacg` terminal CLI; docs "skill" is the procedure, "contract" the rulebook.

NameTypeReqDescription
atstring–screenshot: time after the last op, e.g. 4s
backgroundstring–validate/screenshot: transparent|checker|video|colour|image file
benchboolean–validate/save/pack: live runtime bench (default true)
commandstringyestypes: the graphic types NoaCG knows | scaffold: write a package | validate: gate + runtime bench, regenerates the package | inspect: the operator surface | screenshot: one frame, as an image | docs:…
dataobject–screenshot: explicit field values
designstring–scaffold: a design id, or "neutral"
eventsarray–screenshot: ops after the Take: event|next|out|field=value|wait:2s
fieldsstring–scaffold: typeless: "Label:kind[=value],..."; kinds text|lines|number|color|select|toggle|image; select options as Label:select=a|b|c
folderstring–save: a library folder
fontstring–scaffold
houseContractboolean–validate/save/pack: editability contract as errors (default true)
namestring–scaffold/save/pack: graphic or production name
outstring–scaffold/pack: a new dir (scaffold) or a .noacgpack.json (pack)
palettestring–scaffold
pathstring–validate/inspect/screenshot/save: package dir or .zip
pathsarray–save/pack: package dirs or .zips, in order
productionstring–save: make a production too
rundownarray–save/pack: [{graphic,label,values}]
screenshotsboolean–validate: off/onair/stress + each state reached, as images
shareobject–pack: see the skill's references/share.md
statestring–screenshot: default onair
topicstring–docs: skill|contract|package|validator|control|design-notes
typestring–scaffold: a type id (see types)
valuesobject–scaffold: starting values by field key
zonestring–scaffold

No output schema declared.

No examples provided.

Install

How do I install the NoaCG Broadcast Graphics and Playout MCP server?

NoaCG Broadcast Graphics and Playout runs locally as an npm package, launched with npx -y @noacg/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @noacg/cli

# add to Claude Code
claude mcp add noacg-noacg -- npx -y @noacg/cli
Common questions

What is the NoaCG Broadcast Graphics and Playout MCP server?

NoaCG Broadcast Graphics and Playout is an MCP server listed in the public MCP registry as io.github.NoaCG/noacg. Make broadcast graphics for NoaCG Studio and play them out live on CasparCG, OBS, vMix or OGraf. This page covers its npm package (@noacg/cli).

Is the NoaCG Broadcast Graphics and Playout MCP server safe to use?

NoaCG Broadcast Graphics and Playout scores 79 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 NoaCG Broadcast Graphics and Playout MCP server expose?

NoaCG Broadcast Graphics and Playout exposes 1 tool: noacg. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.

Is the NoaCG Broadcast Graphics and Playout MCP server still maintained?

NoaCG Broadcast Graphics and Playout is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the NoaCG Broadcast Graphics and Playout MCP server under?

NoaCG Broadcast Graphics and Playout 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.