transcribe-mcp
This MCP server lets an agent transcribe audio/video, find dead air to cut, fetch web pages as markdown, and inspect pay-per-call pricing using USDC on Base.
transcribe_url: transcribe a public audio/video URL (README also supports local audio files) into text, timings, and detected language for $0.05; 800 KB limit.find_dead_air: analyze segments or WebVTT subtitles to find silence spans and estimated savings for $0.002; chains with transcription output.shop_info: free tool returning prices, limits, chain, and payment details.README also describes
fetch_page: convert web pages to clean markdown, with optional JavaScript rendering, for $0.005.Supports
save_tofor large JSON results and a dead-air-cutter skill for end-to-end video cutting.Uses x402 pay-per-call payments from a wallet private key, with local validation and a $0.10 spend ceiling; one paid call at a time per wallet.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@transcribe-mcp transcribe this TED talk URL and find dead air to cut"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
transcribe-mcp
Read web pages as clean markdown, transcribe audio and video, and find the silence worth cutting — from any MCP client. No account, no API key, no subscription. Your agent pays a fraction of a cent per call, in USDC, straight from a wallet you control.
{
"mcpServers": {
"transcribe": {
"command": "npx",
"args": ["-y", "transcribe-mcp@latest"],
"env": { "TRANSCRIBE_MCP_WALLET_KEY": "0x..." }
}
}
}On Windows, MCP clients can't start npx directly, so wrap it:
"command": "cmd", "args": ["/c", "npx", "-y", "transcribe-mcp@latest"].
That is the whole setup. There is nothing to sign up for. It needs Node 20+. The video skill also needs ffmpeg.
One paid call at a time per wallet. The shop refuses a second paid request while one is still running (free, with "already in flight"). Call it sequentially, never in parallel.
Tools
tool | what it does | price |
| a public audio/video | $0.05 |
| subtitles or timings (inline, or | $0.002 |
| a web page → clean markdown, links resolved. | $0.005 |
| prices, limits and how payment works | free |
find_dead_air eats exactly what transcribe_url returns, so the two chain:
transcribe a talk, then cut the silence out of it.
"cuts": [{ "from": 2.55, "to": 10.85, "seconds": 8.3, "reason": "silence" }],
"stats": { "sourceSeconds": 20, "speechSeconds": 5.05, "wouldSavePercent": 74.75 }transcribe_url and find_dead_air take save_to: an absolute path to a new .json file. The full result
goes there and the reply is one line plus the receipt, so an hour of transcripts never floods
your agent's context. It never overwrites a file, and a missing folder is refused before paying.
Cutting a whole video
For cutting a whole video end to end — split, transcribe, cut, synced subtitles — there is a
ready agent skill in skills/dead-air-cutter.
Related MCP server: framefetch
What leaves your machine
transcribe_url: theurl, or the bytes of thefile(audio only —.mp3 .wav .m4a .aac .ogg .opus .oga .flac; a video is refused, extract its audio with ffmpeg first).find_dead_air: the timings and text — fromfrom_file, onlystart,end,textof each segment plusdurationSecondsare sent, whatever else the file holds. If the file has avttfield instead, that subtitle text is sent whole.fetch_page: the page URL.
This server talks only to https://transcribe.soboljem.cz. What the shop does with it, from its
terms:
Audio is never stored. It is transcribed by Cloudflare Workers AI and passes through Cloudflare's infrastructure.
The result is kept briefly, up to about 8 hours. It is replayable for 15 minutes, then deleted by a sweep that runs four times a day. The replay is a shop-side safeguard that this client cannot use: every call signs a new payment. After a timeout or a "may have been charged" reply, check the wallet. Calling again pays again.
A row per sale is kept with no automatic deletion: time, price, audio length, word and cut counts, the source hostname (never the full URL), and the paying wallet address and transaction hash, which are public on Base anyway. Ask via the terms page to have rows deleted.
Payment settles through the PayAI facilitator on Base. On each sale, the shop owner gets a Telegram notification with the shortened payer address and source hostname.
The private key in TRANSCRIBE_MCP_WALLET_KEY never leaves the machine. It only signs.
Why pay-per-call instead of an API key
Because an agent cannot fill in a signup form. x402 is an HTTP-native
payment: the server answers 402 Payment Required with a price, the client pays it, the
request goes through. No dashboard, no key rotation, no minimum, no monthly bill. If you
never call it, you never pay anything.
Settlement is USDC on Base (eip155:8453).
Running it without a wallet
It starts fine. shop_info answers, tools/list works, and the paid tools tell you what
to set. Look before you fund anything.
What it will not do
It will not overspend. Every call is filtered through a $0.10 ceiling; a quote above it is dropped and the client refuses to pay rather than guessing.
It will not charge you for a refusal. Bad arguments are caught locally and never leave your machine. The shop is built not to settle error responses; that was verified on testnet (see its terms).
It will not tell you "no charge" when it cannot know. If the connection drops mid-call, it says a payment may have gone out and to check the wallet before calling again.
It will not lie about a sale. If the settlement header is missing, it says so instead of reporting a payment it cannot prove.
Files are capped at 800 KB. Oversized ones are refused for free, before payment.
A local file is sent to the shop as bytes, so nothing has to be hosted first. For anything
long, extract the audio small and split it — mono Opus at 16 kbps fits ~6 minutes per call:
ffmpeg -i talk.mp4 -vn -ac 1 -c:a libopus -b:a 16k -f segment -segment_time 360 part%03d.opusConfiguration
variable | meaning |
| private key of a wallet holding a little USDC on Base. Required only for the paid tools. |
Use a dedicated wallet with a few dollars in it, not your main one. This is true of every tool you hand a private key to, and it is true here.
Tests
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.
Inputs: vtt, segments, durationSeconds.
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.
Inputs: no named parameters.
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.
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
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.
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.
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.
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
Related MCP Connectors
Pay-per-minute speech-to-text: audio URL to text, SRT or VTT. Paid via x402 or credits.
Clean transcripts of any YouTube video with captions. Pay per call with x402 USDC, no API key.
Transcribe audio and video from a link or local file into text and SRT subtitles. Pay-as-you-go.
Transcribe public audio/video URLs and retrieve transcripts, SRT, and VTT subtitles.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables AI assistants to transcribe audio files using dTelecom's real-time speech-to-text with pay-per-use USDC micropayments, no API keys required.31MIT- 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.11 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.1473 npm9MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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