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.

Chutes Media MCP

NPM · CHUTES-MEDIA-MCP

Generate image, video, music and speech through Chutes and save assets into your project.

Available components

0 this week 93 Trust /100

Last scanned (5 hours ago)

Scores higher than 95% 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 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 TheStreamCode/chutes-media-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 22 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 547 tokens (~182/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
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 22 Nov 2026 · Analysed npm/chutes-media-mcp@2.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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo TheStreamCode/chutes-media-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/TheStreamCode/chutes-media-mcp/.github/workflows/publish.yml@refs/tags/v2.1.0
Rekor log index 3604693342
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0899894164ac5d98119bbff849db678dc24eb2d2d7bfd910e7ea743c4baa32995bef73cef4d0a865c36cbe0d218ba86b73956d395722ba4c35b7c3ee2

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~355 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
describe_media_model ~88

Fetch a model's live cords and input schemas so you can compose a valid request. ALWAYS call this before generate_media for an unfamiliar model. Returns every cord (e.g. generate, and img2img/inpaint when present) with its required fields, types, defaults and a minimal example payload.

NameTypeReqDescription
modelstringyesModel name/slug, e.g. owner/model-slug.
NameTypeReqDescription
cordsarrayyes–
invokeBaseUrlstring––
kindstring––
modelstringyes–
supportsEditingbooleanyes–
taglinestring––

No examples provided.

generate_media ~188

Run a generation and save the asset into the workspace. `params` is the payload you composed from describe_media_model. For editing, `params` may reference workspace file paths (e.g. image, mask) which the server reads and encodes. The asset is saved under output_dir (default ./assets/chutes/<kind>/) and the saved path is returned. Long video/music jobs block with progress updates.

NameTypeReqDescription
cordstring–Operation/cord (e.g. img2img); defaults to the primary one.
filenamestring––
kindstringyes–
modelstringyes–
output_dirstring–Output directory relative to CWD.
overwriteboolean–Explicitly replace an existing asset and sidecar.
paramsobjectyesPayload matching the cord's input schema.
timeout_msinteger––
NameTypeReqDescription
bytesintegeryes–
contentTypestringyes–
cordstringyes–
costnumber––
durationMsnumberyes–
kindstringyes–
modelstringyes–
pathstringyes–
provenancePathstring––
schemaHashstring––

No examples provided.

list_media_models ~79

List available Chutes media-generation models (image / video / music / speech), optionally filtered by kind or a free-text query. Use this to discover a model, then call describe_media_model before generate_media.

NameTypeReqDescription
kindstring––
limitinteger––
querystring–Free-text filter on the model name.
NameTypeReqDescription
countintegeryes–
modelsarrayyes–

No examples provided.

Install

How do I install the Chutes Media MCP server?

Chutes Media MCP runs locally as an npm package, launched with npx -y chutes-media-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · chutes-media-mcp

# add to Claude Code
claude mcp add thestreamcode-chutes-media-mcp -- npx -y chutes-media-mcp
Common questions

What is the Chutes Media MCP server?

Chutes Media MCP is listed in the public MCP registry as io.github.TheStreamCode/chutes-media-mcp. Generate image, video, music and speech through Chutes and save assets into your project. This page covers its npm package (chutes-media-mcp).

Is the Chutes Media MCP server safe to use?

Chutes Media MCP scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 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 Chutes Media MCP server expose?

Chutes Media MCP exposes 3 tools: list_media_models, describe_media_model, generate_media. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.

Is the Chutes Media MCP server still maintained?

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

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

What did VerifyMCP test on the Chutes Media MCP server?

VerifyMCP ran 16 checks on Chutes Media MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.