# Brainiall Pronunciation (remote · api.brainiall.com)

Pronunciation assessment, phoneme scoring, speaker voice ID, audio transcription, speech synthesis.

- Trust score: 50/100 (low)
- Change this week: −34
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `api.brainiall.com`: 50/100 (this document), [markdown](https://verifymcp.io/servers/com-brainiall-pronunciation/mcp-pronunciation-mcp.md), [page](https://verifymcp.io/servers/com-brainiall-pronunciation/mcp-pronunciation-mcp)

## Channel facts

- Endpoint: `https://api.brainiall.com/mcp/pronunciation/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-09-21.

- **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 connect, but we couldn't read the tool list to see what that exposes.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 142 tokens (~142/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 26 days we've observed: 14 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Brainiall Pronunciation MCP server?

Brainiall Pronunciation is a hosted endpoint at https://api.brainiall.com/mcp/pronunciation/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 com-brainiall-pronunciation 'https://api.brainiall.com/mcp/pronunciation/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-brainiall-pronunciation": {
      "url": "https://api.brainiall.com/mcp/pronunciation/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-brainiall-pronunciation": {
      "type": "http",
      "url": "https://api.brainiall.com/mcp/pronunciation/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-brainiall-pronunciation]
url = "https://api.brainiall.com/mcp/pronunciation/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-brainiall-pronunciation --url 'https://api.brainiall.com/mcp/pronunciation/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-brainiall-pronunciation:
    url: "https://api.brainiall.com/mcp/pronunciation/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-brainiall-pronunciation": {
      "Transport": "http",
      "Url": "https://api.brainiall.com/mcp/pronunciation/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-brainiall-pronunciation -t streamable-http -u 'https://api.brainiall.com/mcp/pronunciation/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-brainiall-pronunciation": {
      "type": "http",
      "url": "https://api.brainiall.com/mcp/pronunciation/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-09-21 (score 50, +15)

- [security regression] Stability: unverified → fail
- [functional regression] Schema quality: 109 → 142
- [functional regression] Schema quality: fail → unverified
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional] Schema quality: excellent → good
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 35, −51)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.77 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-18 (score 86, +51)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.77
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-17 (score 35, −49)

- [security regression] Endpoint reachability: unreachable → not serving MCP
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.

### 2026-09-15 (score 84, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.63 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-13 (score 84, +1)

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

### 2026-09-12 (score 83, +51)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.57
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-11 (score 32, −17)

The score moved with no change recorded against any check. We would rather say so than guess.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-09-21: 50
- 2026-09-20: 35
- 2026-09-19: 35
- 2026-09-18: 86
- 2026-09-17: 35
- 2026-09-16: 84
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 32
- 2026-09-10: 49
- 2026-09-09: 65
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 80
- 2026-09-04: 80
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75

## Common questions

### What is the Brainiall Pronunciation MCP server?

Brainiall Pronunciation is an MCP server listed in the public MCP registry as com.brainiall/pronunciation. Pronunciation assessment, phoneme scoring, speaker voice ID, audio transcription, speech synthesis. This page covers its hosted endpoint (https://api.brainiall.com/mcp/pronunciation/mcp).

### Is the Brainiall Pronunciation MCP server safe to use?

Brainiall Pronunciation scores 50 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.

### Does the Brainiall Pronunciation MCP server require authentication?

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

### Is the Brainiall Pronunciation MCP server still maintained?

Brainiall Pronunciation is still listed as active in the MCP registry. We last reached this channel on 21 September 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://api.brainiall.com/mcp/pronunciation/mcp
- Website: https://brainiall.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-brainiall-pronunciation/mcp-pronunciation-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-brainiall-pronunciation/mcp-pronunciation-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-brainiall-pronunciation/mcp-pronunciation-mcp