AI Video Check MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVC_API_KEY | Yes | Your AI Video Check API key. Read in local mode only; the remote server never uses a key from its own environment. | |
| AVC_API_BASE | No | API address. | https://api.aivideocheck.net |
| AVC_MCP_WAIT_S | No | How long `check_video` waits for a result before returning the check id. | 55 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_videoA | Check whether the video at a public link (TikTok, Instagram, X, YouTube, Facebook or a direct file URL) was generated by AI. Spends credits: one per started minute of video. Waits up to about a minute; if the check is not done by then, returns its id for get_check. |
| get_checkA | Get the status or result of an earlier check by its id. Free. Results are kept for 24 hours. |
| get_balanceA | Show how many AI Video Check credits the account has left and the limits of its key. Free. |
| check_fileA | Check whether a video file on this computer was generated by AI. Uploading the original file gives a more reliable result than a link. Spends credits: one per started minute of video. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
check_video and check_file both detect AI-generated video and differ only by input source (public link vs local file), which the descriptions make clear but still requires reading carefully. get_check and get_balance have clearly distinct roles (retrieve result vs account status), so overlap is limited to the two check tools.
All four names follow a strict verb_noun snake_case pattern (check_video, check_file, get_check, get_balance). The verbs are used coherently: check_ for initiating analysis, get_ for retrieving information.
Four tools is well-scoped for a focused detection service: two submission paths, one result retrieval, and one account query. Every tool earns its place with no redundancy or padding.
The submit/retrieve/balance lifecycle is covered, including both URL and file inputs. Minor gaps exist: no way to list or cancel prior checks, and results expire after 24 hours without a cleanup or history operation.