Verbatim Transcribe
PYPI · VERBATIM-TRANSCRIBE-MCP · SCANNED SEP 20
让 agent 驱动本机的 Verbatim 音视频转写与博主观点分析：提交转写、轮询、搜索转写库。
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 30 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 973 tokens (~88/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
pypi · verbatim-transcribe-mcp
claude mcp add xyzxinlu-max-verbatim-transcribe-mcp -- uvx verbatim-transcribe-mcp
{
"mcpServers": {
"xyzxinlu-max-verbatim-transcribe-mcp": {
"command": "uvx",
"args": [
"verbatim-transcribe-mcp"
]
}
}
} {
"servers": {
"xyzxinlu-max-verbatim-transcribe-mcp": {
"command": "uvx",
"args": [
"verbatim-transcribe-mcp"
]
}
}
} codex mcp add xyzxinlu-max-verbatim-transcribe-mcp -- uvx verbatim-transcribe-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyzxinlu-max-verbatim-transcribe-mcp": {
"type": "local",
"command": [
"uvx",
"verbatim-transcribe-mcp"
],
"enabled": true
}
}
} openclaw mcp add xyzxinlu-max-verbatim-transcribe-mcp --command uvx --arg verbatim-transcribe-mcp
mcp_servers:
xyzxinlu-max-verbatim-transcribe-mcp:
command: "uvx"
args: ["verbatim-transcribe-mcp"] {
"McpServers": {
"xyzxinlu-max-verbatim-transcribe-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"verbatim-transcribe-mcp"
]
}
}
} assistant mcp add xyzxinlu-max-verbatim-transcribe-mcp -t stdio -c uvx -a verbatim-transcribe-mcp
{
"mcpServers": {
"xyzxinlu-max-verbatim-transcribe-mcp": {
"command": "uvx",
"args": [
"verbatim-transcribe-mcp"
]
}
}
} 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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +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.
- 9 Sept 26 +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.
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 20 Sept 2026 · Analysed pypi/verbatim-transcribe-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
analyze_creator ~131
对一个博主/频道做系统性观点分析：自动枚举其视频 → 逐个转写 → AI 逐期精读 → 按议题综合成一份总文档。这是重量级长任务，几十个视频可能要跑很久。 立刻返回 chain_id，之后用 check_analysis 查进度、list_analysis_files + get_analysis_file 取产出的文档。
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| engine | string | – | – |
| lang | string | – | – |
| max_videos | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
check_analysis ~56
查博主分析的进度。stage 字段是当前阶段（starting / transcribing / analyzing / done / failed / cancelled），videos 里是每个视频各自的状态。
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | – |
No output schema declared.
No examples provided.
check_task ~63
查一个转写任务现在是什么状态。status 为 done 时才能用 get_transcript 取结果；failed 时 error 字段说明原因。progress 是 0-100 的百分比（没在跑时为 null）。
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
get_analysis_file ~67
读取博主分析产出的某个 Markdown 文档。文件名从 list_analysis_files 拿。默认截断到 8000 字，要全文传 full=True。
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | – |
| full | boolean | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_transcript ~91
取一个已完成转写的正文。默认返回前 4000 字的预览加上元信息（AI 生成的标题、摘要、标签）；要完整全文时传 full=True。 任务还没转完时这里会报找不到，先用 check_task 确认 status 是 done。
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
list_analysis_files ~40
列出某次博主分析产出的所有 Markdown 文档（总分析 + 各期分析）。
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | – |
No output schema declared.
No examples provided.
list_transcripts ~65
列出转写库里的条目（按时间倒序）。source 字段区分来源：'mine' 是用户自己转的，'pipeline' 是博主分析流程产出的。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
search_transcripts ~72
全文搜索转写库：文件名、AI 标题、标签、转写正文都会被搜到，返回带命中片段的条目。想读某条的完整内容用 get_transcript(task_id)。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
transcribe_file ~85
转写本机上已有的音频/视频文件。走软链不做拷贝，所以大文件也不会占额外磁盘、不需要上传。路径必须是运行 Verbatim 那台机器上的绝对路径。 立刻返回 task_id，之后用 check_task 查状态。
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
transcribe_urls ~149
提交视频链接进行转写。支持 YouTube / B站的单个视频、播放列表、合集、频道主页——合集类链接会自动展开成里面的每个视频，各自成为独立任务。 链接行尾可以加时间段只转其中一段，例如 'https://... @10:00-25:00'（时间戳会还原成原视频里的真实位置）。 立刻返回每个视频的 task_id；转写在后台跑，之后用 check_task 查状态、用 get_transcript 取结果。
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| max_videos | integer | – | – |
| urls | string | yes | – |
No output schema declared.
No examples provided.
verbatim_status ~44
检查 Verbatim 是否在运行，以及各个 AI 引擎的 API key 配置情况。任何工具报连不上时，先用这个确认一下。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.