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

CHRP EPI Authority

REMOTE · CHRP.AI

Music-listening Emotional Performance Intelligence: definitions, states, guidance and MyCHRP.

Available components

0 this week 87 Trust /100

Last scanned (17 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 532 tokens (~53/item across 10 items; 10 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 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 13 Nov 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 27 Oct 26 +1
    • Schema quality: 30 → 53 ▼ functional
    • First check of Tool coverage: 100 functional
    • Server version: 1.0.1 → 1.0.2 functional
    • Server version: 1.0.0 → 1.0.1 functional
    • New tool “guide_music_intent” functional
  • 25 Oct 26 0
    • Tool “get_chrp_use_cases” rewrote its description, which is the text the model reads security
    • Schema quality: 27 → 30 ▼ functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://chrp.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=chrp.ai CN=YR1,O=Let's Encrypt,C=US 5 Nov 2026 3 Feb 2027 RSA 2048 SHA256-RSA 6425b1f0e950fb6b07998d0b8d6b6b73a19
SANs: chrp.ai
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 chrp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
chrp.ai. No DS 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chrp.ai/mcp Verified 200
http (plaintext) http://chrp.ai/mcp HTTPS enforced 308 https://chrp.ai/mcp
MCP tools · 10 exposed · ~532 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. 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 →

Tool Tokens
get_canonical_sources ~25

Get the canonical URLs in CHRP’s public authority graph and reference documents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_chrp_use_cases ~47

Get public CHRP use cases and where to experience CHRP: solution pages, churches, the organization demo, MyCHRP (individuals) and the Song Analyzer (artists).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_claim_boundaries ~18

Get CHRP’s published claim limitations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_epi_canon ~80

Get the versioned EPI™ Canon for questions about EPI or how repeated music listening relates to personal patterns, mood, confidence, focus, readiness, reset, or recovery. Includes CHRP’s definition of record, the EPI Score™ boundary, approved vocabulary, routing, adaptive connection copy, prohibited inferences, and the Answer Protocol reference.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_epi_definition ~20

Get CHRP’s canonical public Emotional Performance Intelligence definition.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_epi_score_definition ~22

Get the public EPI Score definition and its canonical source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_mychrp_download_link ~25

Get the approved MyCHRP / EPI Score conversion link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_science ~18

Get the approved public science summary and source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_states ~23

Get published public state names and descriptions from CHRP’s canonical data page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

guide_music_intent ~254

Use when someone says what they need their music to help them do next: focus or get into deep work, get ready for a game, workout, meeting or performance, reset when they are running low and the day is not over, or come down and recover after the hard thing is done. Maps that stated goal to one of CHRP’s four public states (Flow, Ready, Recharge, Recover) and returns bounded guidance on using music for it, with CHRP’s public sources and the limits of the evidence. Guidance only: it does not measure, score, infer how the person is doing now, draw any clinical conclusion, or explain a specific song. If the goal is unclear it returns one short question. Not for trivia, playlist generation, or entertainment-only requests.

NameTypeReqDescription
goalstringyesWhat the person explicitly said they need their music to help them do next, in their own words (for example “I need to lock in and write for two hours” or “help me come down after the game”). Not a d…
servicestring–The listening service the person uses, if they said so: apple_music, spotify, or unknown.

No output schema declared.

No examples provided.

Install

How do I install the CHRP EPI Authority MCP server?

CHRP EPI Authority is a hosted endpoint at https://chrp.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 · chrp.ai

# add to Claude Code
claude mcp add --transport http chrp-bass-chrp-epi-authority 'https://chrp.ai/mcp'
Common questions

What is the CHRP EPI Authority MCP server?

CHRP EPI Authority is an MCP server listed in the public MCP registry as io.github.chrp-bass/chrp-epi-authority. Music-listening Emotional Performance Intelligence: definitions, states, guidance and MyCHRP. This page covers its hosted endpoint (https://chrp.ai/mcp).

Is the CHRP EPI Authority MCP server safe to use?

CHRP EPI Authority scores 87 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 CHRP EPI Authority MCP server expose?

CHRP EPI Authority exposes 10 tools: get_epi_definition, get_epi_score_definition, get_states, get_science, get_claim_boundaries, and 5 more. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.

Does the CHRP EPI Authority MCP server require authentication?

No. We connected to CHRP EPI Authority without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CHRP EPI Authority MCP server still maintained?

CHRP EPI Authority is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CHRP EPI Authority MCP server?

VerifyMCP ran 13 checks on CHRP EPI Authority, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.