updated 2026-11-11 00:08 UTC

Studio MCP

Repository by snyk
MCP Servers Go Listed Apache-2.0

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

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 100%
Last push 7d ago
Advisories None known
Compare Studio MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Studio MCP scores 62.5/100 (Grade C), ranked #627 of 1387 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 5.5/10; 100% of recent commits are signed; no published advisory affects its latest release (snyk); last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Studio 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 Studio 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 Signed

    github.com/snyk/studio-mcp, Apache-2.0, last pushed 2026-11-04. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review9
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    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 4
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 9
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • npm snyk Source link points to snyk/snyk, same owner 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: snyk 1.1308.4. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 6.0/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 Studio 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 Studio MCP compares in MCP Servers

  1. #343 Anilist MCP 62.7 +0.2
  2. #344 MCP Uptime Kuma 62.5 ±0
  3. #345 Studio MCP 62.5 this agent
  4. #346 Chat on Steroids 62.5 ±0
  5. #347 Unreal MCP 62.5 ±0

Bars show each HVTrust score; the tick marks Studio MCP’s 62.5.

Where the 62.5 comes from

HVTrust dimensions vs the MCP Servers average

62.5 / 100 · 100.0% confidence

Studio MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.1 above 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
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
in line with avg 12.3
AdoptionLog-scaled stars · package downloads
12.1 / 20
4.5 above 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 22 spots (#628 → #606)
2026-11-02
Rank Moved
Rank dropped 10 spots (#619 → #629)
2026-10-30
Rank Moved
Rank rose 15 spots (#630 → #615)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/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
View MCP Servers Report missing data
46.6
Activity sub-score · out of 100
#345
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-11 00:08 UTC · Repo last pushed 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
59
Forks
16
Last Push
2026-11-04
7 days ago
Commits (4 wk)
2?
Downloads (7d)
790,238
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #628

Analysis

Activity Inputs

46.6 / 100
StarsRepository reach
10.7 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
5.7 / 20

Common questions about Studio MCP

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 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 Studio MCP actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
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
How this surface has changed

Detected changes to Studio 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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 34HVTrust 3Grade 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-04
Rank Moved
Rank rose 22 spots (#628 → #606)
2026-11-02
Rank Moved
Rank dropped 10 spots (#619 → #629)
2026-10-30
Rank Moved
Rank rose 15 spots (#630 → #615)
2026-10-28
Rank Moved
Rank dropped 11 spots (#616 → #627)
2026-10-21
Rank Moved
Rank rose 11 spots (#627 → #616)
2026-10-19
Rank Moved
Rank dropped 19 spots (#609 → #628)
2026-10-16
Rank Moved
Rank dropped 22 spots (#579 → #601)
2026-10-15
Rank Moved
Rank rose 30 spots (#609 → #579)
2026-10-12
Rank Moved
Rank dropped 13 spots (#596 → #609)
2026-09-30
Rank Moved
Rank rose 29 spots (#589 → #560)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 371 spots (#947 → #576)
2026-09-23
HVTrust Changed
HVTrust up 35.9pts (25.9 → 61.8)
2026-09-22
Newly Listed
First tracked at rank #947
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 38 spots (#577 → #615)
2026-09-16
Rank Moved
Rank dropped 16 spots (#563 → #579)
2026-09-14
Rank Moved
Rank dropped 12 spots (#547 → #559)
2026-09-12
Rank Moved
Rank dropped 10 spots (#534 → #544)
2026-09-10
Rank Moved
Rank dropped 11 spots (#522 → #533)
2026-09-09
Rank Moved
Rank dropped 13 spots (#509 → #522)
2026-09-08
Rank Moved
Rank dropped 13 spots (#496 → #509)
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)
GitHub → npm: snyk

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.5 Grade C
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.4 · Raw JSON