@txscribe/mcp

MCPcommunity
v0.2.0txscribeMITUpdated todaynpm

MCP server for the txscribe developer API: transcribe a link, read transcripts and summaries from Claude, ChatGPT or any MCP client.

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
378Downloads/wk
todayLast update
Needs 1 credential before it runs
  • TXSCRIBE_API_KEYAPI keyrequired

    A txscribe API key (txs_live_…), made in the app under Plan and billing → Developer API.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authortxscribe
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface8 tools · 1 privileged
Security scan⚠ Warnings (1)v0.2.0 · todayHow well does this scan work?
EvalsNone
IndexedOct 25, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · 1 privileged
Statically extracted from the published packagev0.2.0 · 12h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_transcriptionsThe account's transcriptions, newest first. Pass the previous page's nextCursor to read on.

The account's transcriptions, newest first. Pass the previous page's nextCursor to read on.

No input schema was published for this tool.

transcribe_linkCreate a transcription from a link to a video or recording (YouTube, Google Drive, Dropbox and others; the recording is transcribed, never downloaded).

Create a transcription from a link to a video or recording (YouTube, Google Drive, Dropbox and others; the recording is transcribed, never downloaded).

No input schema was published for this tool.

search_transcriptionsNo description published

This tool published no description. Forge does not invent one.

get_transcriptionStatus and metadata of one transcription: fetching, uploading, preparing, transcribing, done or error.

Status and metadata of one transcription: fetching, uploading, preparing, transcribing, done or error.

No input schema was published for this tool.

get_transcriptThe finished transcript. json gives segments with word timings and speakers (what the app shows); txt, srt and vtt give the file the app's Export menu makes.

The finished transcript. json gives segments with word timings and speakers (what the app shows); txt, srt and vtt give the file the app's Export menu makes.

No input schema was published for this tool.

get_summaryThe summary of a finished transcription and its status. Ask for one with request_summary if there is none yet.

The summary of a finished transcription and its status. Ask for one with request_summary if there is none yet.

No input schema was published for this tool.

request_summaryAsk for a summary of a finished transcription, or a new one. Returns at once with status generating; read it with get_summary.

Ask for a summary of a finished transcription, or a new one. Returns at once with status generating; read it with get_summary.

No input schema was published for this tool.

delete_transcriptionprivilegedDelete a transcription, its media and everything made from it. Cannot be undone.

Delete a transcription, its media and everything made from it. Cannot be undone.

No input schema was published for this tool.

7 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for the txscribe developer API: transcribe a link, read transcripts and summaries from Claude, ChatGPT or any MCP client.

Keywords
mcpmodel-context-protocoltranscriptionspeech-to-texttxscribeclaudechatgpt
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-25 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.