DeepVoice Guard MCP Server

by evozim Your server? Claim it

answering

DeepVoice Guard is answering right now. Last checked moments ago.

Acoustic deepfake detector and voice biometrics auditor.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

93 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

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

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add deepvoice-guard --transport http https://deepvoice-guard-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "deepvoice-guard": {
      "url": "https://deepvoice-guard-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.deepvoice-guard]
url = "https://deepvoice-guard-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "deepvoice-guard": {
      "url": "https://deepvoice-guard-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "deepvoice-guard": {
      "url": "https://deepvoice-guard-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

URL	Transport	State	Latency	Checked
https://deepvoice-guard-mcp.vercel.app/api/mcp	sse	needs auth	64 ms	0 min ago

Alternatives to DeepVoice Guard

same job, measured the same way

MCP Vmanomaly

by victoriametrics

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

local only

MCP Vmanomaly

by victoriametrics-community

MCP Server for vmanomaly - VictoriaMetrics anomaly detection

local only

Bio-Safe-Audit

by evozim

Biometric data privacy auditor ensuring Zero-Knowledge compliance.

answering

Liongard

by wyre-technology

MCP server for Liongard — inspectors, environments, metrics, detections, and timeline data.

local only

Liongard

by wyre-ai

MCP server for Liongard — inspectors, environments, metrics, detections, and timeline data.

local only

Publishready

by veldica

PublishReady: Deterministic writing control with local-first metrics and AI prose audits.

39 installs/wk local only

AdSpend Auditor

by evozim

PPC advertisement budget auditor grading ad group metrics.

answering

Cronometer

by cphoskins

MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods

333 installs/wk local only

DeepVoice Guard — questions

Answers built from our own checks of this server.

Why is there no tool list for DeepVoice Guard?

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 DeepVoice Guard 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 93 ms. The bar chart above shows every period we have measured.

How do I connect DeepVoice Guard?

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 DeepVoice Guard need an API key?

Yes. Every time we knock, DeepVoice Guard 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 DeepVoice Guard?

It answers our handshake in 93 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.