Security & Testing
chronoverify.com
Verifies photo authenticity and provenance, including capture time, device, location, C2PA credentials, and editing signs.
ENDPOINT 1
https://chronoverify.com/mcp/http
MCP server metadata
- Name
- chronoverify
- Version
- 0.1.7
ChronoVerify verifies a photo's capture time and provenance: it reads EXIF and XMP, cryptographically validates C2PA Content Credentials against the official trust lists, runs classical pixel forensics, and returns one plain-language verdict with a confidence score and a typed verdict object. It works on any image, signed or not. Provenance-first, not a deepfake or AI-generation detector; results are investigative triage, not proof.
Known tools 1
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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.chronoverify]
url = "https://chronoverify.com/mcp/http"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"chronoverify": {
"type": "http",
"url": "https://chronoverify.com/mcp/http"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: chronoverify
Remote MCP URL: https://chronoverify.com/mcp/http
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"chronoverify": {
"url": "https://chronoverify.com/mcp/http"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"chronoverify": {
"type": "http",
"url": "https://chronoverify.com/mcp/http"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "chronoverify",
"transport": "streamable-http",
"url": "https://chronoverify.com/mcp/http"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.