DocVerdict

io.github.rogerberent-netizenPublished by GitHub account rogerberent-netizenv1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableFiles & StorageSecurity & Monitoring

Overview

AI-generated overview

DocVerdict checks PDFs, photos and .eml emails for signature, metadata and routing evidence and returns plain-language reports.

What you can do
  • Check a PDF for digital signature status, content added after signing, and metadata observations
  • Check a JPG, PNG or HEIC photo for camera metadata, capture time, edit traces and timestamp consistency
  • Check an .eml email for sender alignment, recorded authentication results and delivery route
  • Compare two PDFs for byte identity, derivation and what changed in pages, metadata or signature events
  • Return findings as JSON plus a plain-language report
When to use it
Useful when you need to weigh documentary evidence — a signed contract, a photo's claimed capture time, an email's sender and route, or two versions of a PDF — and want structured findings with a readable summary rather than a verdict.
Requirements
Remote endpoint at api.docverdict.com over streamable HTTP; no local install. An API key is sent in the Authorization header as a bearer token, self-serve from the provider's developer site. A keyless trial allows 3 calls per day per IP.
Before you install
You must supply an API key in the Authorization header. Files you submit — PDFs, photos, emails — are sent to a third-party service for analysis, so consider whether they contain confidential or personal data. Results classify evidence only and do not determine fraud, authenticity or legal validity, so they should not be treated as conclusions.

Installation

In SourceWeft

  1. Open DocVerdict in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rogerberent-netizen%2Fdocverdict/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

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 validity.

Parametersfilenamefile_base64required

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.

Parametersfilenamefile_base64required

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.

Parametersfilenamefile_base64required

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.

Parametersfilename_afilename_bfile_a_base64requiredfile_b_base64required

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.