updated 2026-11-10 04:07 UTC

Flstudio MCP

Repository

AI-powered FL Studio control via the Model Context Protocol. Beyond piano-roll notes — full in-DAW mixing (Mix Doctor, gain staging, EQ/comp/reverb, reference matching), routing, and composition through Claude and other MCP clients. 67 tools. Windows & macOS.

MCP Servers Python Listed MIT

Is Flstudio MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.6 / 10
Provenance None
Signed commits 5%
Last push 6d ago
Advisories None known
Compare Flstudio MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Flstudio MCP scores 56.2/100 (Grade C), ranked #817 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; 5% of recent commits are signed; no published advisory affects its latest release (fl-studio-mcp); last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Flstudio MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Flstudio MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/rosasynthesiz/flstudio-mcp, MIT, last pushed 2026-11-04. 5% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.6/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 3
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • PyPI fl-studio-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: fl-studio-mcp 1.0.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 2.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Flstudio MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Flstudio MCP compares in MCP Servers

  1. #445 Nutrition MCP 56.2 ±0
  2. #446 Dbmcp 56.2 ±0
  3. #447 Flstudio MCP 56.2 this agent
  4. #448 OpenSTAAD MCP Server 56.0 −0.2
  5. #449 FreeCAD MCP 56.0 −0.2

Bars show each HVTrust score; the tick marks Flstudio MCP’s 56.2.

Where the 56.2 comes from

HVTrust dimensions vs the MCP Servers average

56.2 / 100 · 100.0% confidence

Flstudio MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.5 / 25
7.3 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.7 / 17
1.6 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.7 / 20
5.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-04
Rank Moved
Rank rose 198 spots (#1004 → #806)
2026-11-04
HVTrust Changed
HVTrust up 6.3pts (50.3 → 56.6)
2026-11-04
Activity Score Changed
Activity score up 18pts (45 → 63)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
62.4
Activity sub-score · out of 100
#447
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 6 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
136
Forks
23
Last Push
2026-11-04
6 days ago
Commits (4 wk)
32
Downloads (7d)
61
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #817

Analysis

Activity Inputs

62.4 / 100
StarsRepository reach
12.8 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
18.9 / 25
CommunityFork signal
6.4 / 20

Common questions about Flstudio MCP

Flstudio MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Flstudio MCP publish package provenance?
No published build provenance is currently detected for Flstudio MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Flstudio MCP have an OpenSSF Scorecard?
Flstudio MCP has an OpenSSF Scorecard score of 2.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Flstudio MCP actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does Flstudio MCP use?
Flstudio MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Flstudio MCP's commits signed?
5% of the last 100 commits to Flstudio MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Flstudio MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Flstudio MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-14
Activity Resumed
Activity resumed
2026-10-01
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Flstudio MCP?

For maintainers

HVTrust scores Flstudio MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 22HVTrust 5Score 2Scorecard 1Delisted 1Listed 1MCP 1Stale 1Fresh 1Grade 1
2026-11-04
Rank Moved
Rank rose 198 spots (#1004 → #806)
2026-11-04
HVTrust Changed
HVTrust up 6.3pts (50.3 → 56.6)
2026-11-04
Activity Score Changed
Activity score up 18pts (45 → 63)
2026-10-24
Rank Moved
Rank rose 23 spots (#1022 → #999)
2026-10-16
Rank Moved
Rank dropped 27 spots (#980 → #1007)
2026-10-15
Grade Changed
Trust grade D → C
2026-10-15
Rank Moved
Rank rose 55 spots (#1035 → #980)
2026-10-14
Activity Resumed
Activity resumed
2026-10-14
Rank Moved
Rank rose 124 spots (#1159 → #1035)
2026-10-14
HVTrust Changed
HVTrust up 6.7pts (42.2 → 48.9)
2026-10-14
Activity Score Changed
Activity score up 14pts (28 → 42)
2026-10-09
Rank Moved
Rank dropped 10 spots (#1135 → #1145)
2026-10-01
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 119 spots (#1220 → #1101)
2026-09-23
HVTrust Changed
HVTrust up 25.2pts (17.7 → 42.9)
2026-09-22
Newly Listed
First tracked at rank #1220
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 10 spots (#1081 → #1091)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1070 → #1082)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1060 → #1070)
2026-09-07
Rank Moved
Rank dropped 27 spots (#1033 → #1060)
2026-09-06
Rank Moved
Rank rose 213 spots (#1246 → #1033)
2026-09-06
HVTrust Changed
HVTrust up 13.6pts (29.8 → 43.4)
2026-09-05
Scorecard Added
OSSF Scorecard: 2.4/10
2026-09-05
Rank Moved
Rank rose 59 spots (#1305 → #1246)
2026-09-05
HVTrust Changed
HVTrust up 11.5pts (18.3 → 29.8)
2026-09-02
Rank Moved
Rank dropped 16 spots (#1276 → #1292)
2026-09-01
Rank Moved
Rank dropped 11 spots (#1265 → #1276)
2026-08-31
Rank Moved
Rank dropped 11 spots (#1254 → #1265)
2026-08-30
Rank Moved
Rank dropped 11 spots (#1243 → #1254)
2026-08-29
Rank Moved
Rank dropped 16 spots (#1227 → #1243)
2026-08-28
Rank Moved
Rank dropped 13 spots (#1214 → #1227)
2026-08-27
Rank Moved
Rank dropped 10 spots (#1204 → #1214)
2026-08-26
Rank Moved
Rank dropped 48 spots (#1156 → #1204)
2026-08-16
Rank Moved
Rank dropped 23 spots (#1130 → #1153)
GitHub → PyPI: fl-studio-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/flstudio-mcp.svg)](https://hvtracker.net/agents/flstudio-mcp)
HTML:
<a href="https://hvtracker.net/agents/flstudio-mcp"><img src="https://hvtracker.net/badge/flstudio-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON