Uttera
REMOTE · MCP.UTTERA.AI · SCANNED OCT 2
Audio for your agent: transcribe, speak, translate, summarise, plus sound effects and music.
Available components
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
remote · mcp.uttera.ai
claude mcp add --transport http ai-uttera-uttera 'https://mcp.uttera.ai/mcp'
{
"mcpServers": {
"ai-uttera-uttera": {
"url": "https://mcp.uttera.ai/mcp"
}
}
} {
"servers": {
"ai-uttera-uttera": {
"type": "http",
"url": "https://mcp.uttera.ai/mcp"
}
}
} [mcp_servers.ai-uttera-uttera] url = "https://mcp.uttera.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-uttera-uttera": {
"type": "remote",
"url": "https://mcp.uttera.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-uttera-uttera --url 'https://mcp.uttera.ai/mcp' --transport streamable-http
mcp_servers:
ai-uttera-uttera:
url: "https://mcp.uttera.ai/mcp" {
"McpServers": {
"ai-uttera-uttera": {
"Transport": "http",
"Url": "https://mcp.uttera.ai/mcp"
}
}
} assistant mcp add ai-uttera-uttera -t streamable-http -u 'https://mcp.uttera.ai/mcp'
{
"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.
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.
- 2 Oct 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- 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. functional
- 1 Oct 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- 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. security
- 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. functional
- 28 Sept 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
- 27 Sept 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- 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. functional
- 26 Sept 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- 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. security
- 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. functional
- 25 Sept 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
- 22 Sept 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 2 Oct 2026 · Probed https://mcp.uttera.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.uttera.ai | CN=YE1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a1cc2fabc6814cb15f0a90a91c9230e737 |
| SANs: mcp.uttera.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.uttera.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| uttera.ai. | present | 2371 | 13 | Verified |
| mcp.uttera.ai. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.uttera.ai/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.uttera.ai/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| www-authenticate | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.uttera.ai/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://mcp.uttera.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.uttera.ai/mcp |
| Authorisation server | https://mcp.uttera.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.uttera.ai/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.uttera.ai/mcp | HTTPS enforced | 301 | https://api.uttera.ai/mcp |
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 →
generate_music ~118
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».
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| seconds | number | – | – |
| seed | integer | – | – |
| steps | integer | – | – |
No output schema declared.
No examples provided.
generate_sound_effect ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| seconds | number | – | – |
| seed | integer | – | – |
No output schema declared.
No examples provided.
identify_speakers ~31
Who speaks and when. Returns the segments with their speaker and times.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
last_call_cost ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_voices ~20
The voice catalogue, with the language each one speaks.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
speak_text ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| text | string | yes | – |
| voice | string | – | – |
No output schema declared.
No examples provided.
summarize_recording ~54
Summarise a long recording: summary, full transcript, tone, speaker profile and who spoke when — all in one request and one upload.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
transcribe_audio ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
translate_recording ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audio | string | yes | – |
| target_language | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.