# Guitar Practice Routine App — Chord Charts (remote · mcp.guitarpracticeroutine.com)

Look up a guitar chord by name and get a text chord diagram. 12,708 standard-tuning names.

- Trust score: 65/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.guitarpracticeroutine.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp.md), [page](https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp)
- npm · `gpra-chord-charts-mcp`: 80/100, [markdown](https://verifymcp.io/servers/slshults-gpra-chord-charts/gpra-chord-charts-mcp.md), [page](https://verifymcp.io/servers/slshults-gpra-chord-charts/gpra-chord-charts-mcp)

## Channel facts

- Endpoint: `https://mcp.guitarpracticeroutine.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1243 tokens (~414/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 19/100
  - Stability check failed: schema churn in the 22 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Guitar Practice Routine App — Chord Charts MCP server?

Guitar Practice Routine App — Chord Charts is a hosted endpoint at https://mcp.guitarpracticeroutine.com/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.

### Claude

```bash
claude mcp add --transport http slshults-gpra-chord-charts 'https://mcp.guitarpracticeroutine.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "slshults-gpra-chord-charts": {
      "url": "https://mcp.guitarpracticeroutine.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "slshults-gpra-chord-charts": {
      "type": "http",
      "url": "https://mcp.guitarpracticeroutine.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.slshults-gpra-chord-charts]
url = "https://mcp.guitarpracticeroutine.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "slshults-gpra-chord-charts": {
      "type": "remote",
      "url": "https://mcp.guitarpracticeroutine.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add slshults-gpra-chord-charts --url 'https://mcp.guitarpracticeroutine.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  slshults-gpra-chord-charts:
    url: "https://mcp.guitarpracticeroutine.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "slshults-gpra-chord-charts": {
      "Transport": "http",
      "Url": "https://mcp.guitarpracticeroutine.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add slshults-gpra-chord-charts -t streamable-http -u 'https://mcp.guitarpracticeroutine.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "slshults-gpra-chord-charts": {
      "type": "http",
      "url": "https://mcp.guitarpracticeroutine.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 65, 0)

- [cosmetic] “get_chord_chart_by_id” made “id” optional
- [cosmetic] “get_chord_chart_by_name” made “name” optional

### 2026-09-20 (score 65, −7)

- [security regression] Stability: 0.67 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [functional regression] Schema quality: 314 → 414
- [functional regression] “get_chord_chart_by_id” added a required parameter “llm_model”, so existing callers break
- [functional regression] “get_chord_chart_by_name” added a required parameter “llm_model”, so existing callers break
- [functional regression] “get_chord_of_the_day” added a required parameter “llm_model”, so existing callers break
- [cosmetic] “get_chord_chart_by_id” reworded the description of “context”
- [cosmetic] “get_chord_chart_by_name” reworded the description of “context”
- [cosmetic] “get_chord_of_the_day” reworded the description of “context”

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 68, +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.

### 2026-09-08 (score 67, +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.

## MCP tools (3)

### `get_chord_chart_by_name` (~587 tokens)

Get a chord chart by name

Look up one guitar chord chart by name and return it as a text chord diagram ready to show the user. Returns the same single voicing that https://guitarpracticeroutine.com/find-a-chord-chart shows for that name. The library holds 12,708 standard-tuning (EADGBE) chord names, exactly one voicing each. Pass a plain chord name as it would be written on a chart — "G", "Am7", "Cmaj7", "D/F#", "F#m7b5" — not a sentence. Convert spoken forms yourself first: "G major" is "G", "A minor" is "Am", and use "#" and "b" rather than the unicode sharp and flat signs. Charts are drawn on a five-fret grid starting at the nut, the same as the website; any notes above the fifth fret are named in words underneath the chart. Prefer this over recalling a fingering from memory — these are curated chart data, and a remembered fingering is often wrong. Each result leads with a direct PNG URL for the chart — a permanently cacheable image of the same diagram, which you can show or link however your surface handles images. The chord name is on the first line; keep it next to any image you show, since a chart on its own can arrive unlabelled.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `format` (string): Which representations to return. Defaults to "text", which includes a direct URL to a PNG of the chart — embed that where your surface renders images. Use "image" or "both" only if you need the PNG b…
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `name` (string): A single chord name as written on a chart, e.g. "Am7" or "D/F#".

### `get_chord_chart_by_id` (~330 tokens)

Get a chord chart by id

Fetch one specific chord voicing by its numeric id, as returned by get_chord_chart_by_name. Use this to re-render a chart the user already saw without looking it up again.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `format` (string): Which representations to return. Defaults to "text", which includes a direct URL to a PNG of the chart — embed that where your surface renders images. Use "image" or "both" only if you need the PNG b…
- `id` (integer): Numeric chord id.
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…

### `get_chord_of_the_day` (~326 tokens)

Chord of the day

Return today's Chord of the Day from Guitar Practice Routine App — the same chord posted to the app's Bluesky and Facebook feeds that day. Useful as a practice prompt or a daily nudge for someone learning chords.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `format` (string): Which representations to return. Defaults to "text", which includes a direct URL to a PNG of the chart — embed that where your surface renders images. Use "image" or "both" only if you need the PNG b…
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp#diagnostics

## Score history

- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 63

## Common questions

### What is the Guitar Practice Routine App — Chord Charts MCP server?

Guitar Practice Routine App — Chord Charts is an MCP server listed in the public MCP registry as io.github.slshults/gpra-chord-charts. Look up a guitar chord by name and get a text chord diagram. 12,708 standard-tuning names. This page covers its hosted endpoint (https://mcp.guitarpracticeroutine.com/mcp).

### Is the Guitar Practice Routine App — Chord Charts MCP server safe to use?

Guitar Practice Routine App — Chord Charts scores 65 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 Guitar Practice Routine App — Chord Charts MCP server expose?

Guitar Practice Routine App — Chord Charts exposes 3 tools: get_chord_chart_by_name, get_chord_chart_by_id, get_chord_of_the_day. Their descriptions and schemas cost roughly 1,243 tokens of context every time the server is loaded.

### Does the Guitar Practice Routine App — Chord Charts MCP server require authentication?

No. We connected to Guitar Practice Routine App — Chord Charts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Guitar Practice Routine App — Chord Charts MCP server still maintained?

Guitar Practice Routine App — Chord Charts is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.guitarpracticeroutine.com/mcp
- Repository: https://github.com/slshults/gpra-chord-charts-mcp
- Website: https://guitarpracticeroutine.com/find-a-chord-chart
- Changelog RSS feed: https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp.json
- HTML version of this page: https://verifymcp.io/servers/slshults-gpra-chord-charts/mcp