DocVerdict
io.github.rogerberent-netizen/docverdict · v1.0.0
PDF, photo, email, and file comparison evidence checks with plain-language reports.
MCPremoteAPI keyImages, video & audioDocuments & PDFEmail
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 4 tools, protocol 2025-03-26 · checked 2026-10-17
Test & rating
B 83/100
What it does: 4 tools · 4 read, 0 write · Documents & PDF, Law & government, Images, video & audio
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://api.docverdict.com/api/mcpTools
4 tools listed at last check
verify_pdfCheck 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 validitverify_photoCheck 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_emailCheck 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_pdfsCompare 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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.rogerberent-netizen/docverdict)