DocVerdict

io.github.rogerberent-netizen/docverdict

PDF, photo, email, and file comparison evidence checks with plain-language reports.

healthy

status

tools exposed

683ms

connect latency

0e4610b260dd

schema fingerprint

Tools (4)

verify_pdf

Check one PDF: digital signature status, whether content was added after signing, and metadata observations (creation dates, producing software, edit history). Returns findings JSON and a plain-language report. The result classifies evidence; it never determines fraud, authenticity, or legal validit

verify_photo

Check one photo (JPG, PNG, or HEIC): camera metadata, capture time, edit traces, and timestamp consistency. Observations suggest, never prove, how the image was made and handled.

verify_email

Check one email saved as .eml: sender alignment, authentication results as recorded by the receiving server, and the delivery route. Classifications only — a mismatch is evidence to weigh, not a conclusion.

compare_pdfs

Compare two PDFs: byte identity, whether one file derives from the other, and what changed (pages, metadata, signature events). Reports the relationship the bytes show; it does not decide which file is the right one.

Endpoint

https://api.docverdict.com/api/mcp
Category: Communication · Last checked: 2026-07-30T13:59:27Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access

How we measure →

What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.