@mthines/reaper-mcp
npm
v0.19.0
Source verified
Published by mthines — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 6 = 88. 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 |
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.
In the server's implementation (`main.js:2241`): 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: rt { spawn } from "node:child_process"; import { existsSync } from "node:fs"; import { join as join3 } from "node:path";
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 main.js
In the server's implementation (`main.js:2992`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. 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 result = await exec(`"${pythonBin}" --version`); stdout = (result.stdout + result.stderr).trim(); } catch
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 main.js
Each tool and what it can reach — statically extracted from the published source.
get_envelope_pointsreads sensitive dataadd_fxno sensitive capabilityadd_markerno sensitive capabilityadd_regionno sensitive capabilityadd_stretch_markerno sensitive capabilityanalyze_fxno sensitive capabilityanalyze_midino sensitive capabilityanalyze_track_aestheticsno sensitive capabilityclear_envelopeno sensitive capabilitycreate_midi_itemno sensitive capabilitycreate_track_envelopeno sensitive capabilitydelete_envelope_pointno sensitive capabilitydelete_markerno sensitive capabilitydelete_media_itemno sensitive capabilitydelete_midi_ccno sensitive capabilitydelete_midi_noteno sensitive capabilitydelete_regionno sensitive capabilitydelete_stretch_markerno sensitive capabilitydisable_tool_categoryno sensitive capabilityedit_midi_noteno sensitive capabilityedit_midi_notesno sensitive capabilityenable_tool_categoryno sensitive capabilityget_fx_parametersno sensitive capabilityget_fx_preset_listno sensitive capabilityget_media_item_propertiesno sensitive capabilityget_midi_ccno sensitive capabilityget_midi_item_propertiesno sensitive capabilityget_midi_notesno sensitive capabilityget_project_infono sensitive capabilityget_selected_tracksno sensitive capabilityget_stretch_markersno sensitive capabilityget_tempo_mapno sensitive capabilityget_time_selectionno sensitive capabilityget_track_envelopesno sensitive capabilityget_track_propertiesno sensitive capabilityget_track_routingno sensitive capabilityget_transport_stateno sensitive capabilityinsert_envelope_pointno sensitive capabilityinsert_envelope_pointsno sensitive capabilityinsert_midi_ccno sensitive capabilityinsert_midi_noteno sensitive capabilityinsert_midi_notesno sensitive capabilitylist_available_fxno sensitive capabilitylist_markersno sensitive capabilitylist_media_itemsno sensitive capabilitylist_midi_itemsno sensitive capabilitylist_regionsno sensitive capabilitylist_tool_categoriesno sensitive capabilitylist_tracksno sensitive capabilitymeasure_tracksno sensitive capabilitymove_media_itemno sensitive capabilityplayno sensitive capabilityread_track_correlationno sensitive capabilityread_track_crestno sensitive capabilityread_track_lufsno sensitive capabilityread_track_metersno sensitive capabilityread_track_spectrumno sensitive capabilityrecordno sensitive capabilityremove_envelope_pointsno sensitive capabilityremove_fxno sensitive capabilitysearch_fxno sensitive capabilitysend_midi_ccno sensitive capabilitysend_midi_noteno sensitive capabilitysend_midi_pcno sensitive capabilityset_cursor_positionno sensitive capabilityset_envelope_propertiesno sensitive capabilityset_fx_enabledno sensitive capabilityset_fx_offlineno sensitive capabilityset_fx_parameterno sensitive capabilityset_fx_presetno sensitive capabilityset_media_item_propertiesno sensitive capabilityset_media_items_propertiesno sensitive capabilityset_midi_item_propertiesno sensitive capabilityset_multiple_fx_parametersno sensitive capabilityset_multiple_track_propertiesno sensitive capabilityset_time_selectionno sensitive capabilityset_track_propertyno sensitive capabilitysetup_fx_chainno sensitive capabilitysnapshot_deleteno sensitive capabilitysnapshot_listno sensitive capabilitysnapshot_restoreno sensitive capabilitysnapshot_saveno sensitive capabilitysplit_media_itemno sensitive capabilitystopno sensitive capabilitytrim_media_itemno sensitive capabilityScan 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.19.0 latest |
B 88/100 | 2 | 1.9.0 | 2026-07-24 |
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.
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 @mthines/reaper-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
Security scan results for the Reaper (nbdy) MCP server.
Security scan results for the Reaper (bonfire-audio) MCP server.
Security scan results for the Aether MCP server.
Security scan results for the Bedbook MCP server.
Grade any bet against thousands of play-by-play game simulations: win probability, odds, edge.
Security scan results for the Claudinho MCP server.
Security scan results for the Cpu Game MCP server.
Security scan results for the Dfhack MCP server.