# Verbatim Transcribe (pypi · verbatim-transcribe-mcp)

让 agent 驱动本机的 Verbatim 音视频转写与博主观点分析：提交转写、轮询、搜索转写库。

- Trust score: 59/100 (low)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `verbatim-transcribe-mcp`: 59/100 (this document), [markdown](https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp.md), [page](https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp)

## Channel facts

- Registry: `pypi`
- Package: `verbatim-transcribe-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 30 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 973 tokens (~88/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Verbatim Transcribe MCP server?

Verbatim Transcribe runs locally as a PyPI package, launched with uvx verbatim-transcribe-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add xyzxinlu-max-verbatim-transcribe-mcp -- uvx verbatim-transcribe-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "xyzxinlu-max-verbatim-transcribe-mcp": {
      "command": "uvx",
      "args": [
        "verbatim-transcribe-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyzxinlu-max-verbatim-transcribe-mcp": {
      "command": "uvx",
      "args": [
        "verbatim-transcribe-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add xyzxinlu-max-verbatim-transcribe-mcp -- uvx verbatim-transcribe-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyzxinlu-max-verbatim-transcribe-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "verbatim-transcribe-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyzxinlu-max-verbatim-transcribe-mcp --command uvx --arg verbatim-transcribe-mcp
```

### Hermes

```yaml
mcp_servers:
  xyzxinlu-max-verbatim-transcribe-mcp:
    command: "uvx"
    args: ["verbatim-transcribe-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "xyzxinlu-max-verbatim-transcribe-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "verbatim-transcribe-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyzxinlu-max-verbatim-transcribe-mcp -t stdio -c uvx -a verbatim-transcribe-mcp
```

### Other

```json
{
  "mcpServers": {
    "xyzxinlu-max-verbatim-transcribe-mcp": {
      "command": "uvx",
      "args": [
        "verbatim-transcribe-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 59, −3)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 62, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 60, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 74, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `transcribe_urls` (~149 tokens)

提交视频链接进行转写。支持 YouTube / B站的单个视频、播放列表、合集、频道主页——合集类链接会自动展开成里面的每个视频，各自成为独立任务。

链接行尾可以加时间段只转其中一段，例如 'https://... @10:00-25:00'（时间戳会还原成原视频里的真实位置）。

立刻返回每个视频的 task_id；转写在后台跑，之后用 check_task 查状态、用 get_transcript 取结果。

Input parameters:

- `engine` (string)
- `max_videos` (integer)
- `urls` (string, required)

### `transcribe_file` (~85 tokens)

转写本机上已有的音频/视频文件。走软链不做拷贝，所以大文件也不会占额外磁盘、不需要上传。路径必须是运行 Verbatim 那台机器上的绝对路径。

立刻返回 task_id，之后用 check_task 查状态。

Input parameters:

- `engine` (string)
- `path` (string, required)

### `check_task` (~63 tokens)

查一个转写任务现在是什么状态。status 为 done 时才能用 get_transcript 取结果；failed 时 error 字段说明原因。progress 是 0-100 的百分比（没在跑时为 null）。

Input parameters:

- `task_id` (string, required)

### `get_transcript` (~91 tokens)

取一个已完成转写的正文。默认返回前 4000 字的预览加上元信息（AI 生成的标题、摘要、标签）；要完整全文时传 full=True。

任务还没转完时这里会报找不到，先用 check_task 确认 status 是 done。

Input parameters:

- `full` (boolean)
- `task_id` (string, required)

### `search_transcripts` (~72 tokens)

全文搜索转写库：文件名、AI 标题、标签、转写正文都会被搜到，返回带命中片段的条目。想读某条的完整内容用 get_transcript(task_id)。

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `list_transcripts` (~65 tokens)

列出转写库里的条目（按时间倒序）。source 字段区分来源：'mine' 是用户自己转的，'pipeline' 是博主分析流程产出的。

Input parameters:

- `limit` (integer)
- `source` (string)

### `analyze_creator` (~131 tokens)

对一个博主/频道做系统性观点分析：自动枚举其视频 → 逐个转写 → AI 逐期精读 → 按议题综合成一份总文档。这是重量级长任务，几十个视频可能要跑很久。

立刻返回 chain_id，之后用 check_analysis 查进度、list_analysis_files + get_analysis_file 取产出的文档。

Input parameters:

- `author` (string)
- `engine` (string)
- `lang` (string)
- `max_videos` (integer)
- `url` (string, required)

### `check_analysis` (~56 tokens)

查博主分析的进度。stage 字段是当前阶段（starting / transcribing / analyzing / done / failed / cancelled），videos 里是每个视频各自的状态。

Input parameters:

- `chain_id` (string, required)

### `list_analysis_files` (~40 tokens)

列出某次博主分析产出的所有 Markdown 文档（总分析 + 各期分析）。

Input parameters:

- `chain_id` (string, required)

### `get_analysis_file` (~67 tokens)

读取博主分析产出的某个 Markdown 文档。文件名从 list_analysis_files 拿。默认截断到 8000 字，要全文传 full=True。

Input parameters:

- `chain_id` (string, required)
- `full` (boolean)
- `name` (string, required)

### `verbatim_status` (~44 tokens)

检查 Verbatim 是否在运行，以及各个 AI 引擎的 API key 配置情况。任何工具报连不上时，先用这个确认一下。

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp#diagnostics

## Score history

- 2026-09-20: 59
- 2026-09-19: 62
- 2026-09-18: 62
- 2026-09-17: 61
- 2026-09-16: 61
- 2026-09-15: 60
- 2026-09-14: 60
- 2026-09-13: 74
- 2026-09-12: 59
- 2026-09-11: 58
- 2026-09-10: 58
- 2026-09-09: 58
- 2026-09-08: 57
- 2026-09-07: 57
- 2026-09-06: 56
- 2026-09-05: 56
- 2026-09-04: 55
- 2026-09-03: 55
- 2026-09-02: 69
- 2026-09-01: 54
- 2026-08-31: 68
- 2026-08-30: 68
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 68
- 2026-08-26: 68
- 2026-08-25: 66
- 2026-08-24: 66
- 2026-08-23: 66
- 2026-08-22: 66

## Common questions

### What is the Verbatim Transcribe MCP server?

Verbatim Transcribe is an MCP server listed in the public MCP registry as io.github.xyzxinlu-max/verbatim-transcribe-mcp. 让 agent 驱动本机的 Verbatim 音视频转写与博主观点分析：提交转写、轮询、搜索转写库。 This page covers its PyPI package (verbatim-transcribe-mcp).

### Is the Verbatim Transcribe MCP server safe to use?

Verbatim Transcribe scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Verbatim Transcribe MCP server expose?

Verbatim Transcribe exposes 11 tools: transcribe_urls, transcribe_file, check_task, get_transcript, search_transcripts, and 6 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

### Is the Verbatim Transcribe MCP server still maintained?

Verbatim Transcribe is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Verbatim Transcribe MCP server under?

Verbatim Transcribe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/verbatim-transcribe-mcp/
- Socket report: https://socket.dev/pypi/package/verbatim-transcribe-mcp
- Changelog RSS feed: https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyzxinlu-max-verbatim-transcribe-mcp/verbatim-transcribe-mcp