Guitar Practice Routine App — Chord Charts
REMOTE · MCP.GUITARPRACTICEROUTINE.COM · 2 COMPONENTS · SCANNED SEP 21
Look up a guitar chord by name and get a text chord diagram. 12,708 standard-tuning names.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management16
- Stability check failed: schema churn in the 21 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
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 3 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
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.
remote · mcp.guitarpracticeroutine.com
claude mcp add --transport http slshults-gpra-chord-charts 'https://mcp.guitarpracticeroutine.com/mcp'
{
"mcpServers": {
"slshults-gpra-chord-charts": {
"url": "https://mcp.guitarpracticeroutine.com/mcp"
}
}
} {
"servers": {
"slshults-gpra-chord-charts": {
"type": "http",
"url": "https://mcp.guitarpracticeroutine.com/mcp"
}
}
} [mcp_servers.slshults-gpra-chord-charts] url = "https://mcp.guitarpracticeroutine.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"slshults-gpra-chord-charts": {
"type": "remote",
"url": "https://mcp.guitarpracticeroutine.com/mcp",
"enabled": true
}
}
} openclaw mcp add slshults-gpra-chord-charts --url 'https://mcp.guitarpracticeroutine.com/mcp' --transport streamable-http
mcp_servers:
slshults-gpra-chord-charts:
url: "https://mcp.guitarpracticeroutine.com/mcp" {
"McpServers": {
"slshults-gpra-chord-charts": {
"Transport": "http",
"Url": "https://mcp.guitarpracticeroutine.com/mcp"
}
}
} assistant mcp add slshults-gpra-chord-charts -t streamable-http -u 'https://mcp.guitarpracticeroutine.com/mcp'
{
"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.
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.
- 20 Sept 26 −7
- Stability: 0.67 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Schema quality: 314 → 414 ▼ functional
- “get_chord_chart_by_id” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_chord_chart_by_name” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_chord_of_the_day” added a required parameter “llm_model”, so existing callers break ▼ functional
- “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” cosmetic
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 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.
- 8 Sept 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.
- 6 Sept 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.
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 20 Sept 2026 · Probed https://mcp.guitarpracticeroutine.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.guitarpracticeroutine.com | CN=YR2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 629b67a7418a7920c75e1db6ead17d709c3 |
| SANs: mcp.guitarpracticeroutine.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.guitarpracticeroutine.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| guitarpracticeroutine.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.guitarpracticeroutine.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.guitarpracticeroutine.com/mcp | HTTPS enforced | 301 | https://mcp.guitarpracticeroutine.com/mcp |
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 →
get_chord_chart_by_id Get a chord chart by id ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | yes | Numeric chord id. |
| llm_model | string | yes | 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… |
No output schema declared.
No examples provided.
get_chord_chart_by_name Get a chord chart by name ~587
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | yes | 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 | yes | A single chord name as written on a chart, e.g. "Am7" or "D/F#". |
No output schema declared.
No examples provided.
get_chord_of_the_day Chord of the day ~326
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | yes | 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… |
No output schema declared.
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.