Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

REAPER MCP

PYPI · TWELVETAKE-REAPER-MCP · SCANNED OCT 5

Lets an AI assistant work in your open REAPER project: mixing, MIDI, routing and rendering.

Available components

pypi · twelvetake-reaper-mcp 81
+19 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to TwelveTake-Studios/reaper-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 14311 tokens (~79/item across 179 items; 179 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety99
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 21 of 22 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_track_master_send" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 180 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the REAPER MCP server?

REAPER MCP runs locally as a PyPI package, launched with uvx twelvetake-reaper-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · twelvetake-reaper-mcp

# add to Claude Code
claude mcp add com-twelvetake-reaper-mcp -- uvx twelvetake-reaper-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-twelvetake-reaper-mcp": {
      "command": "uvx",
      "args": [
        "twelvetake-reaper-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-twelvetake-reaper-mcp": {
      "command": "uvx",
      "args": [
        "twelvetake-reaper-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-twelvetake-reaper-mcp -- uvx twelvetake-reaper-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-twelvetake-reaper-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "twelvetake-reaper-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-twelvetake-reaper-mcp --command uvx --arg twelvetake-reaper-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-twelvetake-reaper-mcp:
    command: "uvx"
    args: ["twelvetake-reaper-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-twelvetake-reaper-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "twelvetake-reaper-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-twelvetake-reaper-mcp -t stdio -c uvx -a twelvetake-reaper-mcp
// mcp.json
{
  "mcpServers": {
    "com-twelvetake-reaper-mcp": {
      "command": "uvx",
      "args": [
        "twelvetake-reaper-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Sept 26 +1
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 1.7.7 → 1.8.0 functional
    • Package version: 1.7.7 → 1.7.8 functional
  • 28 Sept 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 9 Oct 2026 · Analysed pypi/twelvetake-reaper-mcp@1.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo TwelveTake-Studios/reaper-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/TwelveTake-Studios/reaper-mcp/.github/workflows/publish.yml@refs/tags/v1.8.0
Rekor log index 3005286116
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:5fb6fbfee502e798307c6c039367c69e24da4cf5a5a4f5ca693a6525d65f9cf4

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the REAPER MCP server?

REAPER MCP is listed in the public MCP registry as com.twelvetake/reaper-mcp. Lets an AI assistant work in your open REAPER project: mixing, MIDI, routing and rendering. This page covers its PyPI package (twelvetake-reaper-mcp).

Is the REAPER MCP server safe to use?

REAPER MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the REAPER MCP server still maintained?

REAPER MCP is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the REAPER MCP server under?

REAPER MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.