VoiceHue text to speech
REMOTE · VOICEHUE.COM
Remote text-to-speech MCP server with text_to_speech and list_voices tools. Free plan.
Available components
Last scanned (17 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 236 tokens (~118/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 79
First indexed and scored.
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 4 Nov 2026 · Probed https://voicehue.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=voicehue.com | CN=YR2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 643d9240d6d046e0c426267d852aefca73f |
| SANs: voicehue.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of voicehue.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| voicehue.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="voicehue", resource_metadata="https://voicehue.com/.well-known/oauth-protected-resource"
Bearer realm="voicehue", resource_metadata="https://voicehue.com/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none'; base-uri 'self'; object-src 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), geolocation=(), payment=(), usb=(), microphone=(self) |
Protected resource metadata
| Document | https://voicehue.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://voicehue.com/mcp |
| Authorisation server | https://voicehue.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://voicehue.com/mcp | Verified | 200 | |
| http (plaintext) | http://voicehue.com/mcp | HTTPS enforced | 308 | https://voicehue.com/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 →
list_voices List voices ~61
List the public VoiceHue voices a key can use: id, name, language and gender. Pass a voice id to text_to_speech.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional filter, for example en or zh. Matches the start of the language code. |
No output schema declared.
No examples provided.
text_to_speech Text to speech ~127
Convert text to spoken audio with a VoiceHue voice. Returns the audio (MP3 by default, or WAV) and a one-line summary with the voice, number of characters and duration. Up to 1,200 characters per call. Use list_voices first to get a valid voice id.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Audio format. MP3 is the default. |
| speed | number | – | Speaking speed, 0.5 to 2. |
| text | string | yes | The text to speak. |
| voice | string | yes | A voice id from list_voices. |
No output schema declared.
No examples provided.
How do I install the VoiceHue text to speech MCP server?
VoiceHue text to speech is a hosted endpoint at https://voicehue.com/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 · voicehue.com
claude mcp add --transport http voicehue-voicehue 'https://voicehue.com/mcp'
What is the VoiceHue text to speech MCP server?
VoiceHue text to speech is an MCP server listed in the public MCP registry as io.github.voicehue/voicehue. Remote text-to-speech MCP server with text_to_speech and list_voices tools. Free plan. This page covers its hosted endpoint (https://voicehue.com/mcp).
Is the VoiceHue text to speech MCP server safe to use?
VoiceHue text to speech scores 79 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 VoiceHue text to speech MCP server expose?
VoiceHue text to speech exposes 2 tools: text_to_speech, list_voices. Their descriptions and schemas cost roughly 188 tokens of context every time the server is loaded.
Does the VoiceHue text to speech MCP server require authentication?
Yes. VoiceHue text to speech 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 VoiceHue text to speech MCP server still maintained?
VoiceHue text to speech is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.