MusicXML Comparer
PYPI · COMPARER-MCP · SCANNED OCT 1
Music-aware, multi-level comparison of two MusicXML files
Available components
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
- 3 of 50 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to raulkivi/sheet-music-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 905 tokens (~113/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the MusicXML Comparer MCP server?
MusicXML Comparer runs locally as a PyPI package, launched with uvx comparer-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 · comparer-mcp
claude mcp add raulkivi-comparer-mcp -- uvx comparer-mcp
{
"mcpServers": {
"raulkivi-comparer-mcp": {
"command": "uvx",
"args": [
"comparer-mcp"
]
}
}
} {
"servers": {
"raulkivi-comparer-mcp": {
"command": "uvx",
"args": [
"comparer-mcp"
]
}
}
} codex mcp add raulkivi-comparer-mcp -- uvx comparer-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"raulkivi-comparer-mcp": {
"type": "local",
"command": [
"uvx",
"comparer-mcp"
],
"enabled": true
}
}
} openclaw mcp add raulkivi-comparer-mcp --command uvx --arg comparer-mcp
mcp_servers:
raulkivi-comparer-mcp:
command: "uvx"
args: ["comparer-mcp"] {
"McpServers": {
"raulkivi-comparer-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"comparer-mcp"
]
}
}
} assistant mcp add raulkivi-comparer-mcp -t stdio -c uvx -a comparer-mcp
{
"mcpServers": {
"raulkivi-comparer-mcp": {
"command": "uvx",
"args": [
"comparer-mcp"
]
}
}
} 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.
- 28 Sept 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 71
First indexed and scored.
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 1 Oct 2026 · Analysed pypi/comparer-mcp@0.2.1
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 | raulkivi/sheet-music-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/raulkivi/sheet-music-mcp/.github/workflows/publish.yml@refs/tags/comparer-mcp/v0.2.1 |
| Rekor log index | 2968597368 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1448dda3312eace3b058d643e7836d4322b890c514fee4c60302ecdba40691b7 |
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 50 packages
| Packages resolved | 50 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_musicxml ~132
Full music-aware diff of two MusicXML strings. Returns a structured ComparisonResult with global similarity score, summary statistics, and per-part/measure/note detail.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | Comparison options (docs/architecture.md §8). expand_repeats defaults to false (opt-in — see docs/PLAN.md 'Changed decisions'); normalize_pitch, ignore_articulations, part_filter, measure_range all d… |
| reference_xml | string | yes | Reference MusicXML document as a string |
| target_xml | string | yes | Target MusicXML document as a string, compared against the reference |
No output schema declared.
No examples provided.
compare_musicxml_files ~142
Full music-aware diff of two MusicXML files on disk (.musicxml, .xml, or compressed .mxl). Returns the same structured ComparisonResult as compare_musicxml.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | Comparison options (docs/architecture.md §8). expand_repeats defaults to false (opt-in — see docs/PLAN.md 'Changed decisions'); normalize_pitch, ignore_articulations, part_filter, measure_range all d… |
| reference_path | string | yes | Path to the reference MusicXML/.mxl file |
| target_path | string | yes | Path to the target MusicXML/.mxl file, compared against the reference |
No output schema declared.
No examples provided.
export_annotated_musicxml ~195
Export both scores as MusicXML with per-note color annotations marking the diff (pitch changes, duration changes, substitutions, insertions, deletions). Returns two documents: reference_annotated_musicxml (shows deletions and pre-change values) and target_annotated_musicxml (shows insertions and post-change values). Feed either directly into render-mcp's render_to_pdf or render_to_image to visualize the diff — both take a raw musicxml string.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | Comparison options (docs/architecture.md §8). expand_repeats defaults to false (opt-in — see docs/PLAN.md 'Changed decisions'); normalize_pitch, ignore_articulations, part_filter, measure_range all d… |
| reference_xml | string | yes | Reference MusicXML document as a string |
| target_xml | string | yes | Target MusicXML document as a string, compared against the reference |
No output schema declared.
No examples provided.
generate_comparison_report ~155
Human-readable version comparison report: overall similarity headline, missing/extra parts, missing/extra measures, key/time signature changes, and note-level differences grouped into measure-range summaries (e.g. 'transposed by 3 semitones in measures 17-24').
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | Comparison options (docs/architecture.md §8). expand_repeats defaults to false (opt-in — see docs/PLAN.md 'Changed decisions'); normalize_pitch, ignore_articulations, part_filter, measure_range all d… |
| reference_xml | string | yes | Reference MusicXML document as a string |
| target_xml | string | yes | Target MusicXML document as a string, compared against the reference |
No output schema declared.
No examples provided.
health_check ~51
Check that the server and all its dependencies are working correctly. Runs a self-comparison smoke test and returns a structured status summary. Ask your AI assistant to run this tool to confirm the server is set up correctly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_capabilities ~19
List supported formats and available tools for this server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_changes ~137
List only the note-level differences (operation != MATCH) between two MusicXML strings, optionally filtered to one part and/or a measure range. Useful for targeted queries like 'what changed in the Alto, measures 17-24?'
| Name | Type | Req | Description |
|---|---|---|---|
| measure_range | array | – | [start, end] measure numbers, inclusive. Omit for all measures. |
| part | string | – | Restrict results to this part name (case-insensitive). Omit for all parts. |
| reference_xml | string | yes | Reference MusicXML document as a string |
| target_xml | string | yes | Target MusicXML document as a string, compared against the reference |
No output schema declared.
No examples provided.
quick_similarity ~74
Fast similarity check between two MusicXML strings: returns only the 0.0-1.0 similarity score and summary statistics, without per-note detail.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_xml | string | yes | Reference MusicXML document as a string |
| target_xml | string | yes | Target MusicXML document as a string, compared against the reference |
No output schema declared.
No examples provided.
What is the MusicXML Comparer MCP server?
MusicXML Comparer is an MCP server listed in the public MCP registry as io.github.raulkivi/comparer-mcp. Music-aware, multi-level comparison of two MusicXML files. This page covers its PyPI package (comparer-mcp).
Is the MusicXML Comparer MCP server safe to use?
MusicXML Comparer scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 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.
What tools does the MusicXML Comparer MCP server expose?
MusicXML Comparer exposes 8 tools: compare_musicxml, compare_musicxml_files, quick_similarity, list_changes, generate_comparison_report, and 3 more. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.
Is the MusicXML Comparer MCP server still maintained?
MusicXML Comparer is still listed as active in the MCP registry. We last reached this channel on 1 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 MusicXML Comparer MCP server under?
MusicXML Comparer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.