# Epic Video (remote · mcp.epicvideo.lol)

Generate short AI videos with sound from text prompts, with optional locked characters.

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

## Components

- remote · `mcp.epicvideo.lol`: 73/100 (this document), [markdown](https://verifymcp.io/servers/japage1928-epic-video/mcp.md), [page](https://verifymcp.io/servers/japage1928-epic-video/mcp)

## Channel facts

- Endpoint: `https://mcp.epicvideo.lol/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## 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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 815 tokens (~163/item across 5 items; 5 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.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Epic Video MCP server?

Epic Video is a hosted endpoint at https://mcp.epicvideo.lol/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 japage1928-epic-video 'https://mcp.epicvideo.lol/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "japage1928-epic-video": {
      "url": "https://mcp.epicvideo.lol/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "japage1928-epic-video": {
      "type": "http",
      "url": "https://mcp.epicvideo.lol/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.japage1928-epic-video]
url = "https://mcp.epicvideo.lol/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "japage1928-epic-video": {
      "type": "remote",
      "url": "https://mcp.epicvideo.lol/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add japage1928-epic-video --url 'https://mcp.epicvideo.lol/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  japage1928-epic-video:
    url: "https://mcp.epicvideo.lol/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "japage1928-epic-video": {
      "Transport": "http",
      "Url": "https://mcp.epicvideo.lol/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add japage1928-epic-video -t streamable-http -u 'https://mcp.epicvideo.lol/mcp'
```

### Other

```json
{
  "mcpServers": {
    "japage1928-epic-video": {
      "type": "http",
      "url": "https://mcp.epicvideo.lol/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-20 (score 73, +1)

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

### 2026-11-19 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 72, +54)

- [security regression] Authorization: unverified → fail
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-11-17 (score 18)

First indexed and scored.

## MCP tools (5)

### `create_video` (~564 tokens)

Generate a short AI video with synced sound from a text prompt using Epic Video. Videos are 5, 15, 30, 60 or 120 seconds long; anything over 15 seconds is stitched from chained 5-second clips for consistency. Videos cost tokens per second: 1 token/sec at 480p, 2 tokens/sec at 720p (e.g. a 15-second 480p video costs 15 tokens). Free plans get 15 tokens/week and can make videos up to 15 seconds; 60/120 require the Creator plan ($19.99/mo, 480 tokens/month released 120/week). $4.99/mo = 120 tokens/month released 30/week; $9.99/mo = 240 tokens/month released 60/week. Paid users can also spend top-up tokens bought on the website. Paid plans can attach a locked character (get its id from list_characters) so the same character appears in the video. Image-to-video: pass image_url (a public image URL) and the video will start from that image as its first frame and animate it — the prompt then describes the motion. Returns a job id — poll get_job_status until the status is 'done' to get the video URL. Check get_my_usage first to see the user's tokens left this week/month and top-up balance.

Input parameters:

- `character_id` (integer): Optional id of a locked character from list_characters, so that character appears in the video. Paid plans only.
- `duration_s` (integer): Length in seconds: 5, 15, 30, 60 or 120. Free plans: up to 15. 60/120 require the Creator plan ($19.99/mo). Cost is duration x rate: 1 token/sec at 480p, 2 tokens/sec at 720p.
- `image_url` (string): Optional public URL of an image (JPEG, PNG or WebP, up to 10 MB) to animate: the video starts from this image as its first frame (image-to-video). The server fetches and validates the image; private/…
- `prompt` (string, required): What the video should show, e.g. 'a red sports car on a coastal highway at golden hour, waves crashing'. With image_url, describe the motion instead, e.g. 'the car pulls away and speeds down the coas…
- `quality` (string): Requested quality. The actual quality is set by the user's plan (free and $4.99 plans render 480p; the $9.99 and Creator plans use the user's 720p/480p switch). The returned job shows the real qualit…

### `get_job_status` (~64 tokens)

Check the status of an Epic Video generation job by its job id. Returns the status (queued, rendering, upscaling, done, or failed) and, when done, the video URL.

Input parameters:

- `job_id` (integer, required): The job id returned by create_video.

### `list_my_videos` (~40 tokens)

List the signed-in Epic Video user's finished videos, newest first, with playback URLs.

Input parameters:

- `limit` (integer): Maximum number of videos to return.

### `get_my_usage` (~65 tokens)

Show the signed-in Epic Video user's plan tier, plan tokens left in the current rolling 7-day window and this month, top-up (bonus) token balance, and per-second token rates (1 token/sec at 480p, 2 tokens/sec at 720p).

### `list_characters` (~38 tokens)

List the Epic Video characters available to the signed-in user — their own locked characters plus shared presets — for use with create_video's character_id.

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 18

## Common questions

### What is the Epic Video MCP server?

Epic Video is an MCP server listed in the public MCP registry as io.github.japage1928/epic-video. Generate short AI videos with sound from text prompts, with optional locked characters. This page covers its hosted endpoint (https://mcp.epicvideo.lol/mcp).

### Is the Epic Video MCP server safe to use?

Epic Video scores 73 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 Epic Video MCP server expose?

Epic Video exposes 5 tools: create_video, get_job_status, list_my_videos, get_my_usage, list_characters. Their descriptions and schemas cost roughly 771 tokens of context every time the server is loaded.

### Does the Epic Video MCP server require authentication?

Yes. Epic Video asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Epic Video MCP server still maintained?

Epic Video 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 Epic Video MCP server?

VerifyMCP ran 12 checks on Epic Video, 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 Epic Video: 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.epicvideo.lol/mcp
- Repository: https://github.com/japage1928/epic-video
- Website: https://epicvideo.lol/
- Changelog RSS feed: https://verifymcp.io/servers/japage1928-epic-video/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/japage1928-epic-video/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/japage1928-epic-video/mcp.json
- HTML version of this page: https://verifymcp.io/servers/japage1928-epic-video/mcp
