THIRI Chord Intelligence
REMOTE · MCP.THIRI.AI · 2 COMPONENTS · SCANNED SEP 21
Deterministic music theory for agents: analyze, voice, reharmonize, conduct — computed, not guessed
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 373 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
How do I install the THIRI Chord Intelligence MCP server?
THIRI Chord Intelligence is a hosted endpoint at https://mcp.thiri.ai/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.thiri.ai
claude mcp add --transport http ai-thiri-chord-intelligence 'https://mcp.thiri.ai/mcp'
{
"mcpServers": {
"ai-thiri-chord-intelligence": {
"url": "https://mcp.thiri.ai/mcp"
}
}
} {
"servers": {
"ai-thiri-chord-intelligence": {
"type": "http",
"url": "https://mcp.thiri.ai/mcp"
}
}
} [mcp_servers.ai-thiri-chord-intelligence] url = "https://mcp.thiri.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-thiri-chord-intelligence": {
"type": "remote",
"url": "https://mcp.thiri.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-thiri-chord-intelligence --url 'https://mcp.thiri.ai/mcp' --transport streamable-http
mcp_servers:
ai-thiri-chord-intelligence:
url: "https://mcp.thiri.ai/mcp" {
"McpServers": {
"ai-thiri-chord-intelligence": {
"Transport": "http",
"Url": "https://mcp.thiri.ai/mcp"
}
}
} assistant mcp add ai-thiri-chord-intelligence -t streamable-http -u 'https://mcp.thiri.ai/mcp'
{
"mcpServers": {
"ai-thiri-chord-intelligence": {
"type": "http",
"url": "https://mcp.thiri.ai/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.
- 2 Sept 26 0
- Tool “generate_voicing” rewrote its description, which is the text the model reads security
- Schema quality: 59 → 74 ▼ functional
- Server version: 0.3.0 → 0.4.0 functional
- “generate_voicing” added an optional parameter “voices” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 8 Aug 26 0
- Schema quality: 216 → 297 ▼ functional
- Server version: 0.2.0 → 0.3.0 functional
- New tool “conduct_band” functional
- 31 Jul 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
- 30 Jul 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
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 21 Sept 2026 · Probed https://mcp.thiri.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thiri.ai | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a671db1e0ddde47513f807fab0a1fa6a |
| SANs: thiri.ai, mcp.thiri.ai, *.mcp.thiri.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.thiri.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| thiri.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.thiri.ai/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://mcp.thiri.ai/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://mcp.thiri.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.thiri.ai/mcp |
| Authorisation server | https://mcp.thiri.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thiri.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.thiri.ai/mcp | HTTPS enforced | 301 | https://mcp.thiri.ai/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 →
analyze_chord ~44
Parse a chord into root, quality, intervals, and (with a key) roman numeral + function.
| Name | Type | Req | Description |
|---|---|---|---|
| chord | string | yes | – |
| key | string | – | – |
No output schema declared.
No examples provided.
conduct_band ~81
Arrange a 4-piece band from a natural-language prompt. Returns conductor tempo/groove, 4 lanes of note events, lead sheet, and base64 MIDI. Audio render (Csound → WAV) stays on local thiri-conductor-mcp / POST /v2/render.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | number | – | – |
| prompt | string | yes | – |
No output schema declared.
No examples provided.
generate_voicing ~139
Instrument-ready voicing in a style. Tension symbols voice by seat substitution (arranging practice, not stacking): 9/b9/#9 replace the root, #11/13/b13 replace the 5th, the 3rd and 7th are untouched guide tones. Pass voices: 5 to promote the implied 9 of an 11/13 chord; pass previousNotes for a voice-leading score.
| Name | Type | Req | Description |
|---|---|---|---|
| chord | string | yes | – |
| keyContext | string | – | – |
| octave | number | – | – |
| previousNotes | array | – | – |
| style | string | – | – |
| voices | number | – | – |
No output schema declared.
No examples provided.
reharmonize ~78
Reharmonize a progression. Techniques: tritone_sub, ii_v_insertion, modal_interchange, diminished_passing, secondary_dominant, chain_of_dominants, coltrane_changes, backdoor (or auto).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | – |
| progression | array | yes | – |
| technique | string | – | – |
No output schema declared.
No examples provided.
resolve_chord ~31
Resolve a chord to spelled notes, frequencies, MIDI, and recommended scales.
| Name | Type | Req | Description |
|---|---|---|---|
| chord | string | yes | – |
No output schema declared.
No examples provided.
What is the THIRI Chord Intelligence MCP server?
THIRI Chord Intelligence is an MCP server listed in the public MCP registry as ai.thiri/chord-intelligence. Deterministic music theory for agents: analyze, voice, reharmonize, conduct, computed, not guessed. This page covers its hosted endpoint (https://mcp.thiri.ai/mcp).
Is the THIRI Chord Intelligence MCP server safe to use?
THIRI Chord Intelligence scores 84 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 THIRI Chord Intelligence MCP server expose?
THIRI Chord Intelligence exposes 5 tools: analyze_chord, resolve_chord, generate_voicing, reharmonize, conduct_band. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.
Does the THIRI Chord Intelligence MCP server require authentication?
Yes. THIRI Chord Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the THIRI Chord Intelligence MCP server still maintained?
THIRI Chord Intelligence 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.