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.

Flow Music (fmusic)

PYPI · FLOWMUSIC-CLI

Unofficial MCP server for Google Flow Music (Lyria): generate, remix, stem-split and download songs.

Available components

−15 this week 59 Trust /100

Last scanned (19 hours ago)

Scores higher than 53% 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
  • 2 of 39 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 JvanLeeuwen4/flowmusic-cli). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 691 tokens (~76/item across 9 items; 9 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 (11% 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; "fmusic_chat" implies "send" 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.

What we tested

Checks we ran (14)

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

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 8 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 7 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 6 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 59

    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 21 Nov 2026 · Analysed pypi/flowmusic-cli@0.2.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 JvanLeeuwen4/flowmusic-cli
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/JvanLeeuwen4/flowmusic-cli/.github/workflows/ci.yml@refs/tags/v0.2.0
Rekor log index 3695004705
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0cccfe3efd2043ba4aa16796664f90c48591dc1b0e2116491307007856de9600

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

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

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

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~691 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
fmusic_auth_status ~23

Check whether the CLI is logged in, and the subscription tier.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fmusic_chat ~107

Send a follow-up to an existing Flow Music conversation, e.g. 'make it faster', 'extend it', 'add a guitar solo', 'remix the first take as drum and bass'. loop=True also writes seamless game loops.

NameTypeReqDescription
conversation_idstringyes–
downloadboolean––
formatstring––
loopboolean––
loop_formatstring––
messagestringyes–
out_dir–––

No output schema declared.

No examples provided.

fmusic_credits ~15

Remaining Flow Music credits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fmusic_download ~88

Download a clip's audio (wav, m4a or both) plus a metadata JSON sidecar. loop=True also writes a seamless game loop file (see fmusic_loop).

NameTypeReqDescription
clip_idstringyes–
coverboolean––
formatstring––
loopboolean––
loop_formatstring––
out_dir–––

No output schema declared.

No examples provided.

fmusic_generate ~193

Generate song(s) on Google Flow Music from a text prompt (genre, mood, instruments, tempo, vocals). Optionally pass full lyrics. The AI co-producer may make 1-2 takes. Takes ~1-2 minutes. For video game background music set loop=True: the prompt asks for a loopable song and each clip also gets a seamless <name>_loop.ogg (loop_format: ogg|wav|both) plus `loop` info (start/end, quality). Returns clips with local file paths (when download=True) and a conversation_id for follow-ups.

NameTypeReqDescription
downloadboolean––
formatstring––
instrumentalboolean––
loopboolean––
loop_formatstring––
lyrics–––
modelstring––
out_dir–––
promptstringyes–

No output schema declared.

No examples provided.

fmusic_get_clip ~35

Get a clip's metadata: title, duration, prompt, lyrics, audio URLs.

NameTypeReqDescription
clip_idstringyes–

No output schema declared.

No examples provided.

fmusic_list_clips ~34

List the user's songs (newest first).

NameTypeReqDescription
limitinteger––
offsetinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

fmusic_loop ~152

Make a seamless loop for video game background music, without spending credits. `source` is a local audio file (wav/flac/ogg/mp3) or an existing clip id. Skips the intro and the ending, finds a loop point that matches the loop start, and writes <name>_loop.ogg (loop_format: ogg|wav|both) that loops cleanly with looping enabled in the engine. A WAV source also gets the loop points as a smpl chunk (Godot: Loop Mode "Detect From WAV"). Check `quality` (good|ok|poor).

NameTypeReqDescription
loop_formatstring––
out_dir–––
sourcestringyes–

No output schema declared.

No examples provided.

fmusic_stems ~44

Split a clip into stems (vocals, drums, bass, other) and save them locally.

NameTypeReqDescription
clip_idstringyes–
out_dir–––

No output schema declared.

No examples provided.

Install

How do I install the Flow Music (fmusic) MCP server?

Flow Music (fmusic) runs locally as a PyPI package, launched with uvx flowmusic-cli mcp run. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · flowmusic-cli

# add to Claude Code
claude mcp add jvanleeuwen4-flowmusic-cli -- uvx flowmusic-cli mcp run
Common questions

What is the Flow Music (fmusic) MCP server?

Flow Music (fmusic) is an MCP server listed in the public MCP registry as io.github.JvanLeeuwen4/flowmusic-cli. Unofficial MCP server for Google Flow Music (Lyria): generate, remix, stem-split and download songs. This page covers its PyPI package (flowmusic-cli).

Is the Flow Music (fmusic) MCP server safe to use?

Flow Music (fmusic) scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Flow Music (fmusic) MCP server expose?

Flow Music (fmusic) exposes 9 tools: fmusic_generate, fmusic_chat, fmusic_list_clips, fmusic_get_clip, fmusic_download, and 4 more. Their descriptions and schemas cost roughly 691 tokens of context every time the server is loaded.

Is the Flow Music (fmusic) MCP server still maintained?

Flow Music (fmusic) is still listed as active in the MCP registry. We last reached this channel on 21 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 Flow Music (fmusic) MCP server under?

Flow Music (fmusic) 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 Flow Music (fmusic) MCP server?

VerifyMCP ran 14 checks on Flow Music (fmusic), covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Flow Music (fmusic): Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.