Video Dept. AI
REMOTE · AGENTS.VIDEODEPARTMENT.ORG
Plan a video and script with VIDEO DEPT. in Fort Lauderdale, send a brief, book a call with Nikita.
Available components
Last scanned (4 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_brief). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2597 tokens (~236/item across 11 items; 11 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 Management10
- Stability observed for 3 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 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.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “send_brand_guide” rewrote its description, which is the text the model reads security
- Schema quality: 2243 → 2597 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “get_brief_status” functional
- New tool “get_upload_link” functional
- 2 Nov 26 62
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 5 Nov 2026 · Probed https://agents.videodepartment.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=videodepartment.org | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1464e83d5d7b25d131cfb4b61090ed9 |
| SANs: videodepartment.org, agents.videodepartment.org, *.agents.videodepartment.org | ||||||
| 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 agents.videodepartment.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| videodepartment.org. | absent | 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://agents.videodepartment.org/mcp | Verified | 200 | |
| http (plaintext) | http://agents.videodepartment.org/mcp | HTTPS enforced | 301 | https://agents.videodepartment.org/mcp |
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 →
book_call Book a free call with Nikita ~262
Books a free 30-minute video call with Nikita Marushkov at one of the times from find_call_times. The call goes on Nikita's calendar, and Google Calendar emails the user an invite with the Google Meet link; the result also has a link to cancel. It books the call only. Call it once, after the user has seen the exact time in their own time zone and their contact details and agreed.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | yes | What the user wants to talk about, in a sentence or two, in their own words. |
| company | string | yes | The user's company. |
| string | yes | The user's email address, where the invite goes. | |
| name | string | yes | The user's full name. |
| phone | string | – | Optional: the user's phone number, if they want Nikita to call or text them about this call. It isn't put in the invite. |
| start | string | yes | The exact start from find_call_times, copied as is with its time zone offset, e.g. "2026-11-04T14:00:00-05:00". |
| time_zone | string | – | Optional: the user's time zone, e.g. America/Chicago, to show the time in it. |
No output schema declared.
No examples provided.
draft_a_script Get a script outline for a video ~125
Returns an outline for the script of a video: the parts in order, their rough timing, how many spoken words fit, the two-column format and the rules for writing it. Use it when the user wants a script draft. You write the draft with the user from the outline, and it goes to Nikita with the brief (send_brief). It sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| length_seconds | integer | – | Optional: the planned length in seconds, if the user knows it. |
| video_type | string | – | The kind of video, the same choices as plan_a_video. |
No output schema declared.
No examples provided.
find_call_times Find a time for a free call with Nikita ~152
Returns Nikita Marushkov's open times for a free 30-minute video call (Google Meet): Monday to Friday, 10 AM–6 PM Eastern (the last call starts at 5 PM), at least 4 hours ahead and up to two weeks out. Each time has an exact start to pass to book_call. Give the user's time zone to see the times in their own time zone too.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Optional: the first day to look at, as YYYY-MM-DD, within the next two weeks. Leave empty for the next open times. |
| time_zone | string | – | Optional: the user's time zone, e.g. America/Chicago or Europe/London. |
No output schema declared.
No examples provided.
get_booking_link Get Nikita's booking page ~86
Returns the page where the user books a free 30-minute video call with Nikita Marushkov, the studio's founder, and the hours calls can be booked. The user picks a time on that page, or an agent that can open web pages does it for them after the user agrees to the time and contact details. The page shows times in the user's own time zone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_brief_status Check on a brief sent to Nikita ~128
Returns where a brief sent with send_brief stands: with Nikita, replied, or a fixed quote sent, and any free call booked. Give the brief number (like A-12) and the email it was sent with, exactly as in send_brief's receipt. It shows only the status and dates, never the reply itself, which goes to that email. It changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | The brief number from send_brief's receipt, e.g. "A-12". |
| string | yes | The email address the brief was sent with. |
No output schema declared.
No examples provided.
get_deposit_link Get the deposit link for a fixed quote ~202
For a client who already has a fixed quote from Nikita (it has a number like Q-12). Give the quote number and the email it was sent to, exactly as in Nikita's email. Returns the quote and a Stripe payment link for its 50% deposit; the balance is due when the project is finished. It doesn't pay or accept anything: the user opens the link and pays there themselves, and card details go only to Stripe. The project is booked once the payment goes through. The deposit is fully refundable until the user and Nikita reach the final agreement on a call or at a meeting, and if VIDEO DEPT. can't do the date, the user gets all of it back.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address the quote was sent to, exactly as in Nikita's email. | |
| quote | string | yes | The quote number exactly as in Nikita's email, e.g. "Q-12". |
No output schema declared.
No examples provided.
get_studio_info About VIDEO DEPT. ~91
Returns what VIDEO DEPT. makes, its posted prices, typical timelines, service area, languages, examples of its work and how quotes, calls and deposits work. Use it when the user asks what the studio does or costs, or before planning a video with VIDEO DEPT.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional: services, prices, timeline, area, work or contact. Leave empty for everything. |
No output schema declared.
No examples provided.
get_upload_link Get a private link to send files ~192
Returns a private web page where the user uploads files for Nikita at VIDEO DEPT. from their own computer or phone: footage, photos, logos, references or documents, up to 20 files and 20 GB in all. Use it when the user wants to send files that aren't online. Give the user the link; they open it and choose the files themselves. The link works for 24 hours. Only Nikita can open the files, and they are deleted from the upload storage after 30 days. Making the link sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | Optional: the brief number (like A-12), the quote number (like Q-12) or the project name these files are for. |
| company | string | yes | The user's company. |
| string | yes | The user's email address, where Nikita can reply. | |
| name | string | yes | The user's full name. |
No output schema declared.
No examples provided.
plan_a_video Plan a video with VIDEO DEPT. ~111
Returns what is needed to plan a video with VIDEO DEPT.: the 10 brief questions, formats, the typical timeline (or the step-by-step process for courses, video podcasts and studio setups) and a what-to-prepare checklist. A brief with at least 4 answered questions can then be sent with send_brief.
| Name | Type | Req | Description |
|---|---|---|---|
| video_type | string | – | The kind of video: event, interview, brand_film, product, social, course, video_podcast, podcast_studio or other. |
No output schema declared.
No examples provided.
send_brand_guide Send the company's brand guidelines ~373
Sends Nikita a company's brand guidelines for a video: links to the brand book, logo and font files, the brand colors and fonts, logo rules and tone of voice. Use it when the user wants VIDEO DEPT. to have their brand guidelines, usually with or after a brief. Links must be web addresses the user gives, for example Google Drive, Dropbox or the company's site. For files that aren't online, give the user a private upload link (get_upload_link), or they can email them to nikita@videodepartment.org. This sends the details to Nikita and can't be taken back: show the user exactly what you'll send and ask first.
| Name | Type | Req | Description |
|---|---|---|---|
| colors | array | – | Optional: the brand colors, up to 8, each as a hex code with an optional name, like Navy #0A2342. |
| company | string | yes | The company whose brand this is. |
| string | yes | The user's work email, where Nikita can reply. | |
| fonts | array | – | Optional: the brand font names, up to 4. |
| links | array | – | Up to 5 web addresses (starting with https://) of the brand book, logo or font files, exactly as the user gave them. |
| logo_rules | string | – | Optional: how the logo may and may not be used, in plain words. |
| name | string | yes | The user's full name. |
| notes | string | – | Optional: anything else Nikita should know, such as colors or music to avoid. |
| project | string | – | Optional: the brief number (like A-12), the quote number (like Q-12) or the project name this is for. |
| tone | string | – | Optional: the brand's tone of voice, in a few words. |
No output schema declared.
No examples provided.
send_brief Send a video brief to VIDEO DEPT. ~349
Sends one video brief to Nikita at VIDEO DEPT. for an exact fixed quote, with the user's name and email so he can reply. It is built from the user's own answers to the plan_a_video questions and needs at least 4 of the 10 answered. Each call sends a new brief and cannot be taken back, so call it once, after the user has seen the exact brief and their contact details and agreed.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who exactly is watching? |
| budget | string | – | What's the budget range? |
| company | string | yes | The user's company. |
| deadline | string | – | What's the hard deadline, and why? |
| deliverables | string | – | What exactly should be delivered? |
| string | yes | The user's email address, where Nikita sends the quote. | |
| logistics | string | – | What are the shoot logistics? |
| message | string | – | What's the one message they must remember? |
| name | string | yes | The user's full name. |
| outcome | string | – | What single business outcome should this video drive? |
| phone | string | – | Optional: the user's phone number, if they want Nikita to call or text them about this brief. |
| placements | string | – | Where will the video live? |
| project_name | string | yes | A short name for the video, e.g. "Spring launch film". |
| references | string | – | Which videos do you like? |
| script_draft | string | – | Optional: the script draft you wrote with the user from draft_a_script, exactly as the user approved it. Nikita uses it as a starting point. |
| success | string | – | How will you measure success? |
No output schema declared.
No examples provided.
How do I install the Video Dept. AI MCP server?
Video Dept. AI is a hosted endpoint at https://agents.videodepartment.org/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 · agents.videodepartment.org
claude mcp add --transport http org-videodepartment-agents 'https://agents.videodepartment.org/mcp'
What is the Video Dept. AI MCP server?
Video Dept. AI is an MCP server listed in the public MCP registry as org.videodepartment/agents. Plan a video and script with VIDEO DEPT. in Fort Lauderdale, send a brief, book a call with Nikita. This page covers its hosted endpoint (https://agents.videodepartment.org/mcp).
Is the Video Dept. AI MCP server safe to use?
Video Dept. AI scores 64 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 Video Dept. AI MCP server expose?
Video Dept. AI exposes 11 tools: get_studio_info, plan_a_video, draft_a_script, get_booking_link, send_brief, and 6 more. Their descriptions and schemas cost roughly 2,071 tokens of context every time the server is loaded.
Does the Video Dept. AI MCP server require authentication?
No. We connected to Video Dept. AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Video Dept. AI MCP server still maintained?
Video Dept. AI 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.