Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Fretwork Guitar Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Guitar chords from frets, chord shapes, transposing, capo, scales, song keys and practice plans.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fretwork-guitar-tools-mcp https://mcp.guitarfretwork.com/mcp
# 2 — ask your agent for something these tools do
# identify_chord, get_chord_shapes, transpose_chords and 6 more
Fretwork Guitar Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http fretwork-guitar-tools-mcp https://mcp.guitarfretwork.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Names the chord a guitarist is holding from the fret on each string (standard tuning), lists its notes and returns a chord diagram. Use when someone asks "what chord is this?" and gives frets like x32010, 3-2-0-0-0-3 or "0 2 2 1 0 0" (low E string first; x = muted string).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| frets | string | yes | Six frets from the low E string to the high e string. Use x for a muted string, 0 for open. Examples: "x32010", "3 2 0 0 0 3", "8-10-10-9-8-8". |
Returns playable guitar shapes for a chord name (open position and movable barre shapes), with frets, fingering where known, the notes in the chord and a text chord diagram. Handles major, minor, 7, maj7, m7, sus2, sus4, add9, 6, m6, 9, dim, m7b5, dim7, aug, power chords and slash chords such as G/B.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chord | string | yes | Chord name, for example "F", "Bm", "F#m7", "Cadd9", "Bbmaj7", "G/B", "E5". |
Moves a song's chords to a new key. Accepts a chord list, a chord chart with lyrics (chord lines are transposed, lyric lines are kept), or inline [C] chords. Give either from_key and to_key, or a number of semitones. Also suggests capo positions that let the guitarist keep easy open shapes in the new key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The chords or chord chart, e.g. "G D Em C" or a chart with chord lines above lyrics. |
| from_key | string | no | Current key, e.g. "G" or "A minor". Optional if semitones is given; if missing, the first chord is used. |
| to_key | string | no | Target key, e.g. "Bb" or "C minor". |
| semitones | integer | no | Semitones to move (+ up, - down). Used when to_key is not given. |
| spelling | string | no | Accidentals for the result. auto follows the target key. |
Works out where to put a capo. Give the key you want to sound in (for example to match a singer or a recording) and, optionally, the open-chord key you want to play shapes in. Returns the capo fret, or the easy options if no shape key is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sounding_key | string | yes | The key the music should sound in, e.g. "Bb", "F# minor". |
| shape_key | string | no | Optional. The key whose open chord shapes you want to play, e.g. "G" or "Em". |
Gives the notes of a scale in any key and where they fall on the guitar fretboard (standard tuning), string by string, with root notes marked. Scales: major, natural minor, harmonic minor, melodic minor, the seven modes (dorian, phrygian, lydian, mixolydian, locrian), minor pentatonic, major pentatonic, blues and major blues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| root | string | yes | Key note, e.g. "A", "F#", "Bb". |
| scale | string | yes | Scale type, e.g. "minor pentatonic", "major", "blues", "dorian". |
| from_fret | integer | no | Lowest fret to show (default 0). |
| to_fret | integer | no | Highest fret to show (default 12). |
Works out the most likely key of a song from its chord progression, gives each chord its Roman numeral, lists the other chords that belong to the key, and suggests which scale to solo with.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chords | string | yes | The chords in order, e.g. "G D Em C" or "Am F C G". |
Finds songs a guitarist can play with the chords they already know, from Fretwork's free library of 87 public-domain folk, gospel, blues, campfire and Christmas songs. Each song has chords, key, time signature, level and a free play-along page. Can also list songs that need just one or two new chords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chords_known | string | yes | Chords the player can already play, e.g. "G C D Em". |
| max_new_chords | integer | no | Also include songs needing up to this many extra chords (default 0). |
| level | string | no | Filter by level (default any). |
| time_signature | string | no | Filter by time signature (default any). |
A quick self-assessment that places a guitarist on Fretwork's 10-stage learning path (Stage 0 Getting Started to Stage 9 Artistry) from yes/no answers to up to nine questions about what they can already play, and says what to learn next. The questions build on each other, so answers are read in order up to the first "no". Called with no answers, it returns the nine questions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tune_and_clean_notes | boolean | no | Can you tune the guitar and play a clean note on every string? |
| change_chords_in_time | boolean | no | Can you change between basic open chords (like G, C, D, Em) in time and play a whole simple song? |
| four_chord_song_with_pattern | boolean | no | Can you play a four-chord song start to finish with a strumming pattern? |
| riff_blues_and_short_solo | boolean | no | Can you play a riff, a 12-bar blues and a short solo of your own? |
| barre_chords_and_16th_groove | boolean | no | Can you play any major or minor barre chord and hold a 16th-note strumming groove? |
| keys_and_pentatonic_anywhere | boolean | no | Can you name the chords in any key and solo with the pentatonic scale anywhere on the neck? |
| bends_vibrato_full_solo | boolean | no | Can you play a solo with in-tune bends, vibrato and clear phrases? |
| play_the_changes | boolean | no | Can you solo over a progression and target the chord tones as the chords change? |
| transcribe_and_tension | boolean | no | Can you transcribe a full solo and improvise with tension and release? |
Builds a daily guitar practice routine and a 4-week focus plan sized to the player's level, the minutes they have each day and their goal (songs, strumming, fingerpicking, lead, barre chords, theory or general). Uses Fretwork's 10-stage curriculum, where stage 0 is for someone who has never played.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stage | integer | no | Fretwork stage 0–9 (0 = never played, 1 = first chords, 2 = rhythm & songs, 3 = riffs & first solos, 4 = barre chords, 5 = scales & keys, 6 = lead guitar, 7–9 = advanced). |
| minutes_per_day | integer | no | Practice minutes per day (default 20). |
| days_per_week | integer | no | Practice days per week (default 5). |
| goal | string | no | Main goal (default general). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Fretwork Guitar Tools or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| identify_chord | no tags | |
| get_chord_shapes | no tags | |
| transpose_chords | no tags | |
| find_capo | no tags | |
| get_scale | no tags | |
| find_key | no tags | |
| find_songs | no tags | |
| guitar_level_check | no tags | |
| make_practice_plan | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Fretwork Guitar Tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.