Skip to content

DocVerdict

by rogerberent-netizen · remote · no sign-in to list tools · v1.0.0 · published by GitHub user rogerberent-netizen

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

Changes · 3
CompareRegistry entry

4 tools: 3 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 3Claude Code: ask
  • verify_emailCheck one email saved as .eml: sender alignment, authentication results as recorded by the receiving server, and the delivery route.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_pdfCheck one PDF: digital signature status, whether content was added after signing, and metadata observations (creation dates, producing software, edit history).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 validity.
  • verify_photoCheck one photo (JPG, PNG, or HEIC): camera metadata, capture time, edit traces, and timestamp consistency.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Claude Code: allow
  • compare_pdfsCompare two PDFs: byte identity, whether one file derives from the other, and what changed (pages, metadata, signature events).No findings

    Why it is in this group

    • The name "compare_pdfs" says "compare": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__docverdict__compare_pdfs"
    ],
    "ask": [
      "mcp__docverdict__verify_pdf",
      "mcp__docverdict__verify_photo",
      "mcp__docverdict__verify_email"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as docverdict. Review it before you use it.