rostrum
PYPI · ROSTRUM
Clean up talk recordings: find redos, retakes and dead air, review every cut, render and verify.
Available components
Last scanned (1 hour ago)
Scores higher than 64% of PyPI servers
Category Design and Media
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
- 2 of 47 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to girishkvs/rostrum). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 915 tokens (~83/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 Management57
- Stability observed for 17 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
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 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 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.
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 pypi/rostrum@0.1.0
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 | girishkvs/rostrum |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/girishkvs/rostrum/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3319454563 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:2277a98e80b32b667bb7a599592da5038a8cbeff45978dbe854594d876c2f4b2 |
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 47 packages
| Packages resolved | 47 |
|---|---|
| Stale | 1 |
| 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 ~89
Transcribe recordings and find proposed cuts. `paths` are video files or folders. Files named like talk-part1, talk-part2 are joined into one talk; every other file is a talk of its own. Writes rostrum.json in project_dir. Long-running: returns a job id.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | – | – | – |
| paths | array | yes | – |
| project_dir | string | yes | – |
No output schema declared.
No examples provided.
decide ~73
Record the user's decision for one cut: decision is "keep" or "cut"; start/end adjust its edges.
| Name | Type | Req | Description |
|---|---|---|---|
| cut_id | string | yes | – |
| decision | string | yes | – |
| end | – | – | – |
| project | – | – | – |
| project_dir | string | yes | – |
| start | – | – | – |
| talk | – | – | – |
No output schema declared.
No examples provided.
doctor ~30
Check ffmpeg, the speech engine, model cache, disk and memory.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | – | – |
No output schema declared.
No examples provided.
import_decisions ~73
Apply a decisions file saved from review.html. For each cut the newer decision wins, so decisions made after the page was built are kept. The result says whether it counts as a review.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| project | – | – | – |
| project_dir | string | yes | – |
| talk | – | – | – |
No output schema declared.
No examples provided.
job_status ~30
Progress and, when finished, the result of a long-running job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
list_cuts ~40
All cut candidates with evidence, for one talk or all talks.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| project_dir | string | yes | – |
| talk | – | – | – |
No output schema declared.
No examples provided.
map_time ~117
Convert a time quoted from a rendered video (e.g. "23:30") to source time, or back with to="output". render_dir is a render folder, its cutmap.json, or a render name such as render-4. With a name, pass talk when more than one talk has a render of that name.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| project_dir | string | yes | – |
| render_dir | string | yes | – |
| talk | – | – | – |
| time | string | yes | – |
| to | string | – | – |
No output schema declared.
No examples provided.
plan ~39
Every cut per talk with reason, level, decision and the expected output length. Never renders.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| project_dir | string | yes | – |
No output schema declared.
No examples provided.
render ~80
Render the reviewed cut list with ffmpeg. Long-running: returns a job id. Set confirmed=true only after the user explicitly said to render; without it, rostrum refuses to render a talk whose cuts nobody has reviewed yet.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | – |
| project | – | – | – |
| project_dir | string | yes | – |
| talk | – | – | – |
No output schema declared.
No examples provided.
status ~37
Summary of every talk in the project: stage, cut counts, expected output length.
| Name | Type | Req | Description |
|---|---|---|---|
| project | – | – | – |
| project_dir | string | yes | – |
No output schema declared.
No examples provided.
verify ~86
Check a render: duration, frames, audio continuity, decode, A/V sync at joins. Without render_dir, checks the newest render of the talk. mode is "fast" or "full". Long-running: returns a job id.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| project | – | – | – |
| project_dir | string | yes | – |
| render_dir | – | – | – |
| talk | – | – | – |
No output schema declared.
No examples provided.
How do I install the rostrum MCP server?
rostrum runs locally as a PyPI package, launched with uvx rostrum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · rostrum
claude mcp add girishkvs-rostrum -- uvx rostrum
What is the rostrum MCP server?
rostrum is an MCP server listed in the public MCP registry as io.github.girishkvs/rostrum. Clean up talk recordings: find redos, retakes and dead air, review every cut, render and verify. This page covers its PyPI package (rostrum).
Is the rostrum MCP server safe to use?
rostrum scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 rostrum MCP server expose?
rostrum exposes 11 tools: analyze, job_status, status, plan, list_cuts, and 6 more. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.
Is the rostrum MCP server still maintained?
rostrum 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 rostrum MCP server under?
rostrum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.