Security & Testing

docverdict.com

Verify digital files and emails for authenticity, metadata, and tampering evidence.

1 endpoint4 known toolsFirst detected June 17, 2026Last detected August 29, 2026

ENDPOINT 1

https://api.docverdict.com/api/mcp

No auth detected

MCP server metadata

Name: DocVerdict
Version: 1.0.0

Capabilities

tools

Server instructions

DocVerdict verifies documents and reports what their own evidence shows. Every result is a set of classifications and findings, never a determination of fraud, authenticity, or legal validity — treat the output as evidence for a person to weigh, and say so when you relay it. Files are analyzed in memory and never stored; only derived findings JSON is kept, for 7 days, under the report token.

Known 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).

Potential side effects

verify_photo

Check one photo (JPG, PNG, or HEIC): camera metadata, capture time, edit traces, and timestamp consistency.

Potential side effects

verify_email

Check one email saved as .eml: sender alignment, authentication results as recorded by the receiving server, and the delivery route.

Potential side effects

compare_pdfs

Compare two PDFs: byte identity, whether one file derives from the other, and what changed (pages, metadata, signature events).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.docverdict]
url = "https://api.docverdict.com/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: docverdict
Remote MCP URL: https://api.docverdict.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "docverdict",
  "transport": "streamable-http",
  "url": "https://api.docverdict.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for docverdict.com was fetched 2026-07-26T01:55:56.127Z and is being refreshed.

Trust status Neutral

docverdict.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.