# CHRP EPI Authority (remote · chrp.ai)

Read-only public EPI definitions, claim boundaries, use cases, and canonical sources.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `chrp.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp.md), [page](https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp)

## Channel facts

- Endpoint: `https://chrp.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 170 tokens (~21/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

### Claude

```bash
claude mcp add --transport http chrp-bass-chrp-epi-authority 'https://chrp.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chrp-bass-chrp-epi-authority": {
      "url": "https://chrp.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chrp-bass-chrp-epi-authority": {
      "type": "http",
      "url": "https://chrp.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chrp-bass-chrp-epi-authority]
url = "https://chrp.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrp-bass-chrp-epi-authority": {
      "type": "remote",
      "url": "https://chrp.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chrp-bass-chrp-epi-authority --url 'https://chrp.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chrp-bass-chrp-epi-authority:
    url: "https://chrp.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chrp-bass-chrp-epi-authority": {
      "Transport": "http",
      "Url": "https://chrp.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chrp-bass-chrp-epi-authority -t streamable-http -u 'https://chrp.ai/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 79, +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.

### 2026-09-29 (score 78, +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.

### 2026-09-28 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 77, +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.

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +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.

### 2026-09-21 (score 74, +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.

### 2026-09-19 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `get_epi_definition` (~20 tokens)

Get CHRP’s canonical public Emotional Performance Intelligence definition.

### `get_epi_score_definition` (~22 tokens)

Get the public EPI Score definition and its canonical source.

### `get_states` (~23 tokens)

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

### `get_science` (~18 tokens)

Get the approved public science summary and source.

### `get_claim_boundaries` (~18 tokens)

Get CHRP’s published claim limitations.

### `get_chrp_use_cases` (~19 tokens)

Get public CHRP use-case pages.

### `get_canonical_sources` (~25 tokens)

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

### `get_mychrp_download_link` (~25 tokens)

Get the approved MyCHRP / EPI Score conversion link.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 78
- 2026-09-30: 78
- 2026-09-29: 78
- 2026-09-28: 77
- 2026-09-27: 77
- 2026-09-26: 76
- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72

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

## Links

- Remote endpoint: https://chrp.ai/mcp
- Repository: https://github.com/chrp-bass/chrp-parent-sites
- Website: https://chrp.ai/emotional-performance-intelligence
- Changelog RSS feed: https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp.xml
- Changelog JSON feed: https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp.json
- HTML version of this page: https://verifymcp.io/servers/chrp-bass-chrp-epi-authority/chrp