TrustVision

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

C2PA standard visual authenticity scanner and metadata auditor.

VerifiedSSEWeb executableSecurity & MonitoringMedia & Design

Overview

AI-generated overview

Remote MCP server that scans images for C2PA visual authenticity signals and audits their metadata.

What you can do
  • Scan images against the C2PA standard to check visual authenticity.
  • Audit image metadata for provenance and tampering indicators.
  • Premium settlement features are gated behind a payment signature header.
  • No individual tools are documented in the supplied listing.
When to use it
Useful when an assistant needs to judge whether an image is authentic or has been manipulated, or to inspect provenance metadata before trusting or publishing visual content.
Requirements
A remote SSE endpoint at the given host; no local package or runtime is needed. No authentication is declared, but premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The payment-signature header is a cryptographic authorization that can move funds, so treat it as a spending credential and only supply it when you intend to pay. Image data is sent to a third-party hosted service. Tool behavior is undocumented in the listing, so verify what it does before relying on results.

Installation

In SourceWeft

  1. Open TrustVision 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%2Ftrust-vision/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": {
    "trustvision": {
      "type": "sse",
      "url": "https://trust-vision-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.