Deepfake-Sentinel

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Media forensic analyzer auditing audio and video authenticity.

VerifiedSSEWeb executableMedia & Design

Overview

AI-generated overview

A remote media forensic analyzer that lets an assistant audit audio and video files for authenticity and possible deepfake manipulation.

What you can do
Submit audio or video media for forensic authenticity analysis and review the results. The server is described as a media forensic analyzer auditing audio and video authenticity. No individual tools are listed, so the exact operations are not documented. Premium settlement appears to be a separate, paid capability.
When to use it
Useful when you need a second opinion on whether a clip or recording is authentic, for example before publishing or acting on user-submitted media. It suits occasional verification checks rather than bulk media processing, since the available operations are not documented.
Requirements
A remote SSE endpoint; nothing to install locally. For premium settlement, a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature is required. No accounts or environment variables are declared.
Before you install
Premium settlement requires a payment-signature header, meaning a signed authorization that can move funds; treat it as a spending credential and only supply it deliberately. Media you submit is sent to a third-party remote service, so avoid confidential or personal recordings. The tool set is undocumented, so verify behavior before relying on results.

Installation

In SourceWeft

  1. Open Deepfake-Sentinel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fdeepfake-sentinel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "deepfake-sentinel": {
      "type": "sse",
      "url": "https://deepfake-sentinel-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.