midi-file-mcp
A powerful MCP tool for parsing and manipulating MIDI files that allows users to read, analyze, and modify MIDI files through natural language commands, supporting operations like reading file information, modifying tracks, adding notes, and setting tempo.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
xiaolaa2
Source: ModelScope
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_midi_infoGet midi file info
set_tempoSet tempo for midi file
get_tracks_infoGet tracks info from midi file
get_track_info_by_indexGet track info from midi file by track index. name, instrument, channel, endOfTrackTicks, duration, durationTicks, noteCount
get_notes_by_indexGet notes from midi file by track index
get_pitchbends_by_indexGet pitchbends from midi file by track index
get_controlchanges_by_indexGet controlchanges from midi file by track index
add_notes_by_indexAdd notes to midi file by track index
add_controlchanges_by_indexAdd controlchanges to midi file by track index
add_pitchbends_by_indexAdd pitchbends to midi file by track index
add_trackAdd a new track to midi file and return the new track info
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
11/11 tools missing one or more hints — get_midi_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_tempo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tracks_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.8.0 (high), @modelcontextprotocol/sdk@1.8.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dependency freshness
1/4 production deps stale: @tonejs/midi@2022-04-07 (4.4y)
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/xiaolaa2/midi-file-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check