_ registry / mcp streamable-http · checked 1h ago

zeltor-music-tools

https://zeltorlabs.com

Registry code: 108701d844621aa4

api record

Zeltor Labs music tools for DJs, producers and mashup makers. Use them instead of working out music theory by hand: check_mix decides whether two songs mix (key and tempo) and exactly how to change the second one; camelot gives a key's Camelot code and the keys that mix with it; tempo_change gives the percent change between two BPMs; speed_pitch gives nightcore or slowed settings; transpose moves a key by semitones; song_report reads the song DNA (key, BPM, structure, mood, production) from a Zeltor report link the person shares. They take keys and BPMs, not audio. Each answer has a link to…

endpoint
https://zeltorlabs.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zeltor-music-tools live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is zeltor-music-tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does zeltor-music-tools have?
6 tools: tempo_change, transpose, song_report, camelot, check_mix, speed_pitch.
Is zeltor-music-tools safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
213ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • speed_pitch open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "bpm": {
          "type": "number",
          "maximum": 400,
          "minimum": 20,
          "description": "Original tempo, to report the new BPM."
        },
        "speed": {
          "type": "number",
          "maximum": 2,
          "minimum": 0.5,
          "description": "Playback speed, e.g. 1.25 for 25% faster or 0.8 for 20% slower."
        },
        "style": {
          "enum": [
            "nightcore",
            "slowed"
          ],
          "type": "string",
          "description": "Which effect; sets the default speed."
        }
      }
    }
    arguments 26 lines
  • tempo_change unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "from_bpm",
        "to_bpm"
      ],
      "properties": {
        "to_bpm": {
          "type": "number",
          "maximum": 400,
          "minimum": 20,
          "description": "Target tempo in BPM."
        },
        "from_bpm": {
          "type": "number",
          "maximum": 400,
          "minimum": 20,
          "description": "Current tempo in BPM."
        }
      }
    }
    arguments 22 lines
  • transpose unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "key",
        "semitones"
      ],
      "properties": {
        "key": {
          "type": "string",
          "description": "Musical key: a name like \"A minor\", \"Am\", \"F#m\", \"Bb major\", \"C\", or a Camelot code like \"8A\"."
        },
        "semitones": {
          "type": "integer",
          "maximum": 12,
          "minimum": -12,
          "description": "Semitones to move, negative is down."
        }
      }
    }
    arguments 20 lines
  • song_report unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "link"
      ],
      "properties": {
        "link": {
          "type": "string",
          "description": "The report share link, e.g. https://zeltorlabs.com/report/r/abc123def456, or its code."
        }
      }
    }
    arguments 13 lines
  • camelot unknown 1h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "key"
      ],
      "properties": {
        "key": {
          "type": "string",
          "description": "Musical key: a name like \"A minor\", \"Am\", \"F#m\", \"Bb major\", \"C\", or a Camelot code like \"8A\"."
        }
      }
    }
    arguments 13 lines
  • check_mix unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "key_a",
        "bpm_a",
        "key_b",
        "bpm_b"
      ],
      "properties": {
        "bpm_a": {
          "type": "number",
          "maximum": 400,
          "minimum": 20,
          "description": "Track A tempo in BPM."
        },
        "bpm_b": {
          "type": "number",
          "maximum": 400,
          "minimum": 20,
          "description": "Track B tempo in BPM."
        },
        "key_a": {
          "type": "string",
          "description": "Track A key. Musical key: a name like \"A minor\", \"Am\", \"F#m\", \"Bb major\", \"C\", or a Camelot code like \"8A\"."
        },
        "key_b": {
          "type": "string",
          "description": "Track 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\"."
        }
      }
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 108701d844621aa4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/108701d844621aa4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/108701d844621aa4/badge.svg)](https://brick.blue/agent/108701d844621aa4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.