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.

MusicXML Renderer

PYPI · RENDER-MCP · SCANNED OCT 1

Renders MusicXML scores to PDF, PNG or SVG

Available components

65 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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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 39 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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 228 tokens (~57/item across 4 items; 4 tools + 0 resources), lean.Pass
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

Install

How do I install the MusicXML Renderer MCP server?

MusicXML Renderer runs locally as a PyPI package, launched with uvx render-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 · render-mcp

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

  • 1 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Sept 26 +25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Sept 26 70

    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 1 Oct 2026 · Analysed pypi/render-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/render-mcp/v0.2.1
Rekor log index 2968597293
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:a1624eff5d618565ea33556375e961dddf724cc6c52e3801c75796991d6f53ad

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 39 packages
Packages resolved 39
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~228 tokens

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 →

Tool Tokens
health_check ~31

Check whether all runtime dependencies are available and the server is ready to render scores. Returns a human-readable status summary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_capabilities ~21

List supported formats and available backends for this render server

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

render_to_image ~125

Render a single page of a MusicXML score to PNG or SVG

NameTypeReqDescription
dpiinteger–Resolution for PNG output in dots per inch (default: 150, range: 72–600)
formatstring–Output format: 'png' or 'svg' (default: 'png')
musicxmlstringyesMusicXML document as a string
output_pathstring–Path to write image file (auto-generated if omitted)
pageinteger–Page number to render, 1-indexed (default: 1)

No output schema declared.

No examples provided.

render_to_pdf ~51

Render a MusicXML score to a PDF file

NameTypeReqDescription
musicxmlstringyesMusicXML document as a string
output_pathstring–Path to write PDF file (auto-generated if omitted)

No output schema declared.

No examples provided.

Common questions

What is the MusicXML Renderer MCP server?

MusicXML Renderer is an MCP server listed in the public MCP registry as io.github.raulkivi/render-mcp. Renders MusicXML scores to PDF, PNG or SVG. This page covers its PyPI package (render-mcp).

Is the MusicXML Renderer MCP server safe to use?

MusicXML Renderer scores 65 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 Renderer MCP server expose?

MusicXML Renderer exposes 4 tools: render_to_pdf, render_to_image, list_capabilities, health_check. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.

Is the MusicXML Renderer MCP server still maintained?

MusicXML Renderer 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 Renderer MCP server under?

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