Strudel (williamzujkowski) MCP Server

@williamzujkowski/strudel-mcp-server npm v2.4.1 Source verified

Published by williamzujkowski — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Advanced MCP server for AI-powered music generation with Strudel.cc

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Dynamic evaluation of a non-literal value (dist/services/StrudelEngine.js)MTC-SRC-010

In the server's implementation (`dist/services/StrudelEngine.js:130`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const fn = new Function(...Object.keys(this.context), transpileResult.transpiledCode); const pa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/services/StrudelEngine.js

high Dynamic code execution in server code (dist/services/GeminiService.js)MTC-SRC-001

In the server's implementation (`dist/services/GeminiService.js:743`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: or safety 7. Do not use eval(), Function(), or any dangerous constructs Return the modified pattern code:`; } /

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/services/GeminiService.js

high Dynamic code execution in server code (dist/services/StrudelEngine.js)MTC-SRC-001

In the server's implementation (`dist/services/StrudelEngine.js:130`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const fn = new Function(...Object.keys(this.context), transpileResult.transpiledCode); const pa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/services/StrudelEngine.js

high Dynamic code execution in server code (dist/utils/PatternValidator.js)MTC-SRC-001

In the server's implementation (`dist/utils/PatternValidator.js:181`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: errors.push('Use of eval() or Function() is not allowed'); } return { safe: errors.lengt

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/PatternValidator.js

Tools 65

Each tool and what it can reach — statically extracted from the published source.

  • add_effectno sensitive capability
  • add_swingno sensitive capability
  • analyzeno sensitive capability
  • analyze_rhythmno sensitive capability
  • analyze_spectrumno sensitive capability
  • appendno sensitive capability
  • apply_scaleno sensitive capability
  • capture_audio_sampleno sensitive capability
  • clearno sensitive capability
  • compare_patternsno sensitive capability
Show 55 more tools ↓
  • composeno sensitive capability
  • create_sessionno sensitive capability
  • destroy_sessionno sensitive capability
  • detect_keyno sensitive capability
  • detect_tempono sensitive capability
  • diagnosticsno sensitive capability
  • export_midino sensitive capability
  • generate_basslineno sensitive capability
  • generate_chord_progressionno sensitive capability
  • generate_drumsno sensitive capability
  • generate_euclideanno sensitive capability
  • generate_fillno sensitive capability
  • generate_melodyno sensitive capability
  • generate_patternno sensitive capability
  • generate_polyrhythmno sensitive capability
  • generate_scaleno sensitive capability
  • generate_variationno sensitive capability
  • get_patternno sensitive capability
  • get_pattern_feedbackno sensitive capability
  • humanizeno sensitive capability
  • initno sensitive capability
  • insertno sensitive capability
  • jam_withno sensitive capability
  • listno sensitive capability
  • list_historyno sensitive capability
  • list_sessionsno sensitive capability
  • loadno sensitive capability
  • memory_usageno sensitive capability
  • pauseno sensitive capability
  • performance_reportno sensitive capability
  • playno sensitive capability
  • quantizeno sensitive capability
  • redono sensitive capability
  • refineno sensitive capability
  • remove_effectno sensitive capability
  • replaceno sensitive capability
  • restore_historyno sensitive capability
  • reverseno sensitive capability
  • saveno sensitive capability
  • screenshotno sensitive capability
  • set_energyno sensitive capability
  • set_tempono sensitive capability
  • shift_moodno sensitive capability
  • show_browserno sensitive capability
  • show_errorsno sensitive capability
  • start_audio_captureno sensitive capability
  • statusno sensitive capability
  • stopno sensitive capability
  • stop_audio_captureno sensitive capability
  • stretchno sensitive capability
  • switch_sessionno sensitive capability
  • transposeno sensitive capability
  • undono sensitive capability
  • validate_pattern_runtimeno sensitive capability
  • writeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.4.1 latest A 94/100 4 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/williamzujkowski-strudel-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/williamzujkowski-strudel-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/williamzujkowski-strudel-mcp-server"><img src="https://mcptrustchecker.com/registry/williamzujkowski-strudel-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/williamzujkowski-strudel-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @williamzujkowski/strudel-mcp-server --online

Use the free API → How scoring works

Other implementations of Strudel 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Data Science & ML