kurdish-tts-stt MCP server
com.kurdishtts/kurdish-tts-sttkurdishtts.comstreamable-httpv1.2.0Scanned
Sorani & Kurmanji TTS+STT: Kurdish speech most APIs lack. 885 voices, free tier, no key to browse.
6 tools: 1 can delete or cancel things, 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the kurdish-tts-stt MCP server can do
The kurdish-tts-stt MCP server is published by kurdishtts.com, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: start_streaming_transcription) and create or change data (2 tools: synthesize_speech and transcribe_audio). 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Deletes or cancels 1Claude Code: deny
start_streaming_transcriptionOpen a live speech-to-text session for LISTENING — a microphone or audio stream you transcribe in real time.No findings
Why it is in this group
- The name "start_streaming_transcription" says "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Open a live speech-to-text session for LISTENING — a microphone or audio stream you transcribe in real time. This does NOT make anything speak; to speak Kurdish use synthesize_speech, or POST https://www.kurdishtts.com/api/tts-stream for progressive audio. WARNING: calling this immediately consumes one streaming session from your STT plan quota — only call it when you are ready to connect. Returns a websocket_url: open it, stream PCM16 mono 16kHz audio chunks, send {"type": "finalize"} to flush and {"type": "done"} to close. Session duration is limited by plan.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
synthesize_speechConvert Kurdish text (Sorani or Kurmanji) to speech audio.No findings
Why it is in this group
- The description's first verb is "convert": a word for a change.
Description, as the server wrote it Convert Kurdish text (Sorani or Kurmanji) to speech audio. Requires a TTS API key; characters are billed against your plan. Get speaker_id from list_voices called with the SAME model_version you pass here (default "v3") — ids are not shared between catalogs. Returns one complete clip: MCP cannot stream, so for a live voice agent call POST https://www.kurdishtts.com/api/tts-stream directly instead (SSE, first audio in ~1s). Max 4000 characters per call in the default mp3 container, 600 with format "wav"; free plans are capped at 500 server-side. Note: speed is caller-facing (higher = faster).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
transcribe_audioTranscribe Kurdish audio (Sorani or Kurmanji) to text.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Transcribe Kurdish audio (Sorani or Kurmanji) to text. Requires an STT API key; usage is metered per audio minute against your plan. IMPORTANT: dialect selects the decoder and nothing detects it for you — transcribing Sorani audio as Kurmanji returns fluent, confident, WRONG text with no error. Pass dialect "auto" when you are not certain, and pick the coherent transcript from the two it returns. Max 3MB of decoded audio over MCP (~90s of 16kHz WAV, but ~25 minutes of 64kbps MP3 — send compressed audio to fit more); for larger files call POST https://www.kurdishtts.com/api/stt-proxy directly (multipart).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_planShow what this connection may use.No findings
Why it is in this group
- The name "get_plan" says "get": a word for reading.
Description, as the server wrote it Show what this connection may use. With an API key: your current plan, remaining allowance, which model_versions and speaker ids you may render. Without a key: the purchasable plan ladder and how to get a key. Free, no credits consumed. Call this FIRST when any tool returns a 401 or 403 — it is the fastest way to learn what went wrong.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_dialectsList the supported Kurdish dialects and their scripts.No findings
Why it is in this group
- The name "list_dialects" says "list": a word for reading.
Description, as the server wrote it List the supported Kurdish dialects and their scripts. Static capability descriptor — costs nothing and needs no API key.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_voicesList available Kurdish text-to-speech voices.No findings
Why it is in this group
- The name "list_voices" says "list": a word for reading.
Description, as the server wrote it List available Kurdish text-to-speech voices. Returns speaker ids to use with synthesize_speech. Free metadata call — no credits consumed, no API key needed. Defaults to model_version "v3", the SAME default synthesize_speech uses — pass the same model_version to both, because a speaker id from one catalog does not exist in another. Results are paginated; the response reports total_count and which ids a free plan may render.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.kurdishtts.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.kurdishtts.com/api/mcp: tools/list returned 6 tools to an anonymous client, including start_streaming_transcription (destructive), synthesize_speech (write), transcribe_audio (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http kurdish-tts-stt https://www.kurdishtts.com/api/mcpclaude mcp add --transport http kurdish-tts-stt https://www.kurdishtts.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__kurdish-tts-stt__list_dialects",
"mcp__kurdish-tts-stt__list_voices",
"mcp__kurdish-tts-stt__get_plan"
],
"ask": [
"mcp__kurdish-tts-stt__synthesize_speech",
"mcp__kurdish-tts-stt__transcribe_audio"
],
"deny": [
"mcp__kurdish-tts-stt__start_streaming_transcription"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kurdish-tts-stt. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kurdishtts/kurdish-tts-stt/verify?hash=5a6e8537501d9fc635101451f193368d1e0ea1f634883a75c4a5bd5462a1b8f3" | jq -e '.changed == false'Pinned hash 5a6e8537501d, from Nov 13, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kurdishtts/kurdish-tts-stt/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kurdishtts/kurdish-tts-stt)Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.
kurdish-tts-stt MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the kurdish-tts-stt MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the kurdish-tts-stt MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: start_streaming_transcription.
Can the kurdish-tts-stt MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the kurdish-tts-stt MCP server have?
- 6 tools: 1 destructive, 2 write, 3 read. start_streaming_transcription, synthesize_speech, transcribe_audio, list_dialects, list_voices and get_plan.
Does the kurdish-tts-stt MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the kurdish-tts-stt MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the kurdish-tts-stt MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.