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.

Zovo Chord Chart Maker

REMOTE · CHORD-CHARTS.ZOVO.ONE

Make a guitar chord chart printable in seconds: send a list of chords or paste a song with chords.

+3 this week 78 Trust /100

Last scanned (18 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • 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 1330 tokens (~443/item across 3 items; 2 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 Management43
  • Stability observed for 13 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

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

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

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

  • 13 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.

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

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 72

    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 21 Nov 2026 · Probed https://chord-charts.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 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.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-charts.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS 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-charts.zovo.one/mcp Verified 200
http (plaintext) http://chord-charts.zovo.one/mcp HTTPS enforced 301 https://chord-charts.zovo.one/mcp
MCP tools · 2 exposed · ~1,214 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_chord_fingerings ~465

Use this when the user asks how to play a chord on guitar, ukulele or piano ("how do I play F#m7b5 on ukulele", "easier way to play F"). Pass the chord names in chords. Returns up to 4 positions per chord (default 3), lowest on the neck first, with the frets, finger numbers and the note on each string, checked note by note, plus a PDF of the diagrams. For a whole song sheet use generate_chord_chart. Does not do alternate tunings or bass.

NameTypeReqDescription
capo––Guitar or ukulele capo fret 0-9, or "auto" for the easiest open shapes. Default 0.
capo_modestring–How chord names relate to the capo: "shapes" (default with a capo number) means the names are the shapes you finger, as chord sheets that say "Capo 2" write them; each diagram says which chord sounds…
chordsarray–Chord names, one per item, e.g. ["G", "Em", "C", "D7", "F#m7b5", "C/E"]. Convert a pasted song or a photo of a chord sheet into this list of the chords it uses. Repeats are drawn once. Up to 64 diffe…
instrumentstring–guitar (standard tuning E A D G B E, default), ukulele (G C E A) or piano (keyboard diagrams). Several, e.g. "guitar and ukulele", give one PDF with each instrument on its own pages.
left_handed––true for mirrored left-handed diagrams (low string on the right). Default false.
paperstring–letter (US Letter, default) or a4.
shapes_per_chord––Positions per chord, 1 to 4 (default 3).
titlestring–Heading printed on the sheet, e.g. the song name "Wonderwall" or "Beginner chords". Default "Chord chart".
NameTypeReqDescription
caponumberyes–
chord_countnumberyes–
diagram_countnumberyes–
diagramsarrayyes–
diagrams_shownobject––
downloadsobjectyes–
instrumentstringyes–
left_handedbooleanyes–
notesarrayyes–
pagesnumberyes–
paperstringyes–
per_pagenumberyes–
skippedarrayyes–
titlestringyes–
transpose_semitonesnumberyes–
tuningstringyes–

No examples provided.

generate_chord_chart ~749

Use this when the user wants a guitar chord chart printable, a ukulele chord chart, a piano chord chart, or chord diagrams for a song. Convert a pasted song or an uploaded photo of a chord sheet into the chords list (chord names like G, Em, F#m7, C/E); use chord_sheet only to pass raw pasted text. Draws one diagram per different chord as a print-ready PDF (US Letter or A4, 6, 12 or 24 per page) for guitar in standard tuning, ukulele (G C E A) or piano, with optional transpose, capo (or "auto"), and left-handed diagrams. Guitar and ukulele shapes are checked by their notes. Does not do alternate tunings, bass, tabs or notation.

NameTypeReqDescription
capo––Guitar or ukulele capo fret 0-9, or "auto" to pick the capo with the easiest open shapes. Default 0. A "Capo 2" line in chord_sheet is read too.
capo_modestring–How chord names relate to the capo: "shapes" (default with a capo number) means the names are the shapes you finger, as chord sheets that say "Capo 2" write them; each diagram says which chord sounds…
chord_sheetstring–Fallback: a pasted chord sheet (chords over lyrics, or inline [Am] chords). Every chord in it is drawn once, in order of first use. Example: "G Em\nHello my friend\nC D\nHow are you".
chordsarray–Chord names, one per item, e.g. ["G", "Em", "C", "D7", "F#m7b5", "C/E"]. Convert a pasted song or a photo of a chord sheet into this list of the chords it uses. Repeats are drawn once. Up to 64 diffe…
from_keystring–The song's current key when to_key is used, e.g. E. Optional.
instrumentstring–guitar (standard tuning E A D G B E, default), ukulele (G C E A) or piano (keyboard diagrams). Several, e.g. "guitar and ukulele", give one PDF with each instrument on its own pages.
left_handed––true for mirrored left-handed diagrams (low string on the right). Default false.
paperstring–letter (US Letter, default) or a4.
per_page––Diagrams per page: 6, 12 (default) or 24.
shapes_per_chord––How many positions to draw per chord, 1 (default) to 4, lowest on the neck first.
show_finger_numbers––Print finger numbers in the dots (default true).
titlestring–Heading printed on the sheet, e.g. the song name "Wonderwall" or "Beginner chords". Default "Chord chart".
to_keystring–Transpose to this key instead of giving semitones, e.g. G or Bbm. The original key is from_key, a Key: line in the sheet, or the first chord.
transpose_semitones––Shift every chord up (positive) or down (negative) by this many semitones before drawing, e.g. 2 or -3. Default 0.
NameTypeReqDescription
caponumberyes–
chord_countnumberyes–
diagram_countnumberyes–
diagramsarrayyes–
diagrams_shownobject––
downloadsobjectyes–
instrumentstringyes–
left_handedbooleanyes–
notesarrayyes–
pagesnumberyes–
paperstringyes–
per_pagenumberyes–
skippedarrayyes–
titlestringyes–
transpose_semitonesnumberyes–
tuningstringyes–

No examples provided.

Install

How do I install the Zovo Chord Chart Maker MCP server?

Zovo Chord Chart Maker is a hosted endpoint at https://chord-charts.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-charts.zovo.one

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

What is the Zovo Chord Chart Maker MCP server?

Zovo Chord Chart Maker is an MCP server listed in the public MCP registry as io.github.theluckystrike/chord-charts. Make a guitar chord chart printable in seconds: send a list of chords or paste a song with chords. This page covers its hosted endpoint (https://chord-charts.zovo.one/mcp).

Is the Zovo Chord Chart Maker MCP server safe to use?

Zovo Chord Chart Maker scores 78 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 Zovo Chord Chart Maker MCP server expose?

Zovo Chord Chart Maker exposes 2 tools: generate_chord_chart, find_chord_fingerings. Their descriptions and schemas cost roughly 1,214 tokens of context every time the server is loaded.

Does the Zovo Chord Chart Maker MCP server require authentication?

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

Is the Zovo Chord Chart Maker MCP server still maintained?

Zovo Chord Chart Maker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Zovo Chord Chart Maker MCP server?

VerifyMCP ran 14 checks on Zovo Chord Chart Maker, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.