All servers · Documents & retrieval · Images & design

DocVerdict

io.github.rogerberent-netizen/docverdict · v1.0.0

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-03-26
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	tools
Tool definitions	4 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

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

streamable-http · https://api.docverdict.com/api/mcp

claude mcp add --transport http docverdict https://api.docverdict.com/api/mcp

{
  "mcpServers": {
    "docverdict": {
      "url": "https://api.docverdict.com/api/mcp"
    }
  }
}

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.

Repository · Website · JSON · Text for agents · Registry updated 2026-07-03