Add the ChronoVerify MCP server
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 PDF audit record).
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.
Hosted endpoint, no install
A remote MCP endpoint is live at https://chronoverify.com/mcp/http: streamable HTTP transport, no auth, running on the free rate-limited path. It exposes one read-only tool, verify_image; get_signed_report needs the npm server with a key. MCP clients can auto-discover it from /.well-known/mcp.json.
{
"mcpServers": {
"chronoverify": {
"type": "http",
"url": "https://chronoverify.com/mcp/http"
}
}
}
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, ormanipulation_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 PDF audit record for one image, the chain-of-custody artifact for compliance, insurance, or newsroom use. Requires an API key.
What a verdict tells you
ChronoVerify returns the photo's capture time, the capture device, the validated provenance state, and the file hashes, as a typed verdict with a confidence. 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
Do I need an API key for the ChronoVerify MCP server?
No to start. Without CHRONOVERIFY_API_KEY, verify_image uses the free, rate-limited public path. A signed report always needs a key.
Which MCP clients are supported?
Any MCP client: Claude Desktop, Claude Code, Cursor, VS Code, Cline, Windsurf, and others. Cursor and VS Code have one-click buttons above; the rest take the config block.
Is ChronoVerify C2PA conformant?
Yes. ChronoVerify is a C2PA Conformant Validator on the C2PA Conforming Products List, record 019f8a20-6452-7a43-b11b-59d0b0e4a84a, covering validation of JPEG, PNG, WebP and AVIF under C2PA specification 2.2. The list is public, so you can check the record yourself. It covers validation rather than generation: ChronoVerify reads and validates Content Credentials, it does not sign them.
See a verdict on a real photo first.
Try the free verifier