Reaper (bonfire-audio) MCP Server

reaper-mcp-server PyPI v0.1.1

Published by bonfire-audio — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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

low Shell/command execution in packaging/dev tooling (examples/test_mcp_tools.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`examples/test_mcp_tools.py:28`): 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: osc_mcp.sh"] proc = subprocess.Popen(cmd, stdin=subprocess.PIPE,

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 examples/test_mcp_tools.py

Tools 60

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

  • add_fxno sensitive capability
  • add_master_fxno sensitive capability
  • add_midi_noteno sensitive capability
  • add_notesno sensitive capability
  • add_pan_automationno sensitive capability
  • add_volume_automationno sensitive capability
  • add_vst_pluginno sensitive capability
  • adjust_pitchno sensitive capability
  • adjust_playback_rateno sensitive capability
  • analyze_dynamicsno sensitive capability
Show 50 more tools ↓
  • analyze_frequency_spectrumno sensitive capability
  • analyze_loudnessno sensitive capability
  • analyze_stereo_fieldno sensitive capability
  • analyze_transientsno sensitive capability
  • apply_limiterno sensitive capability
  • apply_mastering_chainno sensitive capability
  • bypass_fxno sensitive capability
  • create_busno sensitive capability
  • create_chord_progressionno sensitive capability
  • create_drum_patternno sensitive capability
  • create_midi_itemno sensitive capability
  • create_projectno sensitive capability
  • create_sendno sensitive capability
  • create_trackno sensitive capability
  • delete_trackno sensitive capability
  • detect_clippingno sensitive capability
  • edit_audio_itemno sensitive capability
  • get_fx_parametersno sensitive capability
  • get_project_infono sensitive capability
  • get_track_infono sensitive capability
  • import_audio_fileno sensitive capability
  • list_master_fxno sensitive capability
  • list_sendsno sensitive capability
  • list_track_fxno sensitive capability
  • list_tracksno sensitive capability
  • load_fx_presetno sensitive capability
  • load_projectno sensitive capability
  • normalize_projectno sensitive capability
  • play_projectno sensitive capability
  • remove_fxno sensitive capability
  • remove_sendno sensitive capability
  • rename_trackno sensitive capability
  • render_projectno sensitive capability
  • render_stemsno sensitive capability
  • render_time_selectionno sensitive capability
  • save_projectno sensitive capability
  • set_cursor_positionno sensitive capability
  • set_fx_parameterno sensitive capability
  • set_master_fx_parameterno sensitive capability
  • set_master_volumeno sensitive capability
  • set_send_volumeno sensitive capability
  • set_tempono sensitive capability
  • set_time_signatureno sensitive capability
  • set_track_colorno sensitive capability
  • set_track_muteno sensitive capability
  • set_track_panno sensitive capability
  • set_track_solono sensitive capability
  • set_track_volumeno sensitive capability
  • start_recordingno sensitive capability
  • stop_transportno 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.1.1 latest A 99/100 1 1.9.0 2026-07-23

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

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 Developer Tools