# rostrum (pypi · rostrum)

Clean up talk recordings: find redos, retakes and dead air, review every cut, render and verify.

- Trust score: 69/100 (medium)
- Change this week: −11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `rostrum`: 69/100 (this document), [markdown](https://verifymcp.io/servers/girishkvs-rostrum/rostrum.md), [page](https://verifymcp.io/servers/girishkvs-rostrum/rostrum)

## Channel facts

- Registry: `pypi`
- Package: `rostrum`
- 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-11-05.

- **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 build step with no custom scripting around it.
  - 2 of 47 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to girishkvs/rostrum).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 915 tokens (~83/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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 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.

### Claude

```bash
claude mcp add girishkvs-rostrum -- uvx rostrum
```

### Cursor

```json
{
  "mcpServers": {
    "girishkvs-rostrum": {
      "command": "uvx",
      "args": [
        "rostrum"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "girishkvs-rostrum": {
      "command": "uvx",
      "args": [
        "rostrum"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add girishkvs-rostrum -- uvx rostrum
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add girishkvs-rostrum --command uvx --arg rostrum
```

### Hermes

```yaml
mcp_servers:
  girishkvs-rostrum:
    command: "uvx"
    args: ["rostrum"]
```

### Netclaw

```json
{
  "McpServers": {
    "girishkvs-rostrum": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "rostrum"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add girishkvs-rostrum -t stdio -c uvx -a rostrum
```

### Other

```json
{
  "mcpServers": {
    "girishkvs-rostrum": {
      "command": "uvx",
      "args": [
        "rostrum"
      ]
    }
  }
}
```

## 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-11-05 (score 69, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 83, +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.

### 2026-11-01 (score 82, +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.

### 2026-10-30 (score 81, +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.

### 2026-10-28 (score 80, +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.

### 2026-10-26 (score 79, +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.

### 2026-10-24 (score 78, +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.

### 2026-10-21 (score 77, +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.

## MCP tools (11)

### `analyze` (~89 tokens)

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.

Input parameters:

- `engine`
- `paths` (array, required)
- `project_dir` (string, required)

### `job_status` (~30 tokens)

Progress and, when finished, the result of a long-running job.

Input parameters:

- `job_id` (string, required)

### `status` (~37 tokens)

Summary of every talk in the project: stage, cut counts, expected output length.

Input parameters:

- `project`
- `project_dir` (string, required)

### `plan` (~39 tokens)

Every cut per talk with reason, level, decision and the expected output length. Never renders.

Input parameters:

- `project`
- `project_dir` (string, required)

### `list_cuts` (~40 tokens)

All cut candidates with evidence, for one talk or all talks.

Input parameters:

- `project`
- `project_dir` (string, required)
- `talk`

### `decide` (~73 tokens)

Record the user's decision for one cut: decision is "keep" or "cut"; start/end adjust its edges.

Input parameters:

- `cut_id` (string, required)
- `decision` (string, required)
- `end`
- `project`
- `project_dir` (string, required)
- `start`
- `talk`

### `import_decisions` (~73 tokens)

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.

Input parameters:

- `path` (string, required)
- `project`
- `project_dir` (string, required)
- `talk`

### `render` (~80 tokens)

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.

Input parameters:

- `confirmed` (boolean)
- `project`
- `project_dir` (string, required)
- `talk`

### `verify` (~86 tokens)

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.

Input parameters:

- `mode` (string)
- `project`
- `project_dir` (string, required)
- `render_dir`
- `talk`

### `map_time` (~117 tokens)

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.

Input parameters:

- `project`
- `project_dir` (string, required)
- `render_dir` (string, required)
- `talk`
- `time` (string, required)
- `to` (string)

### `doctor` (~30 tokens)

Check ffmpeg, the speech engine, model cache, disk and memory.

Input parameters:

- `project_dir` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/girishkvs-rostrum/rostrum#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/rostrum/
- Socket report: https://socket.dev/pypi/package/rostrum
- Repository: https://github.com/girishkvs/rostrum
- Changelog RSS feed: https://verifymcp.io/servers/girishkvs-rostrum/rostrum.xml
- Changelog JSON feed: https://verifymcp.io/servers/girishkvs-rostrum/rostrum.json
- HTML version of this page: https://verifymcp.io/servers/girishkvs-rostrum/rostrum