Is Music Studio safe to use?

Music Studio has an HVTrust score of 77.6/100 (Grade B), ranked #181 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Music Studio?

Music Studio scores 77.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 72 GitHub stars and is categorized under MCP Servers.

Music Studio

linxule/mcp-music-studio

Two-mode MCP music studio: scored composition (ABC notation) and live performance (Strudel). Interactive ext-apps UI with sheet music rendering, 30+ instruments, style presets, and live coding REPL.

MCP Servers TypeScript Listed MIT

Is Music Studio safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 9%

Last push yesterday

Compare Music Studio

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Music Studio scores 77.6/100 (Grade B), ranked #181 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 9% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Music Studio compares in MCP Servers

#99 The MCP server for GoReleaser 77.7 +0.1
#100 MCP Youtube 77.7 +0.1
#101 Music Studio 77.6 this agent
#102 DollhouseMCP 77.4 −0.2
#103 Sec Edgar MCP 77.3 −0.3

Bars show each HVTrust score; the tick marks Music Studio’s 77.6.

Where the 77.6 comes from

HVTrust dimensions vs the MCP Servers average

77.6 / 100 · 100.0% confidence

Music Studio MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.8 / 25

4.5 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

1.0 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.7 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Music Studio View MCP Servers Report missing data

65.9

Activity sub-score · out of 100

#101

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 B 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

142

Downloads (7d)

261

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #180

Analysis

Activity Inputs

65.9 / 100

StarsRepository reach

11.2 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 10

Common questions about Music Studio

Public supply-chain signals for Music Studio are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Music Studio carries less obvious unverified-evidence risk than projects with thin signals.

Does Music Studio publish package provenance?

Yes. Music Studio's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Music Studio have an OpenSSF Scorecard?

Music Studio has an OpenSSF Scorecard score of 5.5/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 Music Studio actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Music Studio use?

Music Studio ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Music Studio's commits signed?

9% of the last 100 commits to Music Studio 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

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 Music Studio'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-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Music Studio?

For maintainers

HVTrust scores Music Studio 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 504 spots (#681 → #177)

2026-09-23

HVTrust Changed

HVTrust up 46.5pts (31.2 → 77.7)

2026-09-22

Newly Listed

First tracked at rank #681

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 37 spots (#217 → #180)

2026-09-08

Grade Changed

Trust grade C → B

2026-09-08

Rank Moved

Rank rose 274 spots (#486 → #212)

2026-09-08

HVTrust Changed

HVTrust up 12.2pts (63.1 → 75.3)

2026-09-08

Activity Score Changed

Activity score up 34pts (32 → 66)

2026-09-07

Rank Moved

Rank dropped 33 spots (#453 → #486)

2026-09-05

Rank Moved

Rank dropped 73 spots (#376 → #449)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 568 spots (#935 → #367)

2026-09-03

HVTrust Changed

HVTrust up 21.5pts (41.9 → 63.4)

2026-09-02

Rank Moved

Rank dropped 56 spots (#879 → #935)

2026-09-01

Scorecard Added

OSSF Scorecard: 4.5/10

2026-09-01

Rank Moved

Rank rose 107 spots (#986 → #879)

2026-09-01

HVTrust Changed

HVTrust up 6.3pts (35.7 → 42.0)

2026-08-31

Rank Moved

Rank dropped 30 spots (#956 → #986)

2026-08-30

Rank Moved

Rank dropped 46 spots (#910 → #956)

2026-08-29

Rank Moved

Rank dropped 54 spots (#856 → #910)

2026-08-28

Rank Moved

Rank dropped 27 spots (#829 → #856)

2026-08-27

Rank Moved

Rank dropped 22 spots (#807 → #829)

2026-08-26

Rank Moved

Rank dropped 104 spots (#703 → #807)

2026-08-16

Rank Moved

Rank dropped 13 spots (#678 → #691)

2026-08-10

Rank Moved

Rank dropped 31 spots (#645 → #676)

2026-08-08

Newly Listed

First tracked at rank #646

GitHub → npm: mcp-music-studio

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/music-studio.svg)](https://hvtracker.net/agents/music-studio)
            
HTML:
            <a href="https://hvtracker.net/agents/music-studio"><img src="https://hvtracker.net/badge/music-studio.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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