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.

Zeltor Music Tools

REMOTE · ZELTORLABS.COM

Check if two songs mix (Camelot key, BPM), read shared song DNA reports, tempo and nightcore math.

Available components

75 Trust /100

Last scanned (43 minutes ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 952 tokens (~158/item across 6 items; 6 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +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.

  • 2 Nov 26 +1

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

  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 73

    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 5 Nov 2026 · Probed https://zeltorlabs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.zeltorlabs.com CN=YR1,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 RSA 2048 SHA256-RSA 6314fc4219c78c8ca30716b81d48381d227
SANs: *.zeltorlabs.com, zeltorlabs.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of zeltorlabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
zeltorlabs.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://zeltorlabs.com/mcp Verified 200
http (plaintext) http://zeltorlabs.com/mcp HTTPS enforced 308 https://zeltorlabs.com/mcp
MCP tools · 6 exposed · ~771 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
camelot ~85

Gives the Camelot wheel code for a key and the three other keys that mix cleanly with it (one step either way with the same letter, and the relative major or minor).

NameTypeReqDescription
keystringyesMusical key: a name like "A minor", "Am", "F#m", "Bb major", "C", or a Camelot code like "8A".

No output schema declared.

No examples provided.

check_mix ~218

Decides whether two songs will mix well, from their keys and BPMs, using the Camelot wheel and DJ tempo limits (about 3% sounds natural, up to about 16% is usable, half and double time count). Returns a verdict, the tempo change in percent and the target BPM for track B, the smallest key shift in semitones if the keys clash, and a link to make the matched audio.

NameTypeReqDescription
bpm_anumberyesTrack A tempo in BPM.
bpm_bnumberyesTrack B tempo in BPM.
key_astringyesTrack A key. Musical key: a name like "A minor", "Am", "F#m", "Bb major", "C", or a Camelot code like "8A".
key_bstringyesTrack B key (the one that would be changed). Musical key: a name like "A minor", "Am", "F#m", "Bb major", "C", or a Camelot code like "8A".

No output schema declared.

No examples provided.

song_report ~170

Reads the song DNA from a MusicMind report the person made on zeltorlabs.com and shared: key and Camelot code with the keys that mix with it, BPM, genre mix, section structure with energy, and production DNA (energy profile, mood, arrangement density, compression, biggest moments). Takes the share link (https://zeltorlabs.com/report/r/<code>) or its code. Use the key and BPM with check_mix to compare it with another song. If the person has no report yet, they can make one free at https://zeltorlabs.com/analyze (the audio is analyzed in their browser).

NameTypeReqDescription
linkstringyesThe report share link, e.g. https://zeltorlabs.com/report/r/abc123def456, or its code.

No output schema declared.

No examples provided.

speed_pitch ~127

For a nightcore (faster and higher) or slowed (slower and lower) version: the pitch change in semitones for a speed, the new BPM if given, and typical settings. Defaults: nightcore 1.25x, slowed 0.80x.

NameTypeReqDescription
bpmnumber–Original tempo, to report the new BPM.
speednumber–Playback speed, e.g. 1.25 for 25% faster or 0.8 for 20% slower.
stylestring–Which effect; sets the default speed.

No output schema declared.

No examples provided.

tempo_change ~74

Percent change and playback rate to go from one BPM to another, how noticeable it will sound, the pitch change if it is not time-stretched, and the half and double time of the target.

NameTypeReqDescription
from_bpmnumberyesCurrent tempo in BPM.
to_bpmnumberyesTarget tempo in BPM.

No output schema declared.

No examples provided.

transpose ~97

Moves a key up or down by semitones and gives the new key name and Camelot code, with a note on how natural the shift will sound.

NameTypeReqDescription
keystringyesMusical key: a name like "A minor", "Am", "F#m", "Bb major", "C", or a Camelot code like "8A".
semitonesintegeryesSemitones to move, negative is down.

No output schema declared.

No examples provided.

Install

How do I install the Zeltor Music Tools MCP server?

Zeltor Music Tools is a hosted endpoint at https://zeltorlabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · zeltorlabs.com

# add to Claude Code
claude mcp add --transport http com-zeltorlabs-music-tools 'https://zeltorlabs.com/mcp'
Common questions

What is the Zeltor Music Tools MCP server?

Zeltor Music Tools is an MCP server listed in the public MCP registry as com.zeltorlabs/music-tools. Check if two songs mix (Camelot key, BPM), read shared song DNA reports, tempo and nightcore math. This page covers its hosted endpoint (https://zeltorlabs.com/mcp).

Is the Zeltor Music Tools MCP server safe to use?

Zeltor Music Tools scores 75 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 Zeltor Music Tools MCP server expose?

Zeltor Music Tools exposes 6 tools: check_mix, camelot, tempo_change, speed_pitch, transpose, song_report. Their descriptions and schemas cost roughly 771 tokens of context every time the server is loaded.

Does the Zeltor Music Tools MCP server require authentication?

No. We connected to Zeltor Music Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zeltor Music Tools MCP server still maintained?

Zeltor Music Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.