ChronoVerify
https://chronoverify.com/mcp/http ↗
Description
**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
What our measurements say
ChronoVerify is a remote MCP server published at chronoverify.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 406 ms, placing it among the faster endpoints. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Clear purpose in verifying image provenance and capture time
- Deterministic pipeline with C2PA validation
Weaknesses
- No input schema details for parameters
- Truncated description cuts off critical info
- No explicit error handling documentation
verify_image— Description lacks use case contextverify_image— No parameter definitions or required fields specifiedverify_image— Incomplete description truncates pipeline explanation
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from unknown to legacy · Agent transitioned to legacy era, indicating recognized compliance state
- 2026-09-11T01:59:45.474Z — Compliance score set to 100 · Achieved full compliance, but smoke test status remains unresolved
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 221ms → warm 623ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.7
- Supported versions: — → 2025-11-25
- Era changed: Unknown → Legacy
- Added to watch — era: Unknown
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/beeswaxpat-chronoverify-mcp)<a href="https://mcpmetrics.io/servers/beeswaxpat-chronoverify-mcp"><img src="https://mcpmetrics.io/badge/beeswaxpat/chronoverify-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see