com.pearl.mcp/pearl-api-mcp-server

REMOTE · MCP.PEARL.COM · 2 COMPONENTS · SCANNED AUG 3

Hybrid human + AI expertise for faster, trusted answers and decisions via MCP Server.

Available components

remote · mcp.pearl.com 63 remote · mcp.pearl.com 59

+6 this week 63 63 Trust /100

Trust breakdown (6 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 →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
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 Usability43

0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 691 tokens (~138/item across 5 items; 4 tools + 1 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.pearl.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-pearl-mcp-pearl-api-mcp-server https://mcp.pearl.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-pearl-mcp-pearl-api-mcp-server]
url = "https://mcp.pearl.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pearl-mcp-pearl-api-mcp-server": {
      "type": "remote",
      "url": "https://mcp.pearl.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-pearl-mcp-pearl-api-mcp-server --url https://mcp.pearl.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-pearl-mcp-pearl-api-mcp-server:
    url: "https://mcp.pearl.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-pearl-mcp-pearl-api-mcp-server": {
      "type": "http",
      "url": "https://mcp.pearl.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 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.
1 Aug 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.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 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
29 Jul 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.
28 Jul 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.
27 Jul 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
26 Jul 26 57

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://mcp.pearl.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=pearl.com	CN=WE1,O=Google Trust Services,C=US	25 Jul 2026	23 Oct 2026	ECDSA 256	ECDSA-SHA256	e254edbc6194d61c1366c2b95d75636f
SANs: pearl.com, *.pearl.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of mcp.pearl.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
pearl.com.	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; includeSubDomains; preload
content-security-policy	default-src 'self';
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	no-referrer-when-downgrade
permissions-policy	geolocation=(), microphone=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.pearl.com/mcp	Verified	200
http (plaintext)	http://mcp.pearl.com/mcp	HTTPS enforced	301	https://www.pearl.com/mcp

MCP tools — 4 exposed · ~684 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.

Tool Tokens

askExpert ~210

Use this when the user explicitly asks to speak with a real human expert, needs personalized advice in a complex or sensitive domain, or says something like 'Can I talk to a real expert?'. Supports phone callback — pass phoneNumber and contactPreference='phone' if the user wants a call.

Input Output Examples

Name	Type	Req	Description
chatHistory	array	—	Optional conversation history. This ensures experts see the complete context
contactPreference	string	—	Customer's preferred contact method. Set to 'phone' when the user wants a phone callback.
enableMockResponse	boolean	—	When true, the API returns a hardcoded mock expert success response instead of routing to a real expert. Useful for testing downstream behavior.
phoneNumber	string	—	Customer's phone number for expert callback in E.164 format (e.g., +15551234567). Only pass when the user explicitly provides it.
question	string	yes	The user's question
sessionId	string	—	Optional session ID for continuing a conversation

No output schema declared.

No examples provided.

askPearlAi ~110

Use this when the user wants a rapid AI-generated answer, draft, or alternative perspective on a low-risk or exploratory topic that does not require human validation. Do not use for medical, legal, financial, or safety-critical questions — use askExpert or askPearlExpert instead.

Input Output Examples

Name	Type	Req	Description
chatHistory	array	—	Optional conversation history. This ensures experts see the complete context
question	string	yes	The user's question
sessionId	string	—	Optional session ID for continuing a conversation

No output schema declared.

No examples provided.

askPearlExpert ~231

Use this when the problem is complex, ambiguous, high-stakes, or multidisciplinary and would benefit from AI intake followed by escalation to a human expert. Do not use for simple fact queries (use askPearlAi) or when the user explicitly requests a human directly (use askExpert). Supports phone callback — pass phoneNumber and contactPreference='phone' if the user wants a call.

Input Output Examples

Name	Type	Req	Description
chatHistory	array	—	Optional conversation history. This ensures experts see the complete context
contactPreference	string	—	Customer's preferred contact method. Set to 'phone' when the user wants a phone callback.
enableMockResponse	boolean	—	When true, the API returns a hardcoded mock expert success response instead of routing to a real expert. Useful for testing downstream behavior.
phoneNumber	string	—	Customer's phone number for expert callback in E.164 format (e.g., +15551234567). Only pass when the user explicitly provides it.
question	string	yes	The user's question
sessionId	string	—	Optional session ID for continuing a conversation

No output schema declared.

No examples provided.

verifyAnswer ~133

Use this when a professional needs to validate the correctness, safety, or trustworthiness of a specific AI-generated answer, or when the user asks to have an answer double-checked by a real expert.

Input Output Examples

Name	Type	Req	Description
answer	string	yes	The AI-generated answer that requires human verification
chatHistory	array	—	Optional prior messages for context (ordered, oldest first)
enableMockResponse	boolean	—	When true, the API returns a hardcoded mock expert success response instead of routing to a real expert. Useful for testing downstream behavior.
sessionId	string	—	Existing session ID to continue; generated if omitted

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	57
27 Jul	57
28 Jul	58
29 Jul	59
30 Jul	59
31 Jul	61
1 Aug	62
2 Aug	62
3 Aug	63