CHRP EPI Authority
REMOTE · CHRP.AI · SCANNED OCT 3
Read-only public EPI definitions, claim boundaries, use cases, and canonical sources.
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 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. 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 170 tokens (~21/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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
claude mcp add --transport http chrp-bass-chrp-epi-authority 'https://chrp.ai/mcp'
{
"mcpServers": {
"chrp-bass-chrp-epi-authority": {
"url": "https://chrp.ai/mcp"
}
}
} {
"servers": {
"chrp-bass-chrp-epi-authority": {
"type": "http",
"url": "https://chrp.ai/mcp"
}
}
} [mcp_servers.chrp-bass-chrp-epi-authority] url = "https://chrp.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrp-bass-chrp-epi-authority": {
"type": "remote",
"url": "https://chrp.ai/mcp",
"enabled": true
}
}
} openclaw mcp add chrp-bass-chrp-epi-authority --url 'https://chrp.ai/mcp' --transport streamable-http
mcp_servers:
chrp-bass-chrp-epi-authority:
url: "https://chrp.ai/mcp" {
"McpServers": {
"chrp-bass-chrp-epi-authority": {
"Transport": "http",
"Url": "https://chrp.ai/mcp"
}
}
} assistant mcp add chrp-bass-chrp-epi-authority -t streamable-http -u 'https://chrp.ai/mcp'
{
"mcpServers": {
"chrp-bass-chrp-epi-authority": {
"type": "http",
"url": "https://chrp.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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 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.
- 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
- 27 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.
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 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.
- 19 Sept 26 +1
- Stability: unverified → 0.03 ▲ 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 3 Oct 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=YR2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | RSA 2048 | SHA256-RSA | 698e1067491d5909cc5ad55effd96376b3b |
| SANs: chrp.ai | ||||||
| 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 chrp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| chrp.ai. | 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 |
| 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 |
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_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 ~19
Get public CHRP use-case pages.
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_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.
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. Read-only public EPI definitions, claim boundaries, use cases, and canonical sources. This page covers its hosted endpoint (https://chrp.ai/mcp).
Is the CHRP EPI Authority MCP server safe to use?
CHRP EPI Authority scores 79 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 8 tools: get_epi_definition, get_epi_score_definition, get_states, get_science, get_claim_boundaries, and 3 more. Their descriptions and schemas cost roughly 170 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 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.