Mark Studios Video Toolkit
REMOTE · MCP.MARKSTUDIOS.COM
Video project tools: platform specs, editing briefs, SRT/WebVTT conversion, turnaround times.
Available components
Last scanned (16 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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.
- 19 Nov 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.
- 17 Nov 26 +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.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 65
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.markstudios.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=markstudios.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 88e5003942fef488133dc7f83090503c |
| SANs: markstudios.com, mcp.markstudios.com, *.mcp.markstudios.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.markstudios.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| markstudios.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.markstudios.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.markstudios.com/mcp | Inconclusive | 405 |
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 →
convert_subtitles Convert or retime subtitles (SRT/WebVTT) ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| captions | string | yes | 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). |
No output schema declared.
No examples provided.
create_editing_brief Create a video editing brief ~599
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
find_video_editing_service Find a video editing service ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What the user wants made or edited, in their words. |
No output schema declared.
No examples provided.
get_editing_turnaround Get video editing turnaround ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format to look up. |
No output schema declared.
No examples provided.
get_monthly_editing_plans Get monthly editing plans ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_platform_video_specs Get platform video specs ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Which platform; 'all' returns every platform. |
No output schema declared.
No examples provided.
start_video_project Start a video project ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | Service key from find_video_editing_service; omit if unsure. |
No output schema declared.
No examples provided.
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.
remote · mcp.markstudios.com
claude mcp add --transport http com-markstudios-video-toolkit 'https://mcp.markstudios.com/mcp'
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.