Chronoverify

io.github.beeswaxpatPublished by GitHub account beeswaxpatv0.1.9Updated Oct 24, 2026

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

The publisher's own server: Brontide agent arena

VerifiedSTDIODesktop onlySecurity & MonitoringMedia & Design

Overview

AI-generated overview

Checks a photo's capture time and provenance via C2PA, EXIF/XMP and pixel forensics, returning a verdict with confidence.

What you can do
  • Verify a photo from a public URL, a local file path or base64 bytes, getting a verdict, 0-100 confidence, capture time, device, location presence, C2PA details and file hashes
  • Optionally store the verdict (not the image) and get an unlisted shareable permalink for citing the result
  • Generate a signed PDF audit report for a local image, saved to a chosen output path
  • Branch on typed structured output rather than parsing prose summaries
When to use it
Useful when an assistant needs to triage whether a photo's metadata is internally consistent, whether it carries valid C2PA Content Credentials, or whether pixel forensics suggest editing, and when a citable verdict or a signed audit record is needed for review, legal, insurance or newsroom workflows.
Requirements
Runs locally over stdio, typically launched with npx, so Node.js is needed. An optional CHRONOVERIFY_API_KEY enables signed reports and non-expiring permalinks; without it, verification uses a free, rate-limited public path. Network access is required, and URL inputs must be publicly reachable.
Before you install
The API key is a secret passed via the CHRONOVERIFY_API_KEY environment variable. Signed reports require a key and are metered as premium report units, so usage may cost money. Requesting a permalink stores the verdict on a third party's servers, and URL inputs are fetched by that service. Results are investigative triage, not proof, and the tool is not a deepfake or AI-generation detector.

Installation

In SourceWeft

  1. Open Chronoverify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

json
{  "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:

json
{  "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

Source: README.md at commit b7f0f6c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.9LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Brontide integrations