Claude Collider MCP Server
claude-collider
npm
v0.1.1
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for live coding music with SuperCollider
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 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 1
high Shell/command execution in server code (dist/process.js)MTC-SRC-002
In the server's implementation (`dist/process.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; import { EventEmitter } from "events"; import { debug } from "./debug.js"; impor
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/process.js
Tools 31
Each tool and what it can reach — statically extracted from the published source.
fx_bypassno sensitive capabilityfx_chainno sensitive capabilityfx_connectno sensitive capabilityfx_listno sensitive capabilityfx_loadno sensitive capabilityfx_removeno sensitive capabilityfx_routeno sensitive capabilityfx_route_triggerno sensitive capabilityfx_setno sensitive capabilityfx_sidechainno sensitive capability
Show 21 more tools ↓
midi_clearno sensitive capabilitymidi_connectno sensitive capabilitymidi_list_devicesno sensitive capabilitymidi_map_ccno sensitive capabilitymidi_map_notesno sensitive capabilityrecording_startno sensitive capabilityrecording_statusno sensitive capabilityrecording_stopno sensitive capabilityrouting_debugno sensitive capabilitysample_freeno sensitive capabilitysample_listno sensitive capabilitysample_playno sensitive capabilitysample_reloadno sensitive capabilitysc_audio_devicesno sensitive capabilitysc_bootno sensitive capabilitysc_clearno sensitive capabilitysc_executeno sensitive capabilitysc_rebootno sensitive capabilitysc_statusno sensitive capabilitysc_stopno sensitive capabilitysc_tempono sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (31 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.1 latest |
A 92/100 | 1 | 1.13.0 | 2026-09-08 |
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.
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 claude-collider --onlineMore in Design & Media
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Aleph's official SiliconFlow media-generation MCP server (image / video / TTS)
MCP server for image generation using Google Gemini AI
Ambience AI MCP Server - Generate images, videos, and audio through Model Context Protocol
MCP server exposing every endpoint of the AstroWay Calculation API as tools — natal, synastry, transits, Vedic dashas, Tarot, Numerology, Human Design, AI horoscopes — for Claude Desktop, Cursor and any MCP-compatible AI agent.
Audio-guide and trip-planning tools for 1,100+ cities from Audiala. Free, no API key.