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

chord-transposer

https://chord-transposer.zovo.one

Registry code: 0b023c4190c9663d

api record

Use transpose_chords for a shift, named key pair or capo fret; find_capo_options for frets 0 to 9; show_chord_sheet for an interactive sheet. Full lyrics and sheets are only in widget meta and the stateless sealed PDF link. Key estimates can be wrong for songs that change key. The monospaced PDF prints Latin, Greek, Cyrillic, Vietnamese, Chinese, Japanese and Korean lyrics; right-to-left scripts and emoji get a note instead of a PDF.

endpoint
https://chord-transposer.zovo.one/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 chord-transposer live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is chord-transposer free to use?
Yes — the hub reached it with no key and no payment.
What tools does chord-transposer have?
3 tools: find_capo_options, show_chord_sheet, transpose_chords.
Is chord-transposer 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
363ms

last good check

priced tools
0

of 3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • find_capo_options unknown 1h ago

    Use this when you want a capo chart or capo calculator for a sounding key or chord list. Returns frets 0 to 9, the shapes to play and easy open chord counts. Supply one key or 1 to 100 chord names, each up to 80 characters. Does not process audio, tablature or staff notation; ease counts chord names, not fingering variations.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "key": {
          "type": "string",
          "maxLength": 24,
          "description": "Sounding key, for example D or Am. Give key or chords, not both."
        },
        "chords": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 80
          },
          "maxItems": 100,
          "description": "Chord list of 1 to 100 names; for example [\"D\", \"G\", \"A\", \"Bm\"]. Give this instead of key."
        }
      }
    }
    arguments 20 lines
  • show_chord_sheet unknown 1h ago

    Use this when you want a live chord sheet with -1 and +1 semitone controls. Accepts 1 to 12,000 characters in chord-line or ChordPro format; controls call transpose_chords. Shows the original key and chord counts plus a monospaced PDF. Chord names only; does not process audio, tablature or staff notation. Key estimates can be wrong for songs that change key.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sheet"
      ],
      "properties": {
        "sheet": {
          "type": "string",
          "description": "Chord sheet of 1 to 12,000 characters, with chords above lyrics or inline; for example C    G\\nLanterns glow, or [Am]Lantern [F]garden."
        },
        "title": {
          "type": "string",
          "maxLength": 80,
          "description": "PDF title up to 80 characters; for example Lantern Garden."
        },
        "from_key": {
          "type": "string",
          "maxLength": 24,
          "description": "Origin key; for example C or Am. Required with to_key; otherwise the header or first and last chords give a key estimate."
        },
        "spelling": {
          "enum": [
            "auto",
            "sharps",
            "flats"
          ],
          "type": "string",
          "description": "Chord spelling; for example auto follows the target key, while sharps forces F# instead of Gb for consistent round trips."
        }
      }
    }
    arguments 32 lines
  • transpose_chords unknown 1h ago

    Use this when you want to transpose chords or change the key of a song. Accepts a sheet up to 12,000 characters, chords above lyrics or ChordPro brackets; choose semitones -11 to +11, from_key with to_key, or capo_fret 0 to 9. Returns key change, chord mapping, widget sheet and a monospaced PDF. Chord names only; does not process audio, tablature or staff notation. Key estimates can be wrong for songs that change key.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "sheet"
      ],
      "properties": {
        "sheet": {
          "type": "string",
          "description": "Chord sheet of 1 to 12,000 characters, with chords above lyrics or inline; for example C    G\\nLanterns glow, or [Am]Lantern [F]garden."
        },
        "title": {
          "type": "string",
          "maxLength": 80,
          "description": "PDF title up to 80 characters; for example Lantern Garden."
        },
        "to_key": {
          "type": "string",
          "maxLength": 24,
          "description": "Target key paired with from_key; for example from_key C and to_key F. Use this instead of semitones or capo_fret."
        },
        "from_key": {
          "type": "string",
          "maxLength": 24,
          "description": "Origin key; for example C or Am. Required with to_key; otherwise the header or first and last chords give a key estimate."
        },
        "spelling": {
          "enum": [
            "auto",
            "sharps",
            "flats"
          ],
          "type": "string",
          "description": "Chord spelling; for example auto follows the target key, while sharps forces F# instead of Gb for consistent round trips."
        },
        "capo_fret": {
          "type": "integer",
          "maximum": 9,
          "minimum": 0,
          "description": "Capo fret from 0 to 9; for example 2 returns shapes two semitones below the sounding key. Use this instead of semitones or to_key."
        },
        "semitones": {
          "type": "integer",
          "maximum": 11,
          "minimum": -11,
          "description": "Signed shift from -11 to +11; for example 2 moves up two semitones. Give one transposition choice."
        }
      }
    }
    arguments 49 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 0b023c4190c9663d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0b023c4190c9663d/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/0b023c4190c9663d/badge.svg)](https://brick.blue/agent/0b023c4190c9663d?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
70%

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.

_ also on zovo.one 12 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

4 more sit on this domain. All of them.