Chronoverify MCP Server

Verify a photo's capture time and provenance: C2PA validation, EXIF/XMP, and pixel forensics.

Local serverstdio

What is the Chronoverify MCP server?

Connect Chronoverify to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Verify a photo's capture time and provenance: C2PA validation, EXIF/XMP, and pixel forensics. The chronoverify mcp server is what makes that connection.

What the server does

Provenance-first, not a deepfake or AI-generation detector. Results are investigative triage to support human review, not proof.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • verify_image — Verify a photo's capture time and provenance. Takes exactly one of:
  • get_signed_report — Generate a signed PDF audit report for one image: the chain-of-custody / compliance record (for example an EU AI Act Article 50 transparency record

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Credentials and setup notes

Configuration is passed through the environment: CHRONOVERIFY_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Chronoverify's toolset — verify_image, get_signed_report — is a fair guide to whether it matches your workflow. It is maintained by beeswaxpat; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
verify_imageVerify a photo's capture time and provenance. Takes exactly one of:
get_signed_reportGenerate a signed PDF audit report for one image: the chain-of-custody / compliance record (for example an EU AI Act Article 50 transparency record, an insurance or legal evidence file, or a newsroom audit trail). Takes

How to install the Chronoverify MCP server

{
  "mcpServers": {
    "chronoverify": {
      "command": "npx",
      "args": ["-y", "chronoverify-mcp"],
      "env": { "CHRONOVERIFY_API_KEY": "cv_live_..." }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CHRONOVERIFY_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Chronoverify to verify image.
  • Use Chronoverify to get signed report.

Frequently asked questions

It connects Chronoverify to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (verify_image, get_signed_report) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Chronoverify directly.