Add the ChronoVerify MCP server

Model Context Protocol · npm chronoverify-mcp

Give your AI assistant two tools: verify_image (a photo's capture time and provenance, as a typed verdict) and get_signed_report (a signed, timestamped PDF audit record). Provenance-first, not a deepfake detector.

One click

One click adds the server to your editor. After it is added, open the server's settings to paste a CHRONOVERIFY_API_KEY for metered use; without one it runs on the free public path.

Claude Desktop, Claude Code, Cline, Windsurf

Add this to your MCP configuration (for Claude Desktop, claude_desktop_config.json; for Windsurf, ~/.codeium/windsurf/mcp_config.json), then restart or refresh the MCP server list:

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

Omit the env block to use the free, rate-limited public path. Get a key at pricing.

What your assistant gets

• verify_image: pass a url, a file path, or base64 image bytes; get one verdict (provenance_confirmed, consistent, inconclusive, metadata_anomaly, or manipulation_indicated) with a 0 to 100 confidence, the capture time and device, the C2PA validation state and signer, and the SHA-256 and SHA-512 fingerprints, as typed structured output.
• get_signed_report: write a signed, timestamped PDF audit record for one image, the chain-of-custody artifact for compliance, insurance, or newsroom use. Requires an API key.

What it does and does not tell you

ChronoVerify validates provenance and metadata and flags possible editing for human review. It is not a deepfake or AI-generation detector, and a verdict is investigative triage, not proof. A clean result means a file's saved data is internally consistent, not that the scene it shows is real. Never use a verdict as the sole basis for an automated decision about a person.

Common questions