AI & Machine Learning
aivideocheck.net
Checks whether a video at a public link was AI-generated and reports check status or account credit balance.
ENDPOINT 1
https://api.aivideocheck.net/mcp
MCP server metadata
- Name
- AI Video Check
- Version
- 1.0.0
Use these tools to check whether a video was generated by AI. Pass a public link to check_video. Report the result with its caveats; never present a score as proof. Each check spends credits from the user's AI Video Check account (one credit per started minute of video).
Known tools 3
check_videoCheck whether the video at a public link (TikTok, Instagram, X, YouTube, Facebook or a direct file URL) was generated by AI.
Inferred read-onlyget_balanceShow how many AI Video Check credits the account has left and the limits of its key.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ai-video-check]
url = "https://api.aivideocheck.net/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ai-video-check": {
"type": "http",
"url": "https://api.aivideocheck.net/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ai-video-check
Remote MCP URL: https://api.aivideocheck.net/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ai-video-check": {
"url": "https://api.aivideocheck.net/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ai-video-check": {
"type": "http",
"url": "https://api.aivideocheck.net/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ai-video-check",
"transport": "streamable-http",
"url": "https://api.aivideocheck.net/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.