# Uttera (remote · mcp.uttera.ai)

Audio for your agent: transcribe, speak, translate, summarise, plus sound effects and music.

- Trust score: 39/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `mcp.uttera.ai`: 39/100 (this document), [markdown](https://verifymcp.io/servers/ai-uttera-uttera/mcp.md), [page](https://verifymcp.io/servers/ai-uttera-uttera/mcp)

## Channel facts

- Endpoint: `https://mcp.uttera.ai/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-10-02.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 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 Uttera MCP server?

Uttera is a hosted endpoint at https://mcp.uttera.ai/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 ai-uttera-uttera 'https://mcp.uttera.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-uttera-uttera": {
      "url": "https://mcp.uttera.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-uttera-uttera": {
      "type": "http",
      "url": "https://mcp.uttera.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-uttera-uttera]
url = "https://mcp.uttera.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-uttera-uttera --url 'https://mcp.uttera.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-uttera-uttera:
    url: "https://mcp.uttera.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-uttera-uttera": {
      "Transport": "http",
      "Url": "https://mcp.uttera.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-uttera-uttera -t streamable-http -u 'https://mcp.uttera.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-uttera-uttera": {
      "type": "http",
      "url": "https://mcp.uttera.ai/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-10-02 (score 39, 0)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] Transport: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-10-01 (score 39, 0)

- [security regression] Endpoint reachability: behind authorisation → unreachable
- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-09-28 (score 39, 0)

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

### 2026-09-27 (score 39, 0)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] Transport: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-26 (score 39, 0)

- [security regression] Endpoint reachability: behind authorisation → unreachable
- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-09-25 (score 39, 0)

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

### 2026-09-22 (score 39, −34)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-21 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (9)

### `transcribe_audio` (~89 tokens)

Transcribe a recording. `audio` is an https URL or base64 audio.

    Use this for short recordings when you want the literal text. For anything
    past a few minutes prefer summarize_recording: it returns the transcript
    too, plus who spoke and the tone, in ONE upload instead of two.

Input parameters:

- `audio` (string, required)
- `language` (string)

Output parameters:

- `result` (string)

### `summarize_recording` (~54 tokens)

Summarise a long recording: summary, full transcript, tone, speaker
    profile and who spoke when — all in one request and one upload.

Input parameters:

- `audio` (string, required)
- `language` (string)

Output parameters:

- `result` (string)

### `identify_speakers` (~31 tokens)

Who speaks and when. Returns the segments with their speaker and times.

Input parameters:

- `audio` (string, required)

Output parameters:

- `result` (string)

### `speak_text` (~88 tokens)

Read text aloud. Returns audio. `voice` defaults to a Spanish one;
    call list_voices to see the catalogue.

    ⚠ Line breaks are billed: each one inserts a pause of about 1.3 s. Strip
    them from formatted text before sending it.

Input parameters:

- `language` (string)
- `text` (string, required)
- `voice` (string)

### `translate_recording` (~61 tokens)

Translate a recording into another language: text and, where the plan
    allows it, voice. `target_language` is a code such as en, es, fr, de.

Input parameters:

- `audio` (string, required)
- `target_language` (string, required)

Output parameters:

- `result` (string)

### `generate_sound_effect` (~81 tokens)

One sound effect from a description: a door, rain, footsteps. Up to 30 s.

    Needs a paid plan (Startup and up). The description works better in English.
    A fixed `seed` reproduces the same sound exactly.

Input parameters:

- `description` (string, required)
- `seconds` (number)
- `seed` (integer)

### `generate_music` (~118 tokens)

A finished piece of music from a description. Up to 380 s.

    Needs a paid plan (Startup and up). ⚠ BOTH controls cost: the price is
    length multiplied by steps, so 380 s at 128 steps is about eight times a
    60 s at 32. Naming style, instruments and BPM helps far more than asking
    for «something upbeat».

Input parameters:

- `description` (string, required)
- `seconds` (number)
- `seed` (integer)
- `steps` (integer)

### `list_voices` (~20 tokens)

The voice catalogue, with the language each one speaks.

Output parameters:

- `result` (string)

### `last_call_cost` (~52 tokens)

What the previous call actually cost, in credits, broken down.

    Worth checking before running something many times: it is the honest way
    to tell the user what a batch is going to cost them.

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39
- 2026-09-21: 73
- 2026-09-20: 72

## Common questions

### What is the Uttera MCP server?

Uttera is an MCP server listed in the public MCP registry as ai.uttera/uttera. Audio for your agent: transcribe, speak, translate, summarise, plus sound effects and music. This page covers its hosted endpoint (https://mcp.uttera.ai/mcp).

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

Uttera scores 39 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 Uttera MCP server expose?

Uttera exposes 9 tools: transcribe_audio, summarize_recording, identify_speakers, speak_text, translate_recording, and 4 more. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.

### Does the Uttera MCP server require authentication?

Yes. Uttera asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Uttera MCP server still maintained?

Uttera is still listed as active in the MCP registry. We last reached this channel on 2 October 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://mcp.uttera.ai/mcp
- Website: https://uttera.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-uttera-uttera/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-uttera-uttera/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-uttera-uttera/mcp