txscribe
NPM · @TXSCRIBE/MCP · 2 COMPONENTS
Transcribe a link, then read the transcript and summary from your txscribe account.
Available components
Last scanned (4 hours ago)
Scores higher than 37% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 779 tokens (~97/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 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.
- 2 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.
- 31 Oct 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.
- 29 Oct 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.
- 28 Oct 26 +5
- Source repository: fail → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 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.
- 25 Oct 26 59
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@txscribe/mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delete_transcription Delete a transcription ~32
Delete a transcription, its media and everything made from it. Cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_summary Read a summary ~37
The summary of a finished transcription and its status. Ask for one with request_summary if there is none yet.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_transcript Read a transcript ~225
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. A long recording is a lot of text: pass from and to (seconds) for only the paragraphs around a moment, such as a match from search_transcriptions, or summaryOnly for the summary instead. Not ready yet answers with the not_ready error; check get_transcription first.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json, txt, srt or vtt. |
| from | number | – | Seconds into the recording where the stretch to read starts. Paragraphs overlapping it come back whole. |
| id | string | yes | – |
| speakers | boolean | – | Include speaker names. |
| summaryOnly | boolean | – | true: the summary instead of the transcript, as get_summary returns it. Leave format, from and to out with it: they are not used. |
| timestamps | boolean | – | txt: include the time of each paragraph. |
| to | number | – | Seconds into the recording where it ends. |
No output schema declared.
No examples provided.
get_transcription Transcription status ~39
Status and metadata of one transcription: fetching, uploading, preparing, transcribing, done or error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The transcription id. |
No output schema declared.
No examples provided.
list_transcriptions List transcriptions ~73
The account's transcriptions, newest first. Pass the previous page's nextCursor to read on.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous page. |
| limit | integer | – | Page size. |
| status | string | – | The API's filter: all, active (still working), done, error. |
No output schema declared.
No examples provided.
request_summary Request a summary ~78
Ask for a summary of a finished transcription, or a new one. Returns at once with status generating; read it with get_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | Output language; defaults to the transcript's. |
| scene | string | – | meeting, interview, lecture, … Omit to let the model choose. |
No output schema declared.
No examples provided.
search_transcriptions Search transcriptions ~124
Which of the account's recordings said something, and when. Looks for the words as one phrase in what was said (not in titles), in the newest 500 recordings (ones still processing or failed among them are skipped; truncated is true when there may be older ones, which are not read): give a distinctive word or short phrase, not a question. Each result has up to five matches with the second each starts at; read around one with get_transcript's from and to rather than reading the whole transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The word or phrase. |
No output schema declared.
No examples provided.
transcribe_link Transcribe a link ~171
Create a transcription from a link to a video or recording (YouTube, Google Drive, Dropbox and others; the recording is transcribed, never downloaded). Starts at once and uses the account's minutes. Returns the transcription with its id; poll get_transcription until status is done, then read get_transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| captions | boolean | – | YouTube only: use the video's own captions when they fit; uses no minutes. |
| diarization | boolean | – | Label speakers (default true; not every language supports it). |
| language | string | – | "auto", or one of the codes the API lists in openapi.json — a full tag such as en-US, pt-BR or es-MX, never "en". Omit for automatic detection. |
| url | string | yes | The link. |
No output schema declared.
No examples provided.
How do I install the txscribe MCP server?
txscribe runs locally as an npm package, launched with npx -y @txscribe/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @txscribe/mcp
claude mcp add ai-txscribe-txscribe -- npx -y @txscribe/mcp
What is the txscribe MCP server?
txscribe is an MCP server listed in the public MCP registry as ai.txscribe/txscribe. Transcribe a link, then read the transcript and summary from your txscribe account. This page covers its npm package (@txscribe/mcp).
Is the txscribe MCP server safe to use?
txscribe scores 69 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 txscribe MCP server expose?
txscribe exposes 8 tools: list_transcriptions, transcribe_link, search_transcriptions, get_transcription, get_transcript, and 3 more. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.
Is the txscribe MCP server still maintained?
txscribe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the txscribe MCP server under?
txscribe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.