Content Credentials (C2PA)

io.github.contentauthPublished by GitHub account contentauthv0.2.0Updated Oct 27, 2026

Read and verify Content Credentials (C2PA) from images and media using the c2pa Rust SDK

VerifiedSTDIODesktop onlySecurity & MonitoringMedia & Design

Overview

AI-generated overview

Local MCP server that lets an assistant read and verify C2PA Content Credentials embedded in images and media files.

What you can do
  • Read Content Credentials (C2PA manifests) from images and media files
  • Verify the provenance and signature information those credentials carry
  • Work through the c2pa Rust SDK, so results reflect the reference implementation
When to use it
Useful when you need to check where an image or media file came from, confirm whether its Content Credentials are present and valid, or inspect provenance metadata before trusting or publishing an asset.
Requirements
Runs as a local process on the user's machine (desktop only, not web-executable). Installed from a platform-specific mcpb bundle for macOS (Apple Silicon or Intel), Linux (aarch64 or x86_64) or Windows x86_64. No authentication, environment variables or headers are declared.
Before you install
Verification results depend on the credentials embedded in the file and on the c2pa Rust SDK; treat them as evidence about provenance, not proof that content is truthful. No credentials, payments or write actions are declared, but the server reads local media files, so point it only at files you are comfortable exposing to the assistant.

Installation

In SourceWeft

  1. Open Content Credentials (C2PA) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.