C2paintake MCP

What c2paintake-mcp MCP server does

The c2paintake-mcp MCP server connects an AI agent to the hosted C2PA Intake Verifier at https://c2paintake.clauxel.com/mcp. It is intended for AI governance teams, policy reviewers, trust and safety leads, and compliance operators who need a consistent way to inspect C2PA intake and produce evidence for review.

The service exposes five MCP tools: verify_c2pa_intake, classify_source_risk, issue_media_receipt, explain_missing_credentials, and export_intake_log. Together, these tools cover intake verification, source-risk classification, media receipt creation, explanations for absent credentials, and intake-log export.

How it works

An MCP client sends tool calls to the hosted endpoint over streamable HTTP. The server returns structured tool-call output rather than requiring the client to run local application code. Production calls use bearer-token access, so an integrating client must be able to connect to a remote MCP endpoint and provide the required authorization.

A typical workflow can begin by checking an intake with verify_c2pa_intake, then assessing source risk with classify_source_risk. If the result needs an evidence artifact, issue_media_receipt can create a receipt-oriented output. explain_missing_credentials is available for cases where credential information is absent, while export_intake_log supports audit-oriented export.

Setup and configuration

Use the remote MCP endpoint rather than installing a local server from this repository:

https://c2paintake.clauxel.com/mcp

The repository also publishes a server card at https://c2paintake.clauxel.com/server-card.json and identifies the service in the registry as com.clauxel.c2paintake/c2paintake-mcp. Production access requires a bearer token. The provided documentation does not specify token names, environment-variable names, subscription requirements, or client-specific configuration syntax.

The project links to separate website, pricing, checkout, and support pages. Those pages are the appropriate references for access and account questions, while the repository serves as public documentation for the hosted service.

Tools and capabilities

The c2paintake-mcp MCP server advertises these tools:

• verify_c2pa_intake for C2PA intake verification.
• classify_source_risk for classifying source risk.
• issue_media_receipt for issuing media receipts.
• explain_missing_credentials for explaining missing credentials.
• export_intake_log for exporting an intake log.

The documented service capabilities also include structured tool-call output, receipt-oriented evidence export, a public server card, and registry metadata.

Limitations and notes

The GitHub repository contains documentation rather than the production implementation. It does not include production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths. The supplied material describes the endpoint and tool names but does not define detailed input schemas, output fields, verification rules, risk categories, receipt formats, retention behavior, or authentication-token issuance.

The service is remote, so availability and access depend on the hosted endpoint and valid authorization. Review the provider’s pricing and support documentation before designing a production workflow around it.