Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Transkripce – Czech audio and video transcription

REMOTE · TRANSKRIPCE.I-DOTAZNIK.CZ

Czech audio/video transcription: upload media, run transcription, get transcript and QA report.

+3 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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 & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 599 tokens (~59/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (90% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Endpoint address

    Registry says
    https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp
    Package shows
    https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp/

    The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 70

    First indexed and scored.

Diagnostics

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 Nov 2026 · Probed https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp/ · Declared URL https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=transkripce.i-dotaznik.cz CN=YE2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA384 5bef7c4b6ca32422da5af2a47ce4294cbf6
SANs: transkripce.i-dotaznik.cz
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 transkripce.i-dotaznik.cz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cz. DS published 20237 13 Verified
i-dotaznik.cz. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp Redirected 307 https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp/
streamable-http · followed https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp/ Verified 200
http (plaintext) http://transkripce.i-dotaznik.cz/api/v1/transcription/mcp HTTPS enforced 301 https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp
MCP tools · 10 exposed · ~464 tokens

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 →

Tool Tokens
transcription_create_topup_checkout ~89

Prepare a Stripe payment link for a credit package (human pays, not the agent). Human-in-the-loop top-up: returns `payment_url` that the HUMAN account owner must open and pay; credits are added automatically after payment. The agent never touches a card or payment method. Requires the transcription:write scope.

NameTypeReqDescription
package_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

transcription_estimate_cost ~32

Estimate credit cost of transcribing audio of the given duration (seconds).

NameTypeReqDescription
duration_secondsnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

transcription_get_credit_balance ~22

Get your prepaid credit balance (total, reserved, available).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

transcription_get_quality_report ~38

Download the quality audit report of a completed workflow (txt/md).

NameTypeReqDescription
formatstring––
workflow_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

transcription_get_transcript ~39

Download the final merged transcript of a completed workflow (txt/json/md).

NameTypeReqDescription
formatstring––
workflow_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

transcription_get_workflow ~34

Get one transcription workflow by ID (status, error, billing, job IDs).

NameTypeReqDescription
workflow_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

transcription_list_audio_files ~25

List audio files you have uploaded (IDs usable in transcription_start_workflow).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

transcription_list_credit_packages ~23

List purchasable credit packages (public CZK price list).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

transcription_list_workflows ~31

List your transcription workflows, newest first (status, IDs, billing).

NameTypeReqDescription
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

transcription_start_workflow ~131

Start an automatic transcription workflow (transcription -> merge -> quality). Requires the transcription:write scope and reserves prepaid credits (1 credit per started minute); fails with INSUFFICIENT_CREDITS when the balance is too low, or AGENT_KEY_BUDGET_EXCEEDED when the key's pre-authorized budget would be exceeded. Upload audio first via REST POST /api/v1/transcription/audio-files.

NameTypeReqDescription
audio_file_idstringyes–
diarization_enabled–––
max_duration_seconds–––
providers–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Transkripce – Czech audio and video transcription MCP server?

Transkripce – Czech audio and video transcription is a hosted endpoint at https://transkripce.i-dotaznik.cz/api/v1/transcription/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 · transkripce.i-dotaznik.cz

# add to Claude Code
claude mcp add --transport http com-surveysai-transkripce 'https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp'
Common questions

What is the Transkripce – Czech audio and video transcription MCP server?

Transkripce – Czech audio and video transcription is an MCP server listed in the public MCP registry as com.surveysai/transkripce. Czech audio/video transcription: upload media, run transcription, get transcript and QA report. This page covers its hosted endpoint (https://transkripce.i-dotaznik.cz/api/v1/transcription/mcp).

Is the Transkripce – Czech audio and video transcription MCP server safe to use?

Transkripce – Czech audio and video transcription scores 75 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 Transkripce – Czech audio and video transcription MCP server expose?

Transkripce – Czech audio and video transcription exposes 10 tools: transcription_list_workflows, transcription_get_workflow, transcription_get_transcript, transcription_get_quality_report, transcription_list_audio_files, and 5 more. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.

Does the Transkripce – Czech audio and video transcription MCP server require authentication?

No. We connected to Transkripce – Czech audio and video transcription without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Transkripce – Czech audio and video transcription MCP server still maintained?

Transkripce – Czech audio and video transcription is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Transkripce – Czech audio and video transcription MCP server?

VerifyMCP ran 13 checks on Transkripce – Czech audio and video transcription, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.