Skip to content

Fretwork Guitar Tools MCP server

com.guitarfretwork/fretworkguitarfretwork.comstreamable-httpv1.0.1Scanned

Guitar chords from frets, chord shapes, transposing, capo, scales, song keys and practice plans.

9 tools: 4 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Fretwork Guitar Tools MCP server can do

The Fretwork Guitar Tools MCP server is published by guitarfretwork.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: identify_chord, transpose_chords, guitar_level_check and make_practice_plan), but cannot delete data. 5 tools only read.

2 tools read private data (get_chord_shapes and get_scale).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 4Claude Code: ask
  • guitar_level_checkA 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a guitarist's level
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • identify_chordNames the chord a guitarist is holding from the fret on each string (standard tuning), lists its notes and returns a chord diagram.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Identify a guitar chord
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • make_practice_planBuilds 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, ba…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Make a guitar practice plan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • transpose_chordsMoves a song's chords to a new key.1 finding

    Why it is in this group

    • The description's first verb is "move": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "transpose_chords" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Transpose guitar chords to a new key
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • find_capoWorks out where to put a capo.No findings

    Why it is in this group

    • The name "find_capo" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find the capo position for a key
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_keyWorks 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 s…No findings

    Why it is in this group

    • The name "find_key" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find the key of a song from its chords
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_songsFinds 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.No findings

    Why it is in this group

    • The name "find_songs" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find songs to play with the chords you know
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_chord_shapesReturns 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_chord_shapes" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show how to play a guitar chord
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scaleGives 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_scale" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Show a guitar scale on the fretboard
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:23 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.guitarfretwork.com/mcp: tools/list returned 9 tools to an anonymous client, including identify_chord (write), transpose_chords (write), guitar_level_check (write), make_practice_plan (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "transpose_chords" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "move": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http fretwork https://mcp.guitarfretwork.com/mcp
claude mcp add --transport http fretwork https://mcp.guitarfretwork.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fretwork__get_chord_shapes",
      "mcp__fretwork__find_capo",
      "mcp__fretwork__get_scale",
      "mcp__fretwork__find_key",
      "mcp__fretwork__find_songs"
    ],
    "ask": [
      "mcp__fretwork__identify_chord",
      "mcp__fretwork__transpose_chords",
      "mcp__fretwork__guitar_level_check",
      "mcp__fretwork__make_practice_plan"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fretwork. Review it before you use it.

Capability tags behind 2 rules
  • mcp__fretwork__get_chord_shapes private-data
  • mcp__fretwork__get_scale private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.guitarfretwork/fretwork/verify?hash=79deda6cb2d22ee9b2d51c27797723de256e74282da47705500c85bd95f1a7e7" | jq -e '.changed == false'

Pinned hash 79deda6cb2d2, from Nov 10, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.guitarfretwork/fretwork/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.guitarfretwork/fretwork
[![Anlyon Radar](https://radar.anlyon.com/badge/com.guitarfretwork/fretwork.svg)](https://radar.anlyon.com/servers/com.guitarfretwork/fretwork)

Source: MCP Registry. Synced Oct 29, 2026, 11:17 UTC.

Fretwork Guitar Tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Fretwork Guitar Tools MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Fretwork Guitar Tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Fretwork Guitar Tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Fretwork Guitar Tools MCP server have?

9 tools: 4 write, 5 read. identify_chord, transpose_chords, guitar_level_check, make_practice_plan, get_chord_shapes, find_capo, get_scale, find_key and 1 more.

Does the Fretwork Guitar Tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Fretwork Guitar Tools MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Fretwork Guitar Tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.