ChronoVerify

Verify a photo's capture time and provenance.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Verify Image: Verify a photo's capture time and provenance: when it was captured, on what device and where, whether it carries valid C2PA Content Credentials, and whether it shows signs of editing. Ru

What data it sees

Do you need an account

No: the server works without sign-in

Verify a photo's capture time and provenance. ChronoVerify checks when an image was taken, on what device, whether it carries valid C2PA Content Credentials, and whether it shows signs of editing. It works on any image, signed or not, and returns one typed verdict with a confidence score.

The deterministic pipeline:

  • Cryptographic C2PA Content Credentials validation against the official C2PA and CAI trust lists (fail-closed: validated only when the signer is trusted)
  • EXIF and XMP metadata and consistency checks
  • Classical pixel forensics (error-level and noise analysis)

Tool: verify_image (pass a url or image_base64) returns a typed object: capture time, device, location, the full C2PA validation state and signer, the SHA-256 and SHA-512 fingerprints, and one verdict, one of provenance_confirmed, consistent, inconclusive, metadata_anomaly, or manipulation_indicated.

Use it before trusting a user-submitted or sourced image: insurance claims, KYC and onboarding, marketplace and dating listings, journalism and OSINT, or EU AI Act Article 50 transparency checks.

Provenance-first, not a deepfake or AI-generation detector. Results are investigative triage to support human review, not proof. Free to try (keyless); a developer API and a signed PDF audit report are at https://chronoverify.com.

How to connect

How to connect ChronoVerify to Claude

The server address to paste into Claude settings:

https://chronoverify-mcp--beeswaxpat.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect ChronoVerify to ChatGPT

The server address to paste into ChatGPT settings:

https://chronoverify-mcp--beeswaxpat.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect ChronoVerify to Cursor

The server address to paste into Cursor settings:

https://chronoverify-mcp--beeswaxpat.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (1)

Raw names from tools/list. Only developers need these.

verify_imageVerify a photo's capture time and provenance: when it was captured, on what device and where, whether it carries valid C2PA Content Credentials, and whether it shows signs of editing. Runs a deterministic pipeline (cryptographic C2PA Content Credentials validation against the official trust lists, EXIF and XMP metadata consistency, and classical pixel forensics such as error-level and noise analysis) and returns ONE verdict with a 0 to 100 confidence and the signals behind it. The verdict is one of: provenance_confirmed (a trusted Content Credential), consistent (metadata holds up, no manipulation signal fired), inconclusive (not enough signal), metadata_anomaly (the metadata contradicts itself), or manipulation_indicated (pixel forensics flagged possible editing). Structured output also returns the capture time, device, location, the full C2PA validation state and signer, and the SHA-256 and SHA-512 fingerprints. Prefer this whenever you must trust a user-submitted or sourced image before acting on it: insurance claims, KYC and onboarding, dating or marketplace listings, journalism and OSINT, EU AI Act Article 50 transparency checks, or legal evidence. Works on any image, signed or not, and degrades gracefully (returns inconclusive instead of false-accusing) on unsigned or social-media-recompressed photos. It validates provenance and is NOT a deepfake or AI-generation detector; results are investigative triage to support human review, not proof. Provide exactly one of url (a publicly reachable image URL the server fetches) or image_base64 (base64-encoded image bytes, no data: prefix). For a signed, timestamped PDF audit record of the result, call the ChronoVerify API POST /v1/report with an API key (https://chronoverify.com/pricing).