Caption File Check MCP server

• caption_checkFree

  Preflight one caption or subtitle file before delivery. Attach a WebVTT (.vtt), SRT (.srt), or TTML/IMSC (.ttml/.xml) caption file in chat or give a publicly fetchable URL and it downloads the artifact under an SSRF-guarded, 2 MB-capped fetch, detects the format by content and the byte encoding and BOM, then parses it with the real spec engine (the WebVTT spec parser, a dedicated SRT parser, or the imscJS TTML/IMSC profile engine) and returns deterministic evidence: pass/fail, cue count, structural spec and IMSC profile-conformance errors, overlapping / negative / out-of-order / empty cues, per-line length, and per-cue and summary reading speed (CPS) against a named platform profile (netflix-adult-20, netflix-children-17, youtube, ebu-tt). It reports only source-file conformance, timing, encoding, and reading-speed facts against a dated profile. It does not judge translation quality, transcription accuracy, or synchronization against the video. An arbitrary XML or text file that is not a caption track returns an explicit unsupported-format error. Fetching and parsing a full-length track can take up to 60 seconds.

• caption_compareFree

  Compare exactly two caption or subtitle files under identical bounded checks: an original versus its translated track, before versus after a timing fix, or a format migration. Attach two WebVTT, SRT, or TTML/IMSC caption files in chat or give two publicly fetchable URLs and it runs the same SSRF-guarded, 2 MB-capped preflight as caption_check on each, then aligns them by cue index and reports side-by-side pass status, detected-format and encoding differences, the cue-count delta, timing drift and overlap differences, reading-speed (CPS) regressions, structural-error deltas, and a winner only when the measured checks separate the two. Use caption_check for a single file. It reports only source-file conformance, timing, encoding, and reading-speed facts against a dated profile: never translation quality, transcription accuracy, or sync against the video. Fetching and parsing two live files can take up to 60 seconds.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 468ms20/20
• Tool poisoning2 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Caption File Check: common questions

Is Caption File Check MCP server safe?

With care: it is graded C, so read the findings first (69/100). Read the Caption File Check safety report

How do I install Caption File Check?

It runs remotely at powmcp.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Caption File Check need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Caption File Check maintained?

The latest release is v0.3.2.

Is Caption File Check up?

100% of our last 6 checks got an answer. We check remote servers about four times a day.