# Voice To Instrument — Music Utilities (mcpb · voicetoinstrument-1.0.0.mcpb)

Offline BPM timing, musical note frequencies, MIDI numbers and cents calculations.

- Trust score: 45/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `voicetoinstrument-1.0.0.mcpb`: 45/100 (this document), [markdown](https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument.md), [page](https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/stark-ydq/site-mcp-servers/releases/download/v1.0.0/voicetoinstrument-1.0.0.mcpb`
- Transport: `stdio`
- SHA-256: `7f320d62d02d1c5b738a6b3936b444614ea40a71e673cd573cad7dc2d39e5322`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 228 tokens (~76/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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 Voice To Instrument — Music Utilities MCP server?

Voice To Instrument — Music Utilities ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 7f320d62d02d1c5b738a6b3936b444614ea40a71e673cd573cad7dc2d39e5322; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/stark-ydq/site-mcp-servers/releases/download/v1.0.0/voicetoinstrument-1.0.0.mcpb`
- SHA-256: `7f320d62d02d1c5b738a6b3936b444614ea40a71e673cd573cad7dc2d39e5322`

### Verify on macOS / Linux

```bash
echo "7f320d62d02d1c5b738a6b3936b444614ea40a71e673cd573cad7dc2d39e5322  voicetoinstrument-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\voicetoinstrument-1.0.0.mcpb).Hash -eq "7f320d62d02d1c5b738a6b3936b444614ea40a71e673cd573cad7dc2d39e5322"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 45, +1)

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

### 2026-11-02 (score 44, +1)

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

### 2026-10-31 (score 43, +1)

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

### 2026-10-28 (score 42, +1)

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

### 2026-10-26 (score 41, +1)

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

### 2026-10-24 (score 40, +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.

### 2026-10-22 (score 39, +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.

### 2026-10-20 (score 38, +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.

## MCP tools (3)

### `tempo_to_timing` (~58 tokens)

Calculate note and bar durations

Calculate delay/sync note durations and total bar duration from quarter-note BPM. Includes dotted eighth and eighth-note triplet timing.

Input parameters:

- `bars` (integer)
- `beatsPerBar` (integer)
- `bpm` (number, required)

### `note_to_frequency` (~64 tokens)

Convert note to frequency

Convert a scientific pitch name such as A4, C#4 or Bb3 to MIDI note number and frequency. Supports enharmonic spelling and adjustable A4 tuning.

Input parameters:

- `note` (string, required)
- `tuningHz` (number): Frequency of A4 in Hz.

### `frequency_to_note` (~57 tokens)

Find nearest musical note

Find the nearest equal-tempered MIDI note and cents deviation for an input frequency. A positive cents value means the input is sharp.

Input parameters:

- `frequencyHz` (number, required)
- `tuningHz` (number): Frequency of A4 in Hz.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument#diagnostics

## Score history

- 2026-11-05: 45
- 2026-11-04: 45
- 2026-11-03: 44
- 2026-11-02: 44
- 2026-11-01: 43
- 2026-10-31: 43
- 2026-10-30: 42
- 2026-10-29: 42
- 2026-10-28: 42
- 2026-10-27: 41
- 2026-10-26: 41
- 2026-10-25: 40
- 2026-10-24: 40
- 2026-10-23: 39
- 2026-10-22: 39
- 2026-10-21: 38
- 2026-10-20: 38
- 2026-10-19: 37
- 2026-10-18: 37
- 2026-10-17: 36

## Common questions

### What is the Voice To Instrument — Music Utilities MCP server?

Voice To Instrument — Music Utilities is an MCP server listed in the public MCP registry as io.github.stark-ydq/voicetoinstrument. Offline BPM timing, musical note frequencies, MIDI numbers and cents calculations. This page covers its MCPB bundle (https://github.com/stark-ydq/site-mcp-servers/releases/download/v1.0.0/voicetoinstrument-1.0.0.mcpb).

### Is the Voice To Instrument — Music Utilities MCP server safe to use?

Voice To Instrument — Music Utilities scores 45 out of 100 on VerifyMCP. 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 Voice To Instrument — Music Utilities MCP server expose?

Voice To Instrument — Music Utilities exposes 3 tools: tempo_to_timing, note_to_frequency, frequency_to_note. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.

### What licence is the Voice To Instrument — Music Utilities MCP server under?

Voice To Instrument — Music Utilities declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Voice To Instrument — Music Utilities MCP server?

VerifyMCP ran 12 checks on Voice To Instrument — Music Utilities, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Voice To Instrument — Music Utilities: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/stark-ydq/site-mcp-servers
- Website: https://voicetoinstrument.com/
- Changelog RSS feed: https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument.xml
- Changelog JSON feed: https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument.json
- HTML version of this page: https://verifymcp.io/servers/stark-ydq-voicetoinstrument/voicetoinstrument