Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

THIRI Chord Intelligence

REMOTE · MCP.THIRI.AI · 2 COMPONENTS · SCANNED AUG 3

Deterministic music theory for agents: analyze, voice, reharmonize, conduct — computed, not guessed

+10 this week 71 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 216 tokens (~54/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.thiri.ai

# add to Claude Code
claude mcp add --transport http ai-thiri-chord-intelligence https://mcp.thiri.ai/mcp
# ~/.codex/config.toml
[mcp_servers.ai-thiri-chord-intelligence]
url = "https://mcp.thiri.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-thiri-chord-intelligence": {
      "type": "remote",
      "url": "https://mcp.thiri.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-thiri-chord-intelligence --url https://mcp.thiri.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-thiri-chord-intelligence:
    url: "https://mcp.thiri.ai/mcp"
// mcp.json
{
  "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.

Changelog

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 Aug 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.

  • 31 Jul 26 +8
    • 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
  • 29 Jul 26 +1

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

  • 27 Jul 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
  • 26 Jul 26 60

    First indexed and scored.

Diagnostics

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 3 Aug 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 5 Jun 2026 3 Sept 2026 ECDSA 256 ECDSA-SHA256 2a6d5dfa020493eb0efd7970c9f63d67
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
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
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
MCP tools — 4 exposed · ~216 tokens

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.

Tool Tokens
analyze_chord ~44

Parse a chord into root, quality, intervals, and (with a key) roman numeral + function.

NameTypeReqDescription
chordstringyes
keystring

No output schema declared.

No examples provided.

generate_voicing ~63

Instrument-ready voicing in a style; pass previousNotes for a voice-leading score.

NameTypeReqDescription
chordstringyes
keyContextstring
octavenumber
previousNotesarray
stylestring

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).

NameTypeReqDescription
keystring
progressionarrayyes
techniquestring

No output schema declared.

No examples provided.

resolve_chord ~31

Resolve a chord to spelled notes, frequencies, MIDI, and recommended scales.

NameTypeReqDescription
chordstringyes

No output schema declared.

No examples provided.