Epic Video
REMOTE · MCP.EPICVIDEO.LOL
Generate short AI videos with sound from text prompts, with optional locked characters.
Available components
Last scanned (20 hours ago)
Scores higher than 59% 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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. 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
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 20 Nov 26 +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.
- 19 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Nov 26 +54
- Authorization: unverified → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 17 Nov 26 18
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.epicvideo.lol/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=epicvideo.lol | CN=YE2,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 545333b7d44450893e5f595ac78c2915f76 |
| SANs: *.epicvideo.lol, epicvideo.lol | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.epicvideo.lol. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| lol. | DS published | 60144 | 13 | Verified |
| epicvideo.lol. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="epic-video-mcp", resource_metadata="https://mcp.epicvideo.lol/.well-known/oauth-protected-resource", scope="epicvideo"
Bearer realm="epic-video-mcp", resource_metadata="https://mcp.epicvideo.lol/.well-known/oauth-protected-resource", scope="epicvideo" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Protected resource metadata
| Document | https://mcp.epicvideo.lol/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.epicvideo.lol/mcp |
| Authorisation server | https://mcp.epicvideo.lol |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.epicvideo.lol/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.epicvideo.lol/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 →
create_video ~564
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
get_job_status ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | The job id returned by create_video. |
No output schema declared.
No examples provided.
get_my_usage ~65
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_characters ~38
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_videos ~40
List the signed-in Epic Video user's finished videos, newest first, with playback URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of videos to return. |
No output schema declared.
No examples provided.
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.
remote · mcp.epicvideo.lol
claude mcp add --transport http japage1928-epic-video 'https://mcp.epicvideo.lol/mcp'
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.