# 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.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agents.videodepartment.org`: 64/100 (this document), [markdown](https://verifymcp.io/servers/org-videodepartment-agents/agents.md), [page](https://verifymcp.io/servers/org-videodepartment-agents/agents)

## Channel facts

- Endpoint: `https://agents.videodepartment.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_brief).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 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).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http org-videodepartment-agents 'https://agents.videodepartment.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-videodepartment-agents": {
      "url": "https://agents.videodepartment.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-videodepartment-agents": {
      "type": "http",
      "url": "https://agents.videodepartment.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-videodepartment-agents]
url = "https://agents.videodepartment.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-videodepartment-agents": {
      "type": "remote",
      "url": "https://agents.videodepartment.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-videodepartment-agents --url 'https://agents.videodepartment.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-videodepartment-agents:
    url: "https://agents.videodepartment.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-videodepartment-agents": {
      "Transport": "http",
      "Url": "https://agents.videodepartment.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-videodepartment-agents -t streamable-http -u 'https://agents.videodepartment.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-videodepartment-agents": {
      "type": "http",
      "url": "https://agents.videodepartment.org/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-05 (score 64, +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-03 (score 63, +1)

- [security] 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
- [functional regression] Schema quality: 2243 → 2597
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “get_brief_status”
- [functional] New tool “get_upload_link”

### 2026-11-02 (score 62)

First indexed and scored.

## MCP tools (11)

### `get_studio_info` (~91 tokens)

About VIDEO DEPT.

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.

Input parameters:

- `topic` (string): Optional: services, prices, timeline, area, work or contact. Leave empty for everything.

### `plan_a_video` (~111 tokens)

Plan a video with VIDEO DEPT.

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.

Input parameters:

- `video_type` (string): The kind of video: event, interview, brand_film, product, social, course, video_podcast, podcast_studio or other.

### `draft_a_script` (~125 tokens)

Get a script outline for a video

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.

Input parameters:

- `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.

### `get_booking_link` (~86 tokens)

Get Nikita's booking page

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.

### `send_brief` (~349 tokens)

Send a video brief to VIDEO DEPT.

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.

Input parameters:

- `audience` (string): Who exactly is watching?
- `budget` (string): What's the budget range?
- `company` (string, required): The user's company.
- `deadline` (string): What's the hard deadline, and why?
- `deliverables` (string): What exactly should be delivered?
- `email` (string, required): 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, required): 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, required): 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?

### `send_brand_guide` (~373 tokens)

Send the company's brand guidelines

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.

Input parameters:

- `colors` (array): Optional: the brand colors, up to 8, each as a hex code with an optional name, like Navy #0A2342.
- `company` (string, required): The company whose brand this is.
- `email` (string, required): 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, required): 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.

### `get_brief_status` (~128 tokens)

Check on a brief sent to Nikita

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.

Input parameters:

- `brief` (string, required): The brief number from send_brief's receipt, e.g. "A-12".
- `email` (string, required): The email address the brief was sent with.

### `get_upload_link` (~192 tokens)

Get a private link to send files

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.

Input parameters:

- `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, required): The user's company.
- `email` (string, required): The user's email address, where Nikita can reply.
- `name` (string, required): The user's full name.

### `find_call_times` (~152 tokens)

Find a time for a free call with Nikita

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.

Input parameters:

- `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.

### `book_call` (~262 tokens)

Book a free call with Nikita

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.

Input parameters:

- `about` (string, required): What the user wants to talk about, in a sentence or two, in their own words.
- `company` (string, required): The user's company.
- `email` (string, required): The user's email address, where the invite goes.
- `name` (string, required): 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, required): 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.

### `get_deposit_link` (~202 tokens)

Get the deposit link for a fixed quote

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.

Input parameters:

- `email` (string, required): The email address the quote was sent to, exactly as in Nikita's email.
- `quote` (string, required): The quote number exactly as in Nikita's email, e.g. "Q-12".

## Diagnostics

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

## Score history

- 2026-11-05: 64
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://agents.videodepartment.org/mcp
- Repository: https://github.com/Maroosh1/video-dept-ai
- Website: https://videodepartment.org/ai-assistant
- Changelog RSS feed: https://verifymcp.io/servers/org-videodepartment-agents/agents.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-videodepartment-agents/agents.json
- HTML version of this page: https://verifymcp.io/servers/org-videodepartment-agents/agents