mcpField
C
ChronoVerify

ChronoVerify

Local
chronoverify.comSecurity2Updated 8w ago

About ChronoVerify

ChronoVerify is an MCP server that checks image provenance, capture time, metadata, and signs of pixel-level editing. Its structured verdicts support investigative triage and human review, rather than serving as proof or deepfake detection.

Key features

  1. 01Validate C2PA credentials against trust lists
  2. 02Read EXIF and XMP metadata
  3. 03Run pixel-level forensics
  4. 04Return typed verdicts with confidence scores
  5. 05Generate signed PDF audit reports

Use cases

  1. 01Check a photo's capture time and provenance
  2. 02Review image evidence for possible editing
  3. 03Create a signed image audit record

MCP support

Exposes `verify_image` and `get_signed_report` tools to MCP clients. The verification tool accepts a URL, local file path, or base64 image; signed reports require an API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"chronoverify": {
"command": "npx",
"args": [
"-y",
"chronoverify-mcp"
],
"env": {
"CHRONOVERIFY_API_KEY": "<CHRONOVERIFY_API_KEY>"
}
}
}
}
Run commandnpx -y chronoverify-mcp
Environment variables to set
CHRONOVERIFY_API_KEYSecretYour ChronoVerify API key (cv_live_...). Optional: omit to use the free, rate-limited public path.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmchronoverify-mcp0.1.9

Tools

2

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
urlstringNoA publicly reachable image URL; the server fetches it.
file_pathstringNoAbsolute path to a local image file to verify.
image_base64stringNoBase64-encoded image bytes (no data: prefix).
permalinkbooleanNoAlso store the verdict (never the image) and return an unlisted, shareable link to it in the permalink field. Keyless links expire after 90 days; links minted with an API key do not expire.

Details

From the project README

chronoverify-mcp

chronoverify-mcp MCP server smithery badge

An MCP server for ChronoVerify. It gives any MCP-compatible AI agent (Claude Desktop, Cursor, Cline, VS Code, and others) the tools to check a photo's capture time and provenance: C2PA Content Credentials, EXIF and XMP metadata, and classical pixel forensics, fused into one verdict (provenance_confirmed, consistent, inconclusive, metadata_anomaly, or manipulation_indicated) with a 0 to 100 confidence.

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

ChronoVerify is a C2PA Conformant Validator, listed on the C2PA Conforming Products List (record 019f8a20-6452-7a43-b11b-59d0b0e4a84a; validation of JPEG, PNG, WebP, and AVIF). Details: https://chronoverify.com/compliance#conformance

Source and issues: github.com/beeswaxpat/chronoverify-mcp

Listed on Smithery: https://smithery.ai/servers/beeswaxpat/chronoverify-mcp

Get an API key (the first 100 verifications each month are included): https://chronoverify.com/pricing . Without a key, verify_image uses the free, rate-limited public path. A signed report requires a key.

Install

Add it to your MCP client config. For Claude Desktop (claude_desktop_config.json) or any MCP client:

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

Omit the env block to use the free public path (verification only; signed reports always need a key).

Tools

verify_image

Verify a photo's capture time and provenance. Takes exactly one of:

  • url: a publicly reachable image URL (the server fetches it),
  • file_path: an absolute path to a local image, or
  • image_base64: base64-encoded image bytes.

Optionally set permalink: true to also store the verdict (never the image) and get back an unlisted, shareable link to it in the permalink field, for citing the result to people or in reports. Keyless links expire after 90 days; links minted with an API key do not expire.

It returns a human-readable summary and a typed structured object so an agent can branch on the result without parsing prose:

{
  "schema_version": "v1",
  "verdict": "consistent",
  "confidence": 58,
  "headline": "Metadata is internally consistent. No manipulation signals fired.",
  "summary": "...",
  "capture_time": { "value": "2026-03-14T09:21:30", "source": "exif", "consistent": null },
  "capture_device": { "make": "Canon", "model": "EOS R6", "software": "Firmware 1.8.1" },
  "capture_location": { "present": false, "place": null },
  "c2pa": {
    "present": false,
    "validated": null,
    "validation_state": null,
    "signature_valid": null,
    "trust_list_match": null,
    "signer": null
  },
  "integrity": {
    "sha256": "1313339a...",
    "sha512": "93a81e4a...",
    "format": "JPEG",
    "width": 1200,
    "height": 800,
    "c2pa_validator_enabled": true
  },
  "permalink": null,
  "limits": "ChronoVerify returns investigative triage, not proof.",
  "source": "ChronoVerify (https://chronoverify.com)"
}

The verdict enum:

  • provenance_confirmed: a trusted C2PA Content Credential validated against the official trust list.
  • consistent: metadata holds up and no manipulation signal fired (consistent with an unedited capture, not proof).
  • inconclusive: not enough signal to decide.
  • metadata_anomaly: the metadata contradicts itself.
  • manipulation_indicated: pixel forensics flagged possible editing for human review.
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, an insurance or legal evidence file, or a newsroom audit trail). Takes one of file_path or image_base64 (this endpoint does not fetch URLs) and an optional out_path. Writes the PDF and returns the path. Requires CHRONOVERIFY_API_KEY; metered as a premium report unit. The report carries an Ed25519 signature you can verify against the public key at https://chronoverify.com/v1/key.

Example prompts

  • "Verify the provenance of /Users/me/Downloads/photo.jpg"
  • "When was the photo at this URL taken, and has it been edited? https://example.com/photo.jpg"
  • "Validate the C2PA Content Credentials on this image and tell me the signer."
  • "Verify this photo and give me a shareable link to the verdict."
  • "Generate a signed provenance report for ./evidence/claim-001.jpg and save it to ./reports/"

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.