mcp server
DocVerdict
PDF, photo, email, and file comparison evidence checks with plain-language reports.
Description as published by the maintainer. Source
- version 1.0.0
- active
- document understanding
- security
active — Registry entry last updated 2026-07-03. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
compare_pdfs(filename_a, filename_b, file_a_base64, file_b_base64)- 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. Required: file_a_base64, file_b_base64.
verify_email(filename, file_base64)- 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. Required: file_base64.
verify_pdf(filename, file_base64)- 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. Required: file_base64.
verify_photo(filename, file_base64)- 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. Required: file_base64.
Last successful function declaration observed on . Source: https://api.docverdict.com/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.docverdict.com/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.docverdict.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | api.docverdict.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json