dtelecom-sttofficial
A
licenseA
qualityF
maintenanceEnables AI assistants to transcribe audio files using dTelecom's real-time speech-to-text with pay-per-use USDC micropayments, no API keys required.
3
10 npm
1
MIT
transcribe-mcp
by Soboljem
transcribe-mcp
오디오와 비디오를 텍스트로 변환하고, 잘라낼 가치가 있는 무음 구간을 찾아보세요 — 모든 MCP 클라이언트에서 사용 가능합니다. 계정 불필요, API 키 불필요, 구독 불필요. 여러분의 에이전트는 통화당 1센트 미만의 비용을, 여러분이 통제하는 지갑에서 바로 USDC로 지불합니다.
{
"mcpServers": {
"transcribe": {
"command": "npx",
"args": ["-y", "transcribe-mcp"],
"env": { "TRANSCRIBE_MCP_WALLET_KEY": "0x..." }
}
}
}이것이 설정의 전부입니다. 가입할 것이 아무것도 없습니다.
도구
도구 | 기능 | 가격 |
| 공개 오디오/비디오 URL → 텍스트, 시간 정보, 감지된 언어 | $0.05 |
| 자막 또는 시간 정보 → 잘라낼 가치가 있는 구간과 절약할 수 있는 시간 | $0.002 |
| 가격, 한도 및 결제 작동 방식 | 무료 |
find_dead_air는 transcribe_url이 반환한 결과를 그대로 사용하므로, 두 도구는 연쇄적으로 작동합니다:
강연을 텍스트로 변환한 다음, 그 강연에서 무음 구간을 잘라내세요.
"cuts": [{ "from": 2.55, "to": 10.85, "seconds": 8.3, "reason": "silence" }],
"stats": { "sourceSeconds": 20, "speechSeconds": 5.05, "wouldSavePercent": 74.75 }Related MCP server: framefetch
API 키 대신 통화당 지불 방식을 사용하는 이유
에이전트는 가입 양식을 작성할 수 없기 때문입니다. x402는 HTTP 기반
결제 방식입니다: 서버가 가격과 함께 402 Payment Required로 응답하면, 클라이언트가 이를 지불하고
요청이 처리됩니다. 대시보드, 키 교체, 최소 사용량, 월별 청구서가 없습니다. 호출하지 않으면
비용이 전혀 발생하지 않습니다.
정산은 Base (eip155:8453) 네트워크의 USDC로 이루어집니다.
지갑 없이 실행하기
정상적으로 시작됩니다. shop_info가 응답하고, tools/list가 작동하며, 유료 도구들은 설정해야 할
내용을 알려줍니다. 자금을 충전하기 전에 먼저 확인해보세요.
제공하지 않는 기능
초과 지출하지 않습니다. 모든 호출은 $0.10 상한선을 통해 필터링됩니다. 이보다 높은 견적은 거절되며, 클라이언트는 추측하는 대신 지불을 거부합니다.
거절에 대해 요금을 청구하지 않습니다. 잘못된 인수는 로컬에서 포착되며 기기를 떠나지 않습니다. 상점의
4xx응답은 정산되지 않습니다.판매에 대해 거짓말하지 않습니다. 정산 헤더가 누락된 경우, 증명할 수 없는 결제를 보고하는 대신 그 사실을 알립니다.
파일은 800 KB로 제한됩니다. 초과 크기의 파일은 결제 전에 무료로 거절됩니다.
설정
변수 | 의미 |
| Base 네트워크에 소량의 USDC를 보유한 지갑의 개인 키입니다. 유료 도구에만 필요합니다. |
소량의 자금이 있는 전용 지갑을 사용하세요, 메인 지갑은 사용하지 마세요. 이는 개인 키를 제공하는 모든 도구에 해당되며, 여기서도 마찬가지입니다.
테스트
npm testMIT.
Available Tools
3 toolsfind_dead_airFind the silence worth cuttingA
Given subtitles or timings, return the spans of dead air and how much of the runtime cutting them would save. Costs $0.002 per call — a tenth of transcription, because the expensive half is not redone. Feed it the segments transcribe_url returns.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vtt | No | WebVTT subtitles. Use this or segments, not both. | |
| segments | No | Timings as [{start, end, text}] in seconds — exactly what transcribe_url returns. | |
| durationSeconds | No | Total runtime in seconds. Improves the saving estimate; optional. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the per-call cost, that 'the expensive half is not redone' (implying caching or reuse), and that it returns spans and savings estimates. This is transparent for a read‑only analysis tool, though limits like max input size or error handling are not mentioned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description delivers core purpose in the first sentence, then adds essential usage and cost info in a second sentence. No redundant words; every sentence earns its place. It is front‑loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 3 optional parameters and no output schema. The description explains the input options (VTT or segments), the pipeline from transcribe_url, and the nature of the output (spans and saving estimate). It lacks a precise specification of the return format, but the description is sufficient for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds context about using segments from transcribe_url and the cost, but does not significantly expand on what the parameters mean beyond the schema. The value comes from pipeline guidance rather than parameter detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'the spans of dead air and how much of the runtime cutting them would save,' which is a specific verb+resource. It distinguishes itself from the sibling 'transcribe_url' by focusing on silence detection rather than transcription.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent to 'feed it the segments transcribe_url returns,' establishing a clear pipeline. It also highlights the cost advantage ($0.002 vs. transcription cost). However, it does not explicitly state when not to use this tool (e.g., if no subtitles or timings are available).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
shop_infoWhat this costs before you spend anythingA
Free. Returns the prices, the size limit, the chain and how payment works, so an agent can decide whether to call the paid tools at all.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states the tool is free, which is a key behavioral trait. However, with no annotations, it doesn't disclose auth requirements, side effects, or whether results are cached or dynamic. This partial transparency is adequate for a simple cost-checking tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence front-loaded with 'Free.' It wastes no words while conveying purpose, output, and usage context. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description sufficiently covers what the tool returns and when to use it. It lacks details about response format or authentication, but the low complexity makes it complete enough for a simple info tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters, the input schema requires no explanation. The description adds value by specifying what the tool returns, which is not parameter semantics but does inform the agent's decision to call it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns specific information (prices, size limit, chain, payment) and positions it as a free decision support tool before using paid tools. This distinguishes it from siblings transcribe_url and find_dead_air, which have different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent to use this tool before calling paid tools to decide if they are needed. While it doesn't list exclusions or alternative tools, the context of preventing unnecessary paid calls is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
transcribe_urlTranscribe audio or video from a URLA
Turn a publicly reachable audio or video URL into text with per-segment timings and a detected language. Costs $0.05 per call, paid in USDC from your own wallet. The file must be under 800 KB; oversized files are refused for free before any payment.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http(s) URL of the audio or video file. |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses cost, payment method, file size limit, and refusal policy for oversized files. It also describes output behavior (per-segment timings and language detection). Missing details on error handling for unreachable URLs but overall provides key behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with purpose, each sentence adding non-redundant information (purpose, cost, size limit). Concise without missing critical details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema and no annotations, the description covers purpose, cost, size limit, and output shape (timings, language). It is sufficient for an agent to decide to invoke, though more detail on output format would increase completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a basic param description. The tool description adds value beyond the schema: constraints (public reachable, <800KB), cost, and output details. This helps an agent understand the parameter's context and limits.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool transcribes audio/video from a URL into text with per-segment timings and detected language. The verb 'transcribe' and resource 'audio or video from a URL' are specific and distinct from unrelated sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells when to use: for public URLs needing transcription with timings and language detection. It provides important constraints (file <800KB, cost $0.05, USDC payment). However, it does not explicitly state when to avoid the tool or suggest alternatives, though siblings are unrelated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
v0.1.2- First observed
find_dead_air - First observed
shop_info - First observed
transcribe_url
TDQS
A4.4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool serves a completely distinct role: transcribe_url handles audio-to-text, find_dead_air post-processes timings to find silence, and shop_info provides pricing metadata. There is zero overlap in purpose.
Naming Consistency4/5
Tool names follow a clear verb_noun pattern (transcribe_url, find_dead_air, shop_info) with snake_case. shop_info deviates slightly from the domain-action style of the others, but it is still predictable and readable.
Tool Count5/5
Three tools is perfectly scoped for this server: a core action (transcribe), a derived analysis (find_dead_air), and informational helper (shop_info). No tool feels extraneous, and the count matches the narrow purpose well.
Completeness4/5
The tool surface covers the key transcription workflow and provides a helpful cost info tool. An obvious gap is the lack of an update or delete operation for transcripts, but for a consumption-oriented service this is reasonable. The surface feels complete for its intended use.
Maintenance
ActivitySlowing
ResponsivenessNo issues
Related MCP Connectors
AI transcription from URLs or files. 119 languages, diarization, SRT/VTT/text export.
Transcribe any audio or video URL to text, SRT and VTT, with chunking and only-new episodes
Verbatim transcription of public video/audio URLs to clean text, SRT, and timestamped records.
Pay-per-use AI and data tools via x402: image, video, music, voice, search, crypto. USDC.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAgent-first video-data API + MCP across 6 platforms (YouTube/Shorts, TikTok, Reddit, Instagram, Pinterest): metadata, insights, Whisper transcript, and parametric frames. Pay-per-call via x402 (USDC) or Stripe.28 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to transcribe audio and video from URLs or local files with high accuracy, speaker diarization, 119 languages, and word-level timestamps, while also supporting transcription management and caption export in SRT, WebVTT, or plain text.14264 npm11MIT
- AlicenseNot gradedqualityDmaintenanceEnables extracting clean, structured markdown from any URL—stripping nav, ads, and scripts—for RAG pipelines and AI research agents, with pay-per-call micropayments via x402.MIT