mcpbeat

DocVerdict MCP Server

io.github.rogerberent-netizen/docverdict
answering

DocVerdict is answering right now. Last checked 11 min ago. It exposes 4 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
373 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add docverdict --transport http https://api.docverdict.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "docverdict": {
      "url": "https://api.docverdict.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.docverdict]
url = "https://api.docverdict.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "docverdict": {
      "url": "https://api.docverdict.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "docverdict": {
      "url": "https://api.docverdict.com/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
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.
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.
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.
compare
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.

Endpoints

URLTransportStateLatencyChecked
https://api.docverdict.com/api/mcp streamable-http answering 425 ms 11 min ago

DocVerdict — questions

Answers built from our own checks of this server.

What can DocVerdict do?
It exposes 4 tools, read directly from the server on our last check. Among them: compare_pdfs, verify_email, verify_pdf, verify_photo. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DocVerdict working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 373 ms. The bar chart above shows every period we have measured.
Is DocVerdict still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect DocVerdict?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DocVerdict need an API key?
No. DocVerdict completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DocVerdict?
It answers our handshake in 373 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.