Deepfake-Sentinel MCP server
Checked 2026-09-07. Alive: no. Handshake: unknown.
Category: security. API and field schema.
Facts
| id | registry--io.github.evozim--deepfake-sentinel |
| name | Deepfake-Sentinel |
| registry_name | io.github.Evozim/deepfake-sentinel |
| repo_url | not available |
| endpoint_url | https://deepfake-sentinel-mcp.vercel.app/api/mcp |
| transport | sse |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | no |
| check_installable | not verifiable |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T18:47:56Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:402 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 2540 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | security |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://deepfake-sentinel-mcp.vercel.app/api/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.