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.

Keyshift Chord Transposer

REMOTE · CHORD-TRANSPOSER.ZOVO.ONE

Change keys and capo shapes

74 Trust /100

Last scanned (5 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 23 Oct 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 Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 839 tokens (~209/item across 4 items; 3 tools + 1 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 Management3
  • Stability observed for 1 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
  • Supports UI / widget rendering.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.

  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 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 23 Oct 2026 · Probed https://chord-transposer.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 3cc78dbfbb77ff4b0eff4c8d23ab1c39
SANs: zovo.one, chord-transposer.zovo.one, *.chord-transposer.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of chord-transposer.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
zovo.one. 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=15552000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chord-transposer.zovo.one/mcp Verified 200
http (plaintext) http://chord-transposer.zovo.one/mcp HTTPS enforced 301 https://chord-transposer.zovo.one/mcp
MCP tools · 3 exposed · ~743 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
find_capo_options ~149

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.

NameTypeReqDescription
chordsarray–Chord list of 1 to 100 names; for example ["D", "G", "A", "Bm"]. Give this instead of key.
keystring–Sounding key, for example D or Am. Give key or chords, not both.
NameTypeReqDescription
chord_countnumberyes–
keystring|nullyes–
kindstringyes–
optionsarrayyes–
shapes_truncatedbooleanyes–

No examples provided.

show_chord_sheet ~230

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 Latin-only Courier PDF. Chord names only; does not process audio, tablature or staff notation. Key estimates can be wrong for songs that change key.

NameTypeReqDescription
from_keystring–Origin key; for example C or Am. Required with to_key; otherwise the header or first and last chords give a key estimate.
sheetstringyesChord sheet of 1 to 12,000 characters, with chords above lyrics or inline; for example C G\nLanterns glow, or [Am]Lantern [F]garden.
spellingstring–Chord spelling; for example auto follows the target key, while sharps forces F# instead of Gb for consistent round trips.
titlestring–PDF title up to 80 Western Latin characters; for example Lantern Garden.
NameTypeReqDescription
capo–yes–
chord_countnumberyes–
chords_usedarrayyes–
downloadsobjectyes–
from_keystringyes–
gapsarrayyes–
in_keyarrayyes–
key_estimatedbooleanyes–
kindstringyes–
lyric_linesnumberyes–
modestringyes–
notesarrayyes–
semitonesnumberyes–
to_keystringyes–
unique_chord_countnumberyes–

No examples provided.

transpose_chords ~364

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 Latin-only Courier PDF. Chord names only; does not process audio, tablature or staff notation. Key estimates can be wrong for songs that change key.

NameTypeReqDescription
capo_fretinteger–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.
from_keystring–Origin key; for example C or Am. Required with to_key; otherwise the header or first and last chords give a key estimate.
semitonesinteger–Signed shift from -11 to +11; for example 2 moves up two semitones. Give one transposition choice.
sheetstringyesChord sheet of 1 to 12,000 characters, with chords above lyrics or inline; for example C G\nLanterns glow, or [Am]Lantern [F]garden.
spellingstring–Chord spelling; for example auto follows the target key, while sharps forces F# instead of Gb for consistent round trips.
titlestring–PDF title up to 80 Western Latin characters; for example Lantern Garden.
to_keystring–Target key paired with from_key; for example from_key C and to_key F. Use this instead of semitones or capo_fret.
NameTypeReqDescription
capo–yes–
chord_countnumberyes–
chords_usedarrayyes–
downloadsobjectyes–
from_keystringyes–
gapsarrayyes–
in_keyarrayyes–
key_estimatedbooleanyes–
kindstringyes–
lyric_linesnumberyes–
modestringyes–
notesarrayyes–
semitonesnumberyes–
to_keystringyes–
unique_chord_countnumberyes–

No examples provided.

Install

How do I install the Keyshift Chord Transposer MCP server?

Keyshift Chord Transposer is a hosted endpoint at https://chord-transposer.zovo.one/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 · chord-transposer.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-chord-transposer 'https://chord-transposer.zovo.one/mcp'
Common questions

What is the Keyshift Chord Transposer MCP server?

Keyshift Chord Transposer is an MCP server listed in the public MCP registry as io.github.theluckystrike/chord-transposer. Change keys and capo shapes. This page covers its hosted endpoint (https://chord-transposer.zovo.one/mcp).

Is the Keyshift Chord Transposer MCP server safe to use?

Keyshift Chord Transposer scores 74 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 Keyshift Chord Transposer MCP server expose?

Keyshift Chord Transposer exposes 3 tools: transpose_chords, find_capo_options, show_chord_sheet. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.

Does the Keyshift Chord Transposer MCP server require authentication?

No. We connected to Keyshift Chord Transposer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Keyshift Chord Transposer MCP server still maintained?

Keyshift Chord Transposer is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.