Reaper (mthines) MCP Server

@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.

Trust grade
B
88/100
Last scanned get badge →
Trust
B · 88/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
B Why this grade threat 94 − adoption risk = 88/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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−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:

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 2

high Shell/command execution in server code (main.js)MTC-SRC-002

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

medium Untrusted input concatenated into a command sink (main.js)MTC-SRC-009

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

Tools 85

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

  • get_envelope_pointsreads sensitive data
  • add_fxno sensitive capability
  • add_markerno sensitive capability
  • add_regionno sensitive capability
  • add_stretch_markerno sensitive capability
  • analyze_fxno sensitive capability
  • analyze_midino sensitive capability
  • analyze_track_aestheticsno sensitive capability
  • clear_envelopeno sensitive capability
  • create_midi_itemno sensitive capability
Show 75 more tools ↓
  • create_track_envelopeno sensitive capability
  • delete_envelope_pointno sensitive capability
  • delete_markerno sensitive capability
  • delete_media_itemno sensitive capability
  • delete_midi_ccno sensitive capability
  • delete_midi_noteno sensitive capability
  • delete_regionno sensitive capability
  • delete_stretch_markerno sensitive capability
  • disable_tool_categoryno sensitive capability
  • edit_midi_noteno sensitive capability
  • edit_midi_notesno sensitive capability
  • enable_tool_categoryno sensitive capability
  • get_fx_parametersno sensitive capability
  • get_fx_preset_listno sensitive capability
  • get_media_item_propertiesno sensitive capability
  • get_midi_ccno sensitive capability
  • get_midi_item_propertiesno sensitive capability
  • get_midi_notesno sensitive capability
  • get_project_infono sensitive capability
  • get_selected_tracksno sensitive capability
  • get_stretch_markersno sensitive capability
  • get_tempo_mapno sensitive capability
  • get_time_selectionno sensitive capability
  • get_track_envelopesno sensitive capability
  • get_track_propertiesno sensitive capability
  • get_track_routingno sensitive capability
  • get_transport_stateno sensitive capability
  • insert_envelope_pointno sensitive capability
  • insert_envelope_pointsno sensitive capability
  • insert_midi_ccno sensitive capability
  • insert_midi_noteno sensitive capability
  • insert_midi_notesno sensitive capability
  • list_available_fxno sensitive capability
  • list_markersno sensitive capability
  • list_media_itemsno sensitive capability
  • list_midi_itemsno sensitive capability
  • list_regionsno sensitive capability
  • list_tool_categoriesno sensitive capability
  • list_tracksno sensitive capability
  • measure_tracksno sensitive capability
  • move_media_itemno sensitive capability
  • playno sensitive capability
  • read_track_correlationno sensitive capability
  • read_track_crestno sensitive capability
  • read_track_lufsno sensitive capability
  • read_track_metersno sensitive capability
  • read_track_spectrumno sensitive capability
  • recordno sensitive capability
  • remove_envelope_pointsno sensitive capability
  • remove_fxno sensitive capability
  • search_fxno sensitive capability
  • send_midi_ccno sensitive capability
  • send_midi_noteno sensitive capability
  • send_midi_pcno sensitive capability
  • set_cursor_positionno sensitive capability
  • set_envelope_propertiesno sensitive capability
  • set_fx_enabledno sensitive capability
  • set_fx_offlineno sensitive capability
  • set_fx_parameterno sensitive capability
  • set_fx_presetno sensitive capability
  • set_media_item_propertiesno sensitive capability
  • set_media_items_propertiesno sensitive capability
  • set_midi_item_propertiesno sensitive capability
  • set_multiple_fx_parametersno sensitive capability
  • set_multiple_track_propertiesno sensitive capability
  • set_time_selectionno sensitive capability
  • set_track_propertyno sensitive capability
  • setup_fx_chainno sensitive capability
  • snapshot_deleteno sensitive capability
  • snapshot_listno sensitive capability
  • snapshot_restoreno sensitive capability
  • snapshot_saveno sensitive capability
  • split_media_itemno sensitive capability
  • stopno sensitive capability
  • trim_media_itemno 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
v0.19.0 latest B 88/100 2 1.9.0 2026-07-24

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: B · 88/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mthines-reaper-mcp/badge.svg)](https://mcptrustchecker.com/registry/mthines-reaper-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mthines-reaper-mcp"><img src="https://mcptrustchecker.com/registry/mthines-reaper-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mthines-reaper-mcp/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 @mthines/reaper-mcp --online

Use the free API → How scoring works

Other implementations of Reaper 2

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

More in Gaming & Entertainment