io.github.neugence/whipscribe-mcp
PYPI · WHIPSCRIBE-MCP
Transcribe audio/video files or URLs via the WhipScribe cloud API and fetch the transcript.
Available components
Last scanned (13 hours ago)
Scores higher than 68% of PyPI 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 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 build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to neugence/whipscribe-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 542 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 22 Oct 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.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Oct 26 +17
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 22 Oct 2026 · Analysed pypi/whipscribe-mcp@0.1.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | neugence/whipscribe-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/neugence/whipscribe-mcp/.github/workflows/publish.yml@refs/tags/v0.1.5 |
| Rekor log index | 3079773568 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c5be961579ed2d3f2289ee7f1c31c6d2d4dbee3cbd3f0943a3fc1430d9ba6cef |
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 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
get_job_status ~38
Poll the current status of a transcription job by job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Identifier returned by a previous transcribe_* call. |
No output schema declared.
No examples provided.
get_transcript ~65
Fetch a finished transcript in the requested format. Returns a 300-character preview plus a link to the full transcript; large transcripts are not inlined in the MCP response.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. |
| job_id | string | yes | Identifier of a completed job. |
No output schema declared.
No examples provided.
list_recent_jobs ~59
List jobs submitted from this machine (local SQLite cache). Stores only job_id, source kind, status, duration, and created-at timestamp — never URLs, file paths, or transcripts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of jobs to return. |
No output schema declared.
No examples provided.
transcribe_file ~101
Transcribe a local audio or video file. The path is never sent to telemetry. Polls until the job is done or the poll timeout elapses.
| Name | Type | Req | Description |
|---|---|---|---|
| diarize | boolean | – | Label speakers in the transcript. |
| language | string|null | – | ISO 639-1 language code. Auto-detect when omitted. |
| path | string | yes | Absolute path to a local media file. |
| word_timestamps | boolean | – | Include per-word timing. |
No output schema declared.
No examples provided.
transcribe_url ~129
Transcribe audio or video from a URL (direct media link, podcast episode, or Creative-Commons YouTube). Polls until the job is done or the poll timeout elapses, then returns a transcript preview plus a link to the full transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| diarize | boolean | – | Label speakers in the transcript. |
| language | string|null | – | ISO 639-1 language code (e.g. 'en', 'es'). Auto-detect when omitted. |
| url | string | yes | Direct media URL or supported share URL. |
| word_timestamps | boolean | – | Include per-word timing. |
No output schema declared.
No examples provided.
transcribe_urls_batch ~150
Transcribe a list of URLs (YouTube, podcast, direct media) concurrently. Submit up to 20 URLs in one call; each job runs in parallel and the tool returns when all are done or failed. Per-URL failures do not abort the batch. Ideal for building a second-brain knowledge base from a playlist or a curated list of videos.
| Name | Type | Req | Description |
|---|---|---|---|
| diarize | boolean | – | Label speakers in every transcript. |
| language | string|null | – | ISO 639-1 language code. Auto-detect when omitted. |
| urls | array | yes | List of media URLs to transcribe (max 20). |
| word_timestamps | boolean | – | Include per-word timing in every transcript. |
No output schema declared.
No examples provided.
How do I install the io.github.neugence/whipscribe-mcp server?
io.github.neugence/whipscribe-mcp runs locally as a PyPI package, launched with uvx whipscribe-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 · whipscribe-mcp
claude mcp add neugence-whipscribe-mcp -- uvx whipscribe-mcp
What is the io.github.neugence/whipscribe-mcp server?
io.github.neugence/whipscribe-mcp is listed in the public MCP registry as io.github.neugence/whipscribe-mcp. Transcribe audio/video files or URLs via the WhipScribe cloud API and fetch the transcript. This page covers its PyPI package (whipscribe-mcp).
Is the io.github.neugence/whipscribe-mcp server safe to use?
io.github.neugence/whipscribe-mcp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. 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 io.github.neugence/whipscribe-mcp server expose?
io.github.neugence/whipscribe-mcp exposes 6 tools: transcribe_url, transcribe_file, get_job_status, get_transcript, list_recent_jobs, transcribe_urls_batch. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.
Is the io.github.neugence/whipscribe-mcp server still maintained?
io.github.neugence/whipscribe-mcp is still listed as active in the MCP registry. We last reached this channel on 22 October 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 io.github.neugence/whipscribe-mcp server under?
io.github.neugence/whipscribe-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.