# Mark Studios Video Toolkit (remote · mcp.markstudios.com)

Video project tools: platform specs, editing briefs, SRT/WebVTT conversion, turnaround times.

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

## Components

- remote · `mcp.markstudios.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp.md), [page](https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp)

## Channel facts

- Endpoint: `https://mcp.markstudios.com/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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1253 tokens (~179/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Mark Studios Video Toolkit MCP server?

Mark Studios Video Toolkit is a hosted endpoint at https://mcp.markstudios.com/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 com-markstudios-video-toolkit 'https://mcp.markstudios.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-markstudios-video-toolkit": {
      "url": "https://mcp.markstudios.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-markstudios-video-toolkit": {
      "type": "http",
      "url": "https://mcp.markstudios.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-markstudios-video-toolkit]
url = "https://mcp.markstudios.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-markstudios-video-toolkit": {
      "type": "remote",
      "url": "https://mcp.markstudios.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-markstudios-video-toolkit --url 'https://mcp.markstudios.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-markstudios-video-toolkit:
    url: "https://mcp.markstudios.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-markstudios-video-toolkit": {
      "Transport": "http",
      "Url": "https://mcp.markstudios.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-markstudios-video-toolkit -t streamable-http -u 'https://mcp.markstudios.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-markstudios-video-toolkit": {
      "type": "http",
      "url": "https://mcp.markstudios.com/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 69, +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-19 (score 68, +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-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 65)

First indexed and scored.

## MCP tools (7)

### `get_platform_video_specs` (~100 tokens)

Get platform video specs

Maximum length, recommended aspect ratio and resolution for short-form video on YouTube Shorts, Instagram Reels, Facebook Reels, TikTok, Snapchat Spotlight and LinkedIn, read from each platform's own help and developer pages, with the source link for every figure. Use when someone asks how long a Short/Reel/TikTok can be or what size to export.

Input parameters:

- `platform` (string): Which platform; 'all' returns every platform.

### `create_editing_brief` (~599 tokens)

Create a video editing brief

Builds a filled-in 7-section video editing brief (project, audience and goal, references, must-include moments, brand rules, deliverable specs, timeline) from whatever the user already knows, and lists the gaps an editor will ask about. Use when someone is about to hand footage to an editor, freelancer or agency. Pass only fields you know.

Input parameters:

- `approver` (string): Approver: Exactly one person
- `audience` (string): Who it's for: One sentence
- `avoid` (string): What not to copy: The traps to avoid
- `brand_files` (string): Brand files: Lower-thirds, intro, outro, logo
- `captions` (string): Captions: Burned in, SRT file, or both
- `channel` (string): Channel or brand: Where it will be published
- `copy` (string): What to copy: Pacing, captions, color, music, graphics
- `delivery` (string): Delivery: Where final files go
- `donts` (string): Don'ts: Past mistakes not to repeat
- `feeling` (string): How viewers should feel: The reaction you want at the end
- `final_due` (string): Final due: Date and time
- `fonts_colors` (string): Fonts and colors: Font names and HEX codes
- `footage_location` (string): Footage location: The folder link and what's in it
- `kill` (string): KILL: Anything that can't be used
- `length_target` (string): Length target: A target with a hard floor and ceiling
- `master` (string): Master: Resolution, frame rate, audio level
- `metric` (string): The one metric: What success means for this video
- `music` (string): Music rules: Which library or tracks are licensed
- `must` (string): MUST: Timestamps from the raw footage that have to land
- `nice` (string): NICE-TO-HAVE: Moments to use if they fit
- `publish_date` (string): Publish date: Date and time, not just a day
- `references` (string): 2–4 reference videos: Links with timestamps
- `response_time` (string): Response time: How fast you reply to a cut
- `revision_rounds` (string): Revision rounds: How many, in writing
- `rough_cut_due` (string): Rough cut due: Date and time
- `sensitive` (string): SENSITIVE: Faces to blur, legal or private material
- `short_clips` (string): Short clips: Number, ratio and length
- `sponsor` (string): Sponsor read: Where it goes, if any
- `thumbnail_frames` (string): Thumbnail frames: Frames to export as stills
- `working_title` (string): Working title: The title you plan to publish, or the top two options

### `convert_subtitles` (~168 tokens)

Convert or retime subtitles (SRT/WebVTT)

Converts caption text between SubRip (.srt) and WebVTT (.vtt), optionally shifting every timestamp by a number of milliseconds, and reports format problems (missing numbers, comma/period timestamps, captions run together). Runs entirely on the server with the open-source subtitle code used by the markstudios.com caption tools; nothing is stored.

Input parameters:

- `captions` (string, required): The full text of the .srt or .vtt file.
- `filename` (string): Original file name, if known; helps tell .srt from .vtt.
- `shift_ms` (integer): Milliseconds to add to every timestamp (negative moves captions earlier).
- `to` (string): Output format; 'same' keeps the input format (use with shift_ms or to clean up).

### `get_editing_turnaround` (~70 tokens)

Get video editing turnaround

Standard Mark Studios editing turnaround windows by format (vlog, YouTube, talking head, short-form batch, ad, corporate, course, VSL, wedding, monthly plan), plus when the clock starts, rush speeds and revision timing.

Input parameters:

- `format` (string): Format to look up.

### `find_video_editing_service` (~100 tokens)

Find a video editing service

Given a description of a video project (e.g. 'turn my podcast into weekly Reels'), returns the closest-matching Mark Studios editing services with what each includes, its standard turnaround, the service page, and a link to start an instant quote for that service. Use when the user asks who could edit a video or how to get one edited.

Input parameters:

- `need` (string, required): What the user wants made or edited, in their words.

### `start_video_project` (~100 tokens)

Start a video project

Returns a link to the Mark Studios instant quote (start.markstudios.com), preselected for the chosen service, and what happens after: questions about the footage, a price on screen, then upload. It only builds a link; it sends nothing and collects no personal data. Use when the user says they want to hire an editor or get a quote.

Input parameters:

- `service` (string): Service key from find_video_editing_service; omit if unsure.

### `get_monthly_editing_plans` (~54 tokens)

Get monthly editing plans

The four Mark Studios monthly video editing plans with price and what each includes (long videos, Shorts, thumbnails), from markstudios.com/pricing. Use when the user asks what ongoing video editing costs.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66
- 2026-11-15: 66
- 2026-11-14: 65

## Common questions

### What is the Mark Studios Video Toolkit MCP server?

Mark Studios Video Toolkit is an MCP server listed in the public MCP registry as com.markstudios/video-toolkit. Video project tools: platform specs, editing briefs, SRT/WebVTT conversion, turnaround times. This page covers its hosted endpoint (https://mcp.markstudios.com/mcp).

### Is the Mark Studios Video Toolkit MCP server safe to use?

Mark Studios Video Toolkit scores 69 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 Mark Studios Video Toolkit MCP server expose?

Mark Studios Video Toolkit exposes 7 tools: get_platform_video_specs, create_editing_brief, convert_subtitles, get_editing_turnaround, find_video_editing_service, and 2 more. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.

### Does the Mark Studios Video Toolkit MCP server require authentication?

No. We connected to Mark Studios Video Toolkit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mark Studios Video Toolkit MCP server still maintained?

Mark Studios Video Toolkit 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 Mark Studios Video Toolkit MCP server?

VerifyMCP ran 12 checks on Mark Studios Video Toolkit, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Mark Studios Video Toolkit: HTTPS. 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://mcp.markstudios.com/mcp
- Website: https://mcp.markstudios.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-markstudios-video-toolkit/mcp
