reaper-mcp@0.83.2
VERIFIED· install onlyPublisher claims: "MCP server for controlling REAPER DAW — real-time mixing, FX control, and frequency analysis for AI agents" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso huggingface.co — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
"'sudo apt install libfluidsynth3' on Debian/Ubuntu. "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Hi 👋 reaper-mcp isn't a company — it's just me. I'm a developer who loves making music,Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Prefer ReaPack for the REAPER side?</b></summary> In REAPER: **Extensions → ReaPack → Import repositories…**, paste `https://github.com/mthines/reapFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Can it wreck my project?</b></summary> <br> Every edit is a single undo step, and the mix skills snapshot before and after a task. Use <code>/critiqFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Something not working?</b></summary> <br> - **Run `reaper-mcp doctor`.** It checks the bridge, whether it starts with REAPER, the skills and the ClaFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @mthines/reaper-mcp@0.83.2 as of 3d ago. This is the package itself, not its dependencies.