# Coral (remote · mcp.getcoral.co)

Private, non-explicit intimacy exercises, scripts and a couples quiz for adults 18+.

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

## Components

- remote · `mcp.getcoral.co`: 79/100 (this document), [markdown](https://verifymcp.io/servers/co-getcoral-coral/mcp.md), [page](https://verifymcp.io/servers/co-getcoral-coral/mcp)

## Channel facts

- Endpoint: `https://mcp.getcoral.co/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-11-21.

- **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. 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.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1254 tokens (~139/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Coral MCP server?

Coral is a hosted endpoint at https://mcp.getcoral.co/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 co-getcoral-coral 'https://mcp.getcoral.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-getcoral-coral": {
      "url": "https://mcp.getcoral.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-getcoral-coral": {
      "type": "http",
      "url": "https://mcp.getcoral.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-getcoral-coral]
url = "https://mcp.getcoral.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-getcoral-coral": {
      "type": "remote",
      "url": "https://mcp.getcoral.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-getcoral-coral --url 'https://mcp.getcoral.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-getcoral-coral:
    url: "https://mcp.getcoral.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-getcoral-coral": {
      "Transport": "http",
      "Url": "https://mcp.getcoral.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-getcoral-coral -t streamable-http -u 'https://mcp.getcoral.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-getcoral-coral": {
      "type": "http",
      "url": "https://mcp.getcoral.co/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-11-21 (score 79, +1)

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

### 2026-11-19 (score 78, +1)

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

### 2026-11-17 (score 77, +1)

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

### 2026-11-15 (score 76, +1)

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

### 2026-11-14 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 75)

First indexed and scored.

## MCP tools (9)

### `coral_desire_checkin` (~149 tokens)

Coral desire check-in

Explore why desire may have changed and get one personalized, consent-based intimacy exercise. Use for questions about low desire, feeling disconnected, or not knowing what changed. Non-explicit, 18+ only, and not medical advice.

Input parameters:

- `comfort` (string): How much directness the user wants. Bold still means non-explicit.
- `factors` (array): Optional factors the user already recognizes. Omit to let Coral infer from the situation.
- `partnered` (boolean): Whether the user is currently in a relationship.
- `situation` (string): A short summary of the user situation in their own words, for example "I want sex less than my partner and I feel guilty".

### `coral_create_intimacy_challenge` (~167 tokens)

Coral intimacy challenge

Create a short, consent-based intimacy challenge for a couple. Use for questions like "how do we reconnect", "how can we bring back some spark", or "we have drifted apart". Returns a day-by-day plan of non-explicit activities. 18+ only.

Input parameters:

- `boundaries` (string): Any boundaries or limits the user mentions, so the plan can explicitly respect them.
- `comfort` (string): How much directness and playfulness the user wants. Bold still means non-explicit.
- `focus` (string): The main goal. connection is a 7-day reconnection plan, reconnection is a 14-day plan for a longer dry spell, confidence is a 7-day confidence plan, play is a 7-day playful plan.

### `coral_desire_gap_plan` (~135 tokens)

Coral desire gap navigator

Help a couple talk about different levels of desire without blame or pressure. Use when one partner wants more closeness than the other, when desire has changed, or when either person feels guilty or rejected. Returns a conversation plan and one exercise. 18+ only, non-explicit.

Input parameters:

- `higherDesire` (string): Which person currently wants sex more often.
- `pressure` (string): How much pressure or resentment is present right now.
- `situation` (string): A short summary of the situation in the user own words.
- `talkedBefore` (boolean): Whether they have already tried to talk about it.

### `coral_confidence_practice` (~114 tokens)

Coral intimacy confidence coach

Give personalized, non-explicit practices for confidence in intimacy: body confidence, starting a moment of closeness, boundaries, or talking about preferences. Use when someone asks how to feel more confident or less anxious about intimacy. 18+ only.

Input parameters:

- `area` (string): The part of confidence the user wants to work on.
- `situation` (string): A short summary of the situation in the user own words.
- `solo` (boolean): Whether the user is doing this alone rather than with a partner.

### `coral_conversation_coach` (~131 tokens)

Coral intimacy conversation coach

Help the user find the right words to talk about intimacy, desire, boundaries, new ideas, starting things, afterwards, or different levels of desire. Returns a script, talking points, a pause line, and guidance for different partner reactions. 18+ only, non-explicit.

Input parameters:

- `partnerResponse` (string): How the partner has responded before, if known.
- `situation` (string): A short summary of the situation in the user own words.
- `tone` (string): The tone the user wants to use.
- `topic` (string): The conversation the user wants to have.

### `coral_quiz_start` (~65 tokens)

Start a Coral couples quiz

Creates a new private two-person intimacy quiz. Returns an 8-character invite code for the partner, a participant token for the person starting it, and the ten questions with their options. Quizzes are deleted after 14 days. 18+ only, non-explicit.

### `coral_quiz_join` (~60 tokens)

Join a Coral couples quiz

Joins an existing quiz using the 8-character invite code from the partner. Returns a participant token and the ten questions. A quiz holds at most two people.

Input parameters:

- `inviteCode` (string, required): The 8-character invite code from the partner.

### `coral_quiz_submit` (~116 tokens)

Submit answers to a Coral couples quiz

Saves one person's answers to a quiz they started or joined: one option for each of the ten questions. When both people have submitted, the reply includes the shared comparison, which shows only the answers both people chose. Submitting again changes nothing.

Input parameters:

- `answers` (array, required): One answer per question. Every question must be answered.
- `participantToken` (string, required): This person's participant token, returned when they started or joined the quiz.
- `sessionId` (string, required): The session ID returned when the quiz was started or joined.

### `coral_quiz_status` (~82 tokens)

Check a Coral couples quiz

Checks a quiz without changing it. Says whether the partner has answered, and returns the shared comparison once both have. Needs the session ID and the participant token.

Input parameters:

- `participantToken` (string, required): This person's participant token, returned when they started or joined the quiz.
- `sessionId` (string, required): The session ID returned when the quiz was started or joined.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-getcoral-coral/mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75

## Common questions

### What is the Coral MCP server?

Coral is an MCP server listed in the public MCP registry as co.getcoral/coral. Private, non-explicit intimacy exercises, scripts and a couples quiz for adults 18+. This page covers its hosted endpoint (https://mcp.getcoral.co/mcp).

### Is the Coral MCP server safe to use?

Coral 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 Coral MCP server expose?

Coral exposes 9 tools: coral_desire_checkin, coral_create_intimacy_challenge, coral_desire_gap_plan, coral_confidence_practice, coral_conversation_coach, and 4 more. Their descriptions and schemas cost roughly 1,019 tokens of context every time the server is loaded.

### Does the Coral MCP server require authentication?

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

### Is the Coral MCP server still maintained?

Coral 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 Coral MCP server?

VerifyMCP ran 13 checks on Coral, 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.

## Links

- Remote endpoint: https://mcp.getcoral.co/mcp
- Website: https://getcoral.app/claude
- Changelog RSS feed: https://verifymcp.io/servers/co-getcoral-coral/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-getcoral-coral/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-getcoral-coral/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-getcoral-coral/mcp
