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.

Coral

REMOTE · MCP.GETCORAL.CO

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

Available components

+4 this week 79 Trust /100

Last scanned (14 hours ago)

Scores higher than 74% 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 Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • 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 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 9 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 supported MCP spec version (2025-11-25); the latest is 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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 75

    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 21 Nov 2026 · Probed https://mcp.getcoral.co/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.getcoral.co CN=Amazon RSA 2048 S20,O=Amazon,C=US 7 Nov 2026 24 May 2027 RSA 2048 SHA256-RSA 4117ff33c508647bb1aa5c5b65d9645d
SANs: *.getcoral.co
CN=Amazon RSA 2048 S20,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA b95efa916a4e6cff9d8348f039fd125b981b5bd
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.getcoral.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
getcoral.co. 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=15552000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.getcoral.co/mcp Verified 200
http (plaintext) http://mcp.getcoral.co/mcp HTTPS enforced 301 https://mcp.getcoral.co/mcp
MCP tools · 9 exposed · ~1,019 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
coral_confidence_practice ~114

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.

NameTypeReqDescription
areastring–The part of confidence the user wants to work on.
situationstring–A short summary of the situation in the user own words.
soloboolean–Whether the user is doing this alone rather than with a partner.

No output schema declared.

No examples provided.

coral_conversation_coach ~131

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.

NameTypeReqDescription
partnerResponsestring–How the partner has responded before, if known.
situationstring–A short summary of the situation in the user own words.
tonestring–The tone the user wants to use.
topicstring–The conversation the user wants to have.

No output schema declared.

No examples provided.

coral_create_intimacy_challenge ~167

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.

NameTypeReqDescription
boundariesstring–Any boundaries or limits the user mentions, so the plan can explicitly respect them.
comfortstring–How much directness and playfulness the user wants. Bold still means non-explicit.
focusstring–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.

No output schema declared.

No examples provided.

coral_desire_checkin ~149

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.

NameTypeReqDescription
comfortstring–How much directness the user wants. Bold still means non-explicit.
factorsarray–Optional factors the user already recognizes. Omit to let Coral infer from the situation.
partneredboolean–Whether the user is currently in a relationship.
situationstring–A short summary of the user situation in their own words, for example "I want sex less than my partner and I feel guilty".

No output schema declared.

No examples provided.

coral_desire_gap_plan ~135

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.

NameTypeReqDescription
higherDesirestring–Which person currently wants sex more often.
pressurestring–How much pressure or resentment is present right now.
situationstring–A short summary of the situation in the user own words.
talkedBeforeboolean–Whether they have already tried to talk about it.

No output schema declared.

No examples provided.

coral_quiz_join ~60

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.

NameTypeReqDescription
inviteCodestringyesThe 8-character invite code from the partner.

No output schema declared.

No examples provided.

coral_quiz_start ~65

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

coral_quiz_status ~82

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.

NameTypeReqDescription
participantTokenstringyesThis person's participant token, returned when they started or joined the quiz.
sessionIdstringyesThe session ID returned when the quiz was started or joined.

No output schema declared.

No examples provided.

coral_quiz_submit ~116

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.

NameTypeReqDescription
answersarrayyesOne answer per question. Every question must be answered.
participantTokenstringyesThis person's participant token, returned when they started or joined the quiz.
sessionIdstringyesThe session ID returned when the quiz was started or joined.

No output schema declared.

No examples provided.

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.

remote · mcp.getcoral.co

# add to Claude Code
claude mcp add --transport http co-getcoral-coral 'https://mcp.getcoral.co/mcp'
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.