Transkriba — Russian audio transcription
REMOTE · TRANSKRIBA.RU · SCANNED SEP 28
Transcribe Russian audio and video with timestamps and optional speaker labels from files or links.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 884 tokens (~126/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management31
- Stability check failed: schema churn in the 14 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Transkriba — Russian audio transcription MCP server?
Transkriba — Russian audio transcription is a hosted endpoint at https://transkriba.ru/api/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 · transkriba.ru
claude mcp add --transport http ru-transkriba-transcription 'https://transkriba.ru/api/mcp'
{
"mcpServers": {
"ru-transkriba-transcription": {
"url": "https://transkriba.ru/api/mcp"
}
}
} {
"servers": {
"ru-transkriba-transcription": {
"type": "http",
"url": "https://transkriba.ru/api/mcp"
}
}
} [mcp_servers.ru-transkriba-transcription] url = "https://transkriba.ru/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ru-transkriba-transcription": {
"type": "remote",
"url": "https://transkriba.ru/api/mcp",
"enabled": true
}
}
} openclaw mcp add ru-transkriba-transcription --url 'https://transkriba.ru/api/mcp' --transport streamable-http
mcp_servers:
ru-transkriba-transcription:
url: "https://transkriba.ru/api/mcp" {
"McpServers": {
"ru-transkriba-transcription": {
"Transport": "http",
"Url": "https://transkriba.ru/api/mcp"
}
}
} assistant mcp add ru-transkriba-transcription -t streamable-http -u 'https://transkriba.ru/api/mcp'
{
"mcpServers": {
"ru-transkriba-transcription": {
"type": "http",
"url": "https://transkriba.ru/api/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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.
- 15 Sept 26 −1
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “create_upload” rewrote its description, which is the text the model reads security
- Tool “get_transcript” rewrote its description, which is the text the model reads security
- Tool “search_transcripts” rewrote its description, which is the text the model reads security
- Tool “transcribe_url” rewrote its description, which is the text the model reads security
- “create_upload” added a required parameter “size_bytes”, so existing callers break ▼ functional
- “transcribe_file” made “file_name” required, so existing callers break ▼ functional
- 14 Sept 26 64
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 28 Sept 2026 · Probed https://transkriba.ru/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=transkriba.ru | CN=YR2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | RSA 4096 | SHA256-RSA | 5c4b59b7942dd504ecdd651f628a31046c5 |
| SANs: transkriba.ru | ||||||
| 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 transkriba.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| transkriba.ru. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://transkriba.ru/api/mcp | Verified | 200 | |
| http (plaintext) | http://transkriba.ru/api/mcp | HTTPS enforced | 302 | https://transkriba.ru/api/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 →
create_upload Получить ссылку для загрузки файла ~206
Путь для локального файла, у которого нет публичной ссылки. Передайте file_name и точный size_bytes. Возвращает upload_url, s3_key и обязательный content_type. Загрузите файл запросом PUT, передав Content-Type и Content-Length в точности из ответа (например, curl -X PUT -H 'Content-Type: application/octet-stream' -H 'Content-Length: 1048576' --data-binary @file.ogg <upload_url>), после чего передайте s3_key и file_name в transcribe_file. Ссылка живёт 30 минут; один файл может занимать не более 256 МБ.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | MIME-тип файла. По умолчанию application/octet-stream. |
| file_name | string | yes | Имя файла с расширением, например voice.ogg |
| size_bytes | number | yes | Точный размер файла в байтах, от 1 до 268435456. |
No output schema declared.
No examples provided.
get_balance Остаток минут ~50
Показывает, сколько минут расшифровки осталось на балансе. Стоит спросить перед пачкой длинных записей, чтобы не упереться в нехватку на середине.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transcript Забрать расшифровку ~129
Возвращает состояние задачи по job_id, а когда она готова — текст с таймкодами и метками спикеров, если при запуске было передано diarize=true. Пока идёт расшифровка, отвечает status=processing: вызывайте повторно с паузой в несколько секунд. Время зависит от длины записи, очереди и запуска обработчика.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Формат ответа. По умолчанию text — реплики с таймкодами. |
| job_id | string | yes | Идентификатор из transcribe_url |
No output schema declared.
No examples provided.
list_transcripts Список последних расшифровок ~68
Перечисляет последние расшифровки учётной записи: id, имя файла, длительность и состояние. Полезно, чтобы найти job_id вчерашней записи, не спрашивая человека.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Сколько записей вернуть, до 50 |
No output schema declared.
No examples provided.
search_transcripts Поиск по расшифровкам ~96
Ищет фразу по текстам последних 200 готовых расшифровок и возвращает совпадения с таймкодом и именем спикера. Так можно найти, где именно на трёхчасовом созвоне обсуждали сроки, не перечитывая всё.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Сколько совпадений вернуть, до 50 |
| query | string | yes | Что искать |
No output schema declared.
No examples provided.
transcribe_file Расшифровать загруженный файл ~135
Переводит в текст файл, загруженный по ссылке из create_upload. Возвращает job_id сразу: результат забирается инструментом get_transcript. Списывает минуты с баланса по факту длительности записи.
| Name | Type | Req | Description |
|---|---|---|---|
| diarize | boolean | – | Разделить запись по спикерам. По умолчанию false. |
| file_name | string | yes | Человеческое имя записи для списка расшифровок |
| language | string | – | Код языка, например ru или en. Без него определяется сам. |
| s3_key | string | yes | Ключ из ответа create_upload |
No output schema declared.
No examples provided.
transcribe_url Расшифровать запись по ссылке ~153
Переводит аудио или видео по ссылке в текст с таймкодами. Передайте diarize=true, если нужно разделение по спикерам. Понимает публичные записи YouTube, VK Видео, Rutube, Дзен, OK, Castbox и SoundCloud. Возвращает job_id сразу: результат забирается инструментом get_transcript. Списывает минуты с баланса по факту длительности записи.
| Name | Type | Req | Description |
|---|---|---|---|
| diarize | boolean | – | Разделить запись по спикерам. По умолчанию false. |
| language | string | – | Код языка, например ru или en. Без него определяется сам. |
| url | string | yes | Ссылка на запись |
No output schema declared.
No examples provided.
What is the Transkriba — Russian audio transcription MCP server?
Transkriba — Russian audio transcription is an MCP server listed in the public MCP registry as ru.transkriba/transcription. Transcribe Russian audio and video with timestamps and optional speaker labels from files or links. This page covers its hosted endpoint (https://transkriba.ru/api/mcp).
Is the Transkriba — Russian audio transcription MCP server safe to use?
Transkriba — Russian audio transcription scores 68 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 Transkriba — Russian audio transcription MCP server expose?
Transkriba — Russian audio transcription exposes 7 tools: transcribe_url, create_upload, transcribe_file, get_transcript, list_transcripts, and 2 more. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.
Does the Transkriba — Russian audio transcription MCP server require authentication?
No. We connected to Transkriba — Russian audio transcription without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Transkriba — Russian audio transcription MCP server still maintained?
Transkriba — Russian audio transcription is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.