Vibe ComposerSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
- Vibe composer as an MCP server
- Watch the video for an overview
- Talk to an LLM and compose music!
- Multi track - not just a piano, but the whole band
- Also can output to a software or a hardware synthesizer for a better sound!
Complete example on YouTube
Example prompts
Play an upbeat melody on the piano- Audio example of that
Spicy it up with fast passages with 16th notes- Audio example of that
Add a few bars on the saxophone while piano is playing chords- Audio example of that
Add drums for the whole duration of the song- Audio example of that
Playing it on a software or hardware synthesizer
- Ask an LLM to list MIDI outputs -
Which MIDI outputs are available? - It may tell you that you have
Logic Pro - Then ask to play it on logic pro and assign channels: e.g.:
Play in on Logic Pro and route the tracks to the following channels: - Piano - channel 0 - Sax - channel 1 - Drums - channel 2
Installation
- Using an example of Claude Desktop as an MCP client:
Add this to ~/Library/Application Support/Claude/claude_desktop_config.json
"vibe-composer-midi-mcp": {
"command": "npx",
"args": ["vibe-composer-midi-mcp@latest"]
}82500d3ebca3OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add vibe-composer-midi-mcp -- npx -y [email protected]
{
"mcpServers": {
"vibe-composer-midi-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
list-midi-outputs | read | Lists MIDI outputs |
play | read | Plays a music score |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- UNDECLARED (3 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (9)
import { Midi } from "../../midi/midi";import { Drums, Instruments } from "../../midi/instruments";import { Midi } from "../../midi/midi";@modelcontextprotocol/sdk, jzz, zod, @types/express, @types/node, express, tsx, typescript
examples/full-band.wav
examples/upbeat-piano-with-fast-passages.wav
examples/upbeat-piano.wav
examples/with-sax.wav
Gates applied: no_behavioural_pass, no_license.
82500d3ebca3full audit observations/trust-audit/mcp-server/mikeborozdin__vibe-composer.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 82500d3ebca3 | SAFE | B | 89 | first audit |
Questions
What tools does Vibe Composer expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Vibe Composer safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Vibe Composer need?
No credential environment variables were found in its source, so it appears to need none.
How does Vibe Composer run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as vibe-composer-midi-mcp at 1.3.2.
How current is this page?
The grade is for one exact copy of the source (82500d3ebca3), read on 2026-10-10. The repository is watched and re-audited when it changes.