Guitar Practice Routine App — Chord Charts
REMOTE · MCP.GUITARPRACTICEROUTINE.COM · 2 COMPONENTS
Look up a guitar chord by name and get a text chord diagram. 12,708 standard-tuning names.
Available components
Last scanned (38 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1587 tokens (~396/item across 4 items; 4 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 Management50
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 1 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_feedback" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 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
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 Oct 26 −4
No change was recorded against any check on this day. Stability & Change Management went from 83 to 50.
- 12 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1243 → 1587 ▼ functional
- “get_chord_chart_by_id” dropped the required parameter “llm_model” ▼ functional
- “get_chord_chart_by_name” dropped the required parameter “llm_model” ▼ functional
- “get_chord_of_the_day” dropped the required parameter “llm_model” ▼ functional
- “get_chord_chart_by_id” changed the type of “id”: integer → number|string|null ▼ functional
- Destructive annotations: pass → 0 functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “send_feedback” functional
- “get_chord_chart_by_id” reworded the description of “id” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- “get_chord_chart_by_id” made “id” optional cosmetic
- “get_chord_chart_by_name” made “name” optional cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 20 Sept 26 0
- 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
- 31 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Aug 26 0
First indexed and scored.
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 5 Nov 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=YR1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 6bc48acad6d3fa574396e595cdb27932c0f |
| SANs: mcp.guitarpracticeroutine.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 ~274
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 | number|string|null | – | Numeric chord id, e.g. 123 (a numeric string like "123" also works). |
No output schema declared.
No examples provided.
get_chord_chart_by_name Get a chord chart by name ~513
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… |
| name | string | – | 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 ~252
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… |
No output schema declared.
No examples provided.
send_feedback ~419
Send feedback about this chord chart server: a chord or capability you needed that its tools could not provide, a problem with a chart or a result, or praise. Only for feedback about these chord chart tools, not about other tasks. Do not include personal information about the user.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | Optional longer context: what you tried, exact parameter values, the error text you saw, and any workaround you used. Omit when the summary says it all. |
| feedback_type | string | yes | What kind of feedback this is. Use 'missing_capability' when the tool you needed does not exist in the tool list - nothing failed, the capability is absent (this is the most valuable report; send it… |
| friction_points | string | – | Optional: the specific moments that slowed you down, as short bullet-like sentences, quoting exact tool names, parameters, or error text. |
| sentiment | string | – | Optional: how the experience felt overall. |
| suggested_improvement | string | – | Optional: the concrete change that would have helped, e.g. the tool to add, the description to reword, or the error message to improve. |
| summary | string | yes | One self-contained sentence. For 'missing_capability': the capability you needed, e.g. 'No tool to delete multiple cohorts in one call.' For 'issue': the tool and the problem, e.g. 'query-trends reje… |
| task_completed | boolean | – | Optional: whether you still completed the user's task despite the problem. |
| tool_name | string | – | Optional: the existing tool this feedback is about (for 'issue' or 'praise'). Leave empty for 'missing_capability' - the point is that no tool fits. |
No output schema declared.
No examples provided.
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'
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 75 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 4 tools: get_chord_chart_by_name, get_chord_chart_by_id, get_chord_of_the_day, send_feedback. Their descriptions and schemas cost roughly 1,458 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.