# com.pearl.mcp/pearl-api-mcp-server (remote · mcp.pearl.com)

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

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

## Components

- remote · `mcp.pearl.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp)
- remote · `mcp.pearl.com`: 59/100, [markdown](https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp-2.md), [page](https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp-2)

## Channel facts

- Endpoint: `https://mcp.pearl.com/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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 43/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 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-08-03 (score 63, +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-08-01 (score 62, +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-07-31 (score 61, +2)

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

### 2026-07-30 (score 59, 0)

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

### 2026-07-29 (score 59, +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-07-28 (score 58, +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-07-27 (score 57, 0)

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

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (4)

### `askPearlAi` (~110 tokens)

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 parameters:

- `chatHistory` (array): Optional conversation history. This ensures experts see the complete context
- `question` (string, required): The user's question
- `sessionId` (string): Optional session ID for continuing a conversation

### `askPearlExpert` (~231 tokens)

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 parameters:

- `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, required): The user's question
- `sessionId` (string): Optional session ID for continuing a conversation

### `askExpert` (~210 tokens)

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 parameters:

- `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, required): The user's question
- `sessionId` (string): Optional session ID for continuing a conversation

### `verifyAnswer` (~133 tokens)

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 parameters:

- `answer` (string, required): 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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 57

## Links

- Remote endpoint: https://mcp.pearl.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-pearl-mcp-pearl-api-mcp-server/mcp