mcpbeat Sign in

Deepfake-Lens MCP Server

answering

Deepfake-Lens is answering right now. Last checked moments ago.

Forensic image analyzer detecting facial and visual anomalies.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
95 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check Deepfake-Lens every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add deepfake-lens --transport http https://deepfake-lens-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "deepfake-lens": {
      "url": "https://deepfake-lens-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.deepfake-lens]
url = "https://deepfake-lens-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "deepfake-lens": {
      "url": "https://deepfake-lens-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "deepfake-lens": {
      "url": "https://deepfake-lens-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://deepfake-lens-mcp.vercel.app/api/mcp sse needs auth 72 ms 0 min ago

Alternatives to Deepfake-Lens

same job, measured the same way
Deepfake-Sentinel
by evozim

Media forensic analyzer auditing audio and video authenticity.

answering
identifAI MCP Server
by identifai

Detect AI-generated images, videos, and audio with identifAI's deepfake detection tools.

19 tools answering
AutoTS
by winedarksea

Automated time series forecasting with model search, anomaly detection, and event risk analysis

89 installs/wk local only
Automatic Face Anonymization Image/Video MCP — NoonAI DIS
by dyndns-server-noon-ai

Automatic face detection, anonymization, and de-identification by NoonAI DIS.

answering
Pdf4vllm
by pyjudge

PDF reader for vision LLMs. Auto-detects text corruption and switches to image mode.

139 installs/wk local only
Bynn
by bynn

Document fraud detection for manipulated, fake and AI-generated PDF and image documents.

answering
three.ws Vision
by nirholas

Image understanding for AI agents — analyze and describe any image via the three.ws pipeline.

283 installs/wk local only
MCP Vmanomaly
by victoriametrics-community

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

local only

Deepfake-Lens — questions

Answers built from our own checks of this server.

Why is there no tool list for Deepfake-Lens?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Deepfake-Lens working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 95 ms. The bar chart above shows every period we have measured.
How do I connect Deepfake-Lens?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Deepfake-Lens need an API key?
Yes. Every time we knock, Deepfake-Lens answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Deepfake-Lens?
It answers our handshake in 95 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.