Transcribe MCP logo

Transcribe MCP

Transcribes public media and identifies removable silence with USDC pay-per-call billing.

Install Transcribe MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "transcribe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "transcribe-mcp"
      ],
      "env": {
        "TRANSCRIBE_MCP_WALLET_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y transcribe-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

The transcribe-mcp MCP server converts public audio or video URLs into text, timings, and detected language. It also analyzes subtitles or timing data to identify dead-air spans and estimate the time saved by cutting them. Calls use x402 payments in USDC on Base, with no account or API key; paid tools require a wallet private key. Reach for it when an agent needs speech-to-text followed by silence-removal analysis.

Use cases

  • Transcribe a public talk or video URL
  • Detect silence ranges in returned timings
  • Estimate how much dead air an edit could remove
  • Inspect service prices and payment limits

Key features

  • Public audio and video URL transcription
  • Transcript timings and detected language
  • Dead-air span detection
  • Estimated duration and percentage savings
  • x402 USDC payments on Base
  • Free pricing and limits lookup

Tools4

What Transcribe MCP lets your agent do. Expand a tool for its parameters.

Self-reported~88 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 22h ago via OSV.dev · transcribe-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads365Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed4Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Transcribe MCP works

What transcribe-mcp MCP server does

The transcribe-mcp MCP server provides MCP tools for two related media-processing tasks: obtaining a transcript from a public audio or video URL, and locating silent sections that may be removed during editing. The transcription result includes text, timing information, and a detected language. The dead-air analysis accepts subtitles or timings and returns candidate cut ranges along with the duration and percentage that could be saved.

The tools are designed to work together. An agent can first call transcribe_url, then pass its timing or subtitle output to find_dead_air. For pricing, usage limits, and payment details, shop_info provides a free discovery call.

How it works

Billing uses the x402 HTTP payment flow rather than an account-based API. A paid request receives a price requirement, the client pays in USDC, and the request proceeds after payment. Settlement takes place on Base, identified as eip155:8453.

The listed prices are $0.05 for transcribe_url and $0.002 for find_dead_air; shop_info does not cost anything. The client applies a $0.10 maximum per call. If a quoted price exceeds that ceiling, the request is rejected instead of being paid. The client also checks for settlement confirmation and does not report a successful payment when the expected settlement header is absent.

Setup and configuration

A standard MCP client can start the package with npx:

config.json
{
  "mcpServers": {
    "transcribe": {
      "command": "npx",
      "args": ["-y", "transcribe-mcp"],
      "env": {
        "TRANSCRIBE_MCP_WALLET_KEY": "0x..."
      }
    }
  }
}

The transcribe-mcp MCP server does not require an account, subscription, or API key. TRANSCRIBE_MCP_WALLET_KEY is needed only for the paid tools and should contain the private key of a wallet holding USDC on Base. A dedicated wallet with a small balance is recommended instead of a primary wallet. Without a wallet, the process can still start, list its tools, and provide shop_info; paid calls explain what configuration is missing.

Tools and capabilities

  • transcribe_url: Accepts a public audio or video URL and returns transcript text, timings, and detected language. The listed price is $0.05 per call.
  • find_dead_air: Accepts subtitles or timing data and reports silence ranges, their duration, and estimated savings. The listed price is $0.002 per call.
  • shop_info: Reports prices, limits, and payment behavior at no charge.

A typical workflow is to transcribe a talk, feed the returned timing data into find_dead_air, and use the resulting ranges for editing decisions. The tool output can include cut objects with start and end positions, duration, and a reason such as silence, plus source, speech, and savings statistics.

Limitations and notes

Inputs are limited to 800 KB. Oversized inputs are refused before payment, so they do not incur a charge. Invalid arguments are also checked locally and do not leave the client. A failed shop response does not settle a payment.

The transcription tool requires a publicly reachable media URL, and the payment wallet must hold USDC on Base for paid requests. The material does not describe private media access, file-upload workflows, editing output, or support for payment networks other than Base.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Transcribe MCP

transcribe-mcp is an MCP server that connects MCP clients to a pay-per-call speech-to-text service over public audio/video URLs. Its main tools are transcribe_url for text, timings, and language; find_dead_air for cuttable silence; and shop_info for pricing, limits, and payment details.

Run it through an MCP client with the command `npx -y transcribe-mcp`. Add `TRANSCRIBE_MCP_WALLET_KEY` to the client environment when using paid tools; the process can start without that variable for tool discovery and `shop_info`.

No, transcribe-mcp does not require an account or API key. Paid calls use a wallet private key and pay in USDC through x402 on Base, while `shop_info` and tool listing work without a funded wallet.

Transcription costs $0.05 per `transcribe_url` call and is paid in USDC on Base through x402. The client rejects quotes above its $0.10 per-call ceiling and checks that settlement occurred before reporting success.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTranscribe MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/transcribe-mcp?style=directory)](https://allmcps.com/mcp/transcribe-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/transcribe-mcp"><img src="https://allmcps.com/api/badge/transcribe-mcp?style=directory" alt="Transcribe MCP on AllMCPs" /></a>