Is Studio MCP safe to use?

Studio MCP has an HVTrust score of 62.7/100 (Grade C), ranked #502 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Studio MCP?

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

Studio MCP

snyk/studio-mcp

MCP Servers Go Grade C Listed Apache-2.0

62.7/100

Rank #502 of 1328

Compare Studio MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-19 · 20d ago

Recent change

Rank +10

Is Studio MCP safe? Studio MCP scores 62.7/100 (Grade C), ranked #502 of 1328 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 6.0/10; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#272 Pyslang MCP — 62.8 (C) → #273 Git MCP Server — 62.8 (C) → #275 Real Browser MCP — 62.7 (C) → #276 Replicant MCP — 62.7 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-07

Rank Moved

Rank dropped 33 spots (#463 → #496)

2026-09-06

Rank Moved

Rank dropped 35 spots (#428 → #463)

2026-09-05

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/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.

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

42.4

Activity sub-score · out of 100

#274

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 →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-08-19

20 days ago

Commits (4 wk)

Downloads (7d)

574,044

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #496

Analysis

HVTrust Dimensions vs MCP Servers

62.7 / 100 · 100.0% confidence

Studio MCP MCP Servers average (778 agents)

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

12.5 / 25

2.6 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

1.6 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

11.9 / 20

5.0 above avg 6.9

Activity Inputs

42.4 / 100

StarsRepository reach

10.5 / 30

FreshnessLast push recency

22.2 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

5.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 9

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 10

SAST 0

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Studio MCP safe?

Studio 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 Studio MCP publish package provenance?

No published build provenance is currently detected for Studio 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 Studio MCP have an OpenSSF Scorecard?

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

Maintained. Last push was 20 days ago.

What license does Studio MCP use?

Studio MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Studio MCP's commits signed?

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

Studio 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

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Studio MCP?

For maintainers

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

2026-09-07

Rank Moved

Rank dropped 33 spots (#463 → #496)

2026-09-06

Rank Moved

Rank dropped 35 spots (#428 → #463)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 660 spots (#1088 → #428)

2026-09-05

HVTrust Changed

HVTrust up 25.4pts (38.3 → 63.7)

2026-09-04

Rank Moved

Rank dropped 22 spots (#1066 → #1088)

2026-09-03

Rank Moved

Rank dropped 38 spots (#1028 → #1066)

2026-09-02

Rank Moved

Rank dropped 45 spots (#983 → #1028)

2026-09-01

Scorecard Added

OSSF Scorecard: 6.0/10

2026-09-01

Rank Moved

Rank rose 281 spots (#1264 → #983)

2026-09-01

HVTrust Changed

HVTrust up 19.2pts (18.4 → 37.6)

2026-08-31

Rank Moved

Rank dropped 11 spots (#1253 → #1264)

2026-08-30

Rank Moved

Rank dropped 11 spots (#1242 → #1253)

2026-08-29

Rank Moved

Rank dropped 16 spots (#1226 → #1242)

2026-08-28

Rank Moved

Rank dropped 17 spots (#1209 → #1226)

2026-08-27

Rank Moved

Rank dropped 18 spots (#1191 → #1209)

2026-08-26

Rank Moved

Rank dropped 44 spots (#1147 → #1191)

2026-08-20

Rank Moved

Rank dropped 11 spots (#1139 → #1150)

2026-08-19

Rank Moved

Rank rose 14 spots (#1153 → #1139)

2026-08-16

Rank Moved

Rank dropped 27 spots (#1133 → #1160)

2026-08-10

Rank Moved

Rank dropped 66 spots (#1061 → #1127)

2026-08-08

Newly Listed

First tracked at rank #1059

GitHub → npm: snyk

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/studio-mcp.svg)](https://hvtracker.net/agents/studio-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/studio-mcp"><img src="https://hvtracker.net/badge/studio-mcp.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