# Zovo Subtitle Fix (remote · subtitle-fix.zovo.one)

Fix subtitles that are out of sync, right in the chat.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `subtitle-fix.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix.md), [page](https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix)

## Channel facts

- Endpoint: `https://subtitle-fix.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1256 tokens (~418/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Subtitle Fix MCP server?

Zovo Subtitle Fix is a hosted endpoint at https://subtitle-fix.zovo.one/mcp, so there is nothing to install locally. 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 --transport http theluckystrike-subtitle-fix 'https://subtitle-fix.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-subtitle-fix": {
      "url": "https://subtitle-fix.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-subtitle-fix": {
      "type": "http",
      "url": "https://subtitle-fix.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-subtitle-fix]
url = "https://subtitle-fix.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-subtitle-fix": {
      "type": "remote",
      "url": "https://subtitle-fix.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-subtitle-fix --url 'https://subtitle-fix.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-subtitle-fix:
    url: "https://subtitle-fix.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-subtitle-fix": {
      "Transport": "http",
      "Url": "https://subtitle-fix.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-subtitle-fix -t streamable-http -u 'https://subtitle-fix.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-subtitle-fix": {
      "type": "http",
      "url": "https://subtitle-fix.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 79, +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-11-19 (score 78, +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-11-17 (score 77, +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-11-15 (score 76, +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-11-13 (score 75, +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-11-10 (score 74, +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.

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 73)

First indexed and scored.

## MCP tools (2)

### `fix_subtitles` (~786 tokens)

Fix subtitles

Use this when the user wants to fix subtitle timing or convert subtitles: shift an SRT or VTT file earlier or later, convert it from one frame rate to another (23.976, 24, 25, 29.97, 30, 50, 59.94, 60), sync it on two cues, trim overlapping cues, give short cues a minimum duration, strip formatting tags, renumber, or convert SRT to WebVTT and back. Takes one attached .srt or .vtt file (or the subtitle text) and returns the fixed file and a CSV change log with old and new times per cue. Times are whole milliseconds, rounded half up. Does not listen to audio or find the right offset by itself, does not translate or edit the words, and does not read SSA/ASS files.

Input parameters:

- `file` (object): The subtitle file: one .srt or .vtt file in UTF-8 or UTF-16 with a byte order mark, e.g. movie.srt.
- `fix_overlaps` (boolean): true: when a cue ends after the next cue starts, or less than gap_ms before it, its end moves to gap_ms before that start. Default false.
- `from_fps`: Frame rate the subtitles were timed for, e.g. 25. One of 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60. Use with to_fps.
- `gap_ms` (integer): Gap kept before the next cue when fixing overlaps or extending cues, 0 to 1000 ms, e.g. 1 (default).
- `line_endings` (string): Line endings of the output, e.g. crlf. Default same as the input (CRLF, LF, or CR for old Mac files).
- `min_duration_ms` (integer): Make short cues last at least this long, up to gap_ms before the next cue, e.g. 1000. 0 (default) = off. Limit 10000.
- `output_format` (string): Output format, e.g. vtt to convert SRT to WebVTT. Default same as the input.
- `renumber` (boolean): SRT output: true (default) numbers cues 1, 2, 3 in output order; false keeps the numbers as written.
- `shift_ms` (integer): Move all cues by this many milliseconds: positive = later, negative = earlier, e.g. 2500 (2.5 s later) or -1200. Limit 24 hours.
- `sort_by_start` (boolean): true writes cues in start-time order (stable). Default false keeps the file order.
- `strip_tags` (boolean): true removes formatting tags such as <i>, <b>, <u>, <font>, WebVTT <c>/<v> tags and {\an8} codes from the text. Default false.
- `subtitle_text` (string): Instead of a file: the subtitle text itself, e.g. "1\n00:00:01,000 --> 00:00:03,000\nHello". Use either file or subtitle_text.
- `sync` (object): Two-point sync: cue_a should start at time_a and cue_b at time_b; all times are mapped on that straight line. Do not combine with shift_ms or frame rates.
- `to_fps`: Frame rate of the video they should match, e.g. 23.976. One of 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60. new time = old time x from_fps / to_fps.

Output parameters:

- `changes_preview` (array)
- `changes_preview_count` (object)
- `check` (object)
- `counts` (object)
- `cues_in` (number)
- `cues_out` (number)
- `downloads` (object)
- `encoding` (string)
- `expires_in_hours` (number)
- `file` (string)
- `format_in` (string)
- `format_out` (string)
- `log_name` (string)
- `notes` (array)
- `output_name` (string)
- `removed` (number)
- `timing` (string)

### `check_subtitles` (~281 tokens)

Check subtitles

Use this when the user asks whether an SRT or VTT subtitle file has problems, or wants a report before fixing it: overlapping cues, zero or negative durations, cues out of order, SRT numbering gaps, empty cues, cues too fast to read (characters per second above max_cps, default 20) and lines longer than max_line_chars (default 42). Takes one attached .srt or .vtt file or the subtitle text. Does not make a file and does not change the subtitles; fix_subtitles does that. Does not check spelling, translation or sync with the audio.

Input parameters:

- `file` (object): The subtitle file: one .srt or .vtt file in UTF-8 or UTF-16 with a byte order mark, e.g. movie.srt.
- `max_cps` (number): Reading speed limit in characters per second, 5 to 60, e.g. 17. Default 20.
- `max_line_chars` (integer): Longest line in characters, 20 to 100, e.g. 42 (default).
- `subtitle_text` (string): Instead of a file: the subtitle text itself, e.g. "1\n00:00:01,000 --> 00:00:03,000\nHello". Use either file or subtitle_text.

Output parameters:

- `bad_durations` (object)
- `cues` (number)
- `empty_cues` (object)
- `encoding` (string)
- `fast_cues` (object)
- `file` (string)
- `first_start` (string)
- `format` (string)
- `last_end` (string)
- `long_lines` (object)
- `notes` (array)
- `numbering` (object)
- `out_of_order` (object)
- `overlaps` (object)
- `problems` (number)
- `suggestions` (array)
- `three_plus_lines` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73

## Common questions

### What is the Zovo Subtitle Fix MCP server?

Zovo Subtitle Fix is an MCP server listed in the public MCP registry as io.github.theluckystrike/subtitle-fix. Fix subtitles that are out of sync, right in the chat. This page covers its hosted endpoint (https://subtitle-fix.zovo.one/mcp).

### Is the Zovo Subtitle Fix MCP server safe to use?

Zovo Subtitle Fix scores 79 out of 100 on VerifyMCP. 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 Zovo Subtitle Fix MCP server expose?

Zovo Subtitle Fix exposes 2 tools: fix_subtitles, check_subtitles. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.

### Does the Zovo Subtitle Fix MCP server require authentication?

No. We connected to Zovo Subtitle Fix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Subtitle Fix MCP server still maintained?

Zovo Subtitle Fix is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo Subtitle Fix MCP server?

VerifyMCP ran 14 checks on Zovo Subtitle Fix, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://subtitle-fix.zovo.one/mcp
- Website: https://subtitle-fix.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-subtitle-fix/subtitle-fix
