com.brainiall/tts
REMOTE · API.BRAINIALL.COM · SCANNED SEP 21
Hosted pay-per-use TTS: 54 neural voices, 9 languages incl. Brazilian Portuguese. $10 free credits.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
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 com.brainiall/tts MCP server?
com.brainiall/tts is a hosted endpoint at https://api.brainiall.com/mcp/tts/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 · api.brainiall.com
claude mcp add --transport http com-brainiall-tts 'https://api.brainiall.com/mcp/tts/mcp'
{
"mcpServers": {
"com-brainiall-tts": {
"url": "https://api.brainiall.com/mcp/tts/mcp"
}
}
} {
"servers": {
"com-brainiall-tts": {
"type": "http",
"url": "https://api.brainiall.com/mcp/tts/mcp"
}
}
} [mcp_servers.com-brainiall-tts] url = "https://api.brainiall.com/mcp/tts/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-brainiall-tts": {
"type": "remote",
"url": "https://api.brainiall.com/mcp/tts/mcp",
"enabled": true
}
}
} openclaw mcp add com-brainiall-tts --url 'https://api.brainiall.com/mcp/tts/mcp' --transport streamable-http
mcp_servers:
com-brainiall-tts:
url: "https://api.brainiall.com/mcp/tts/mcp" {
"McpServers": {
"com-brainiall-tts": {
"Transport": "http",
"Url": "https://api.brainiall.com/mcp/tts/mcp"
}
}
} assistant mcp add com-brainiall-tts -t streamable-http -u 'https://api.brainiall.com/mcp/tts/mcp'
{
"mcpServers": {
"com-brainiall-tts": {
"type": "http",
"url": "https://api.brainiall.com/mcp/tts/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.
- 18 Sept 26 +7
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ 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
- 17 Sept 26 −7
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Sept 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: fail → 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. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. 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. functional
- 12 Sept 26 −17
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ 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
- 11 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 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
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 21 Sept 2026 · Probed https://api.brainiall.com/mcp/tts/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.brainiall.com | CN=YE2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 58149e86edf6d04081a9ee2d9180aba7dcd |
| SANs: api.brainiall.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 insecure
Validation of api.brainiall.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brainiall.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer resource_metadata="https://api.brainiall.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.brainiall.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://api.brainiall.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.brainiall.com/mcp/tts/mcp | Auth required | 401 | |
| http (plaintext) | http://api.brainiall.com/mcp/tts/mcp | HTTPS enforced | 308 | https://api.brainiall.com/mcp/tts/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 →
check_tts_service Check TTS Service ~40
Check health status of the TTS API service. Returns: dict with keys: - status (str): 'healthy' or error state
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_voices List Voices ~138
List available TTS voices with metadata. 54 neural voices across 9 languages. Each voice has an ID (used in synthesize_speech), display name, gender, accent and quality grade. Args: language: Optional language filter (e.g. 'pt-br', 'en-us'). Returns: dict with keys: - voices (list): Each with id, name, gender, accent, lang, grade - count (int): Number of voices returned
| Name | Type | Req | Description |
|---|---|---|---|
| language | – | – | Filter by language code (e.g. 'pt-br', 'en-us', 'ja'); omit for all 54 voices |
No output schema declared.
No examples provided.
synthesize_speech Synthesize Speech ~440
Convert text to natural-sounding speech. Returns WAV audio (16-bit PCM, 24 kHz mono) synthesized with neural voices. 54 voices across 9 languages -- including 3 native Brazilian Portuguese voices (pf_dora, pm_alex, pm_santa). Usage is metered per character. Args: text: Text to convert to speech (max 5000 characters per request). language: Language code; selects the default voice when no voice is given. voice: Explicit voice ID (see list_voices). Overrides language. speed: Speech speed multiplier, 0.5-2.0. output_format: 'audio' for playable MCP audio content, 'base64_json' for a JSON object with the base64-encoded WAV and metadata. Returns: MCP audio content (audio/wav), or when output_format='base64_json' a dict with keys: - audio_base64 (str): Base64-encoded WAV bytes - mime_type (str): 'audio/wav' - voice (str): Voice used - characters (int): Characters billed - estimated_cost_usd (float): Estimated cost of this request
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language code: 'pt' (Brazilian Portuguese, default), 'en', 'en-gb', 'es', 'fr', 'it', 'hi', 'ja', 'zh'. Used to pick a default voice when 'voice' is omitted. |
| output_format | string | – | 'audio' (default) returns playable MCP audio content; 'base64_json' returns JSON with the base64-encoded WAV plus metadata |
| speed | number | – | Speech speed multiplier (0.5 = half speed, 2.0 = double speed) |
| text | string | yes | Text to convert to speech (1-5000 characters per request) |
| voice | – | – | Voice ID (e.g. 'pf_dora', 'pm_alex', 'af_heart', 'bm_george'). Overrides 'language'. Use list_voices for the full catalog. |
No output schema declared.
No examples provided.
What is the com.brainiall/tts MCP server?
com.brainiall/tts is an MCP server listed in the public MCP registry as com.brainiall/tts. Hosted pay-per-use TTS: 54 neural voices, 9 languages incl. Brazilian Portuguese. $10 free credits. This page covers its hosted endpoint (https://api.brainiall.com/mcp/tts/mcp).
Is the com.brainiall/tts MCP server safe to use?
com.brainiall/tts scores 36 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 com.brainiall/tts MCP server expose?
com.brainiall/tts exposes 3 tools: synthesize_speech, list_voices, check_tts_service. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Does the com.brainiall/tts MCP server require authentication?
Yes. com.brainiall/tts 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 com.brainiall/tts MCP server still maintained?
com.brainiall/tts 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.