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.

TrimScript

PYPI · TRIMSCRIPT

Edit video by editing the transcript. Runs locally; agent edits arrive as suggestions you approve.

Available components

−15 this week 59 Trust /100

Last scanned (2 hours ago)

Scores higher than 60% of PyPI 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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 54 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to SilverNine/trimscript). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 571 tokens (~71/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "withdraw" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 21 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Oct 26 +40
    • Injection markers: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 14 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess. functional
  • 13 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.96 ▲ functional
  • 12 Oct 26 23

    First indexed and scored.

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 24 Oct 2026 · Analysed pypi/trimscript@0.1.0

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo SilverNine/trimscript
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/SilverNine/trimscript/.github/workflows/release.yml@refs/tags/v0.1.0
Rekor log index 3186996782
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b25d57123107e06458b64c0fd5a4ac8741cca7c830559d0b96bffef2ba17666a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 54 packages
Packages resolved 54
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~426 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
correct_text ~76

Fix misheard words in items FIRST..LAST (e.g. a product name). Changes captions, not the media. Use it when you are confident: names, jargon, obvious mishearings.

NameTypeReqDescription
firststringyes–
laststringyes–
mediastringyes–
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

enhance_voice ~46

Turn voice enhancement (noise, level, loudness to -14 LUFS) on or off for previews and exports.

NameTypeReqDescription
mediastringyes–
onboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

export ~50

Render the accepted edit next to the source: mp4, wav, srt, vtt or fcpxml. Suggestions are not applied.

NameTypeReqDescription
formatstring––
mediastringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_transcript ~61

The transcript, one sentence per line, prefixed by its item id range and start time. with_ids=true prefixes every item with its id so you can remove part of a sentence.

NameTypeReqDescription
mediastringyes–
with_idsboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_edits ~30

Every removal and suggestion with its id, status, author and reason.

NameTypeReqDescription
mediastringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

suggest_removal ~63

Propose removing items FIRST..LAST (inclusive). Give a short reason the person will see.

NameTypeReqDescription
applyboolean––
firststringyes–
laststringyes–
mediastringyes–
reasonstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

transcribe ~64

Transcribe a media file locally (minutes for long files). Safe to call again: reuses an existing transcript. language is the spoken language code, such as en or de; there is no automatic detection.

NameTypeReqDescription
languagestring––
mediastringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

withdraw ~36

Take back one of your suggestions (or a removal) by id.

NameTypeReqDescription
cut_idstringyes–
mediastringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the TrimScript MCP server?

TrimScript runs locally as a PyPI package, launched with uvx trimscript. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · trimscript

# add to Claude Code
claude mcp add silvernine-trimscript -- uvx trimscript
Common questions

What is the TrimScript MCP server?

TrimScript is an MCP server listed in the public MCP registry as io.github.SilverNine/trimscript. Edit video by editing the transcript. Runs locally; agent edits arrive as suggestions you approve. This page covers its PyPI package (trimscript).

Is the TrimScript MCP server safe to use?

TrimScript scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. 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 TrimScript MCP server expose?

TrimScript exposes 8 tools: transcribe, get_transcript, suggest_removal, correct_text, list_edits, and 3 more. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.

Is the TrimScript MCP server still maintained?

TrimScript is still listed as active in the MCP registry. We last reached this channel on 24 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 TrimScript MCP server under?

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