Skip to content

DocVerdict MCP server

io.github.rogerberent-netizen/docverdictrogerberent-netizenstreamable-httpv1.0.0Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DocVerdict MCP server can do

The DocVerdict MCP server is published by the GitHub account rogerberent-netizen. It has 4 tools. It can create or change data (3 tools: verify_pdf, verify_photo and verify_email), but cannot delete data. 1 tool only reads.

1 tool reads private data (compare_pdfs).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • verify_emailCheck one email saved as .eml: sender alignment, authentication results as recorded by the receiving server, and the delivery route.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_pdfCheck one PDF: digital signature status, whether content was added after signing, and metadata observations (creation dates, producing software, edit history).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_photoCheck one photo (JPG, PNG, or HEIC): camera metadata, capture time, edit traces, and timestamp consistency.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • compare_pdfsCompare two PDFs: byte identity, whether one file derives from the other, and what changed (pages, metadata, signature events).Reads private dataNo findings

    Why it is in this group

    • The name "compare_pdfs" says "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "compare" and "file": it reads files.
    • private-dataThe input names a file (input.file_a_base64), and the tool reads: it reads files.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.docverdict.com/api/mcp: tools/list returned 4 tools to an anonymous client, including verify_pdf (write), verify_photo (write), verify_email (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http docverdict https://api.docverdict.com/api/mcp
claude mcp add --transport http docverdict https://api.docverdict.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__docverdict__compare_pdfs"
    ],
    "ask": [
      "mcp__docverdict__verify_pdf",
      "mcp__docverdict__verify_photo",
      "mcp__docverdict__verify_email"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docverdict. Review it before you use it.

Capability tags behind 1 rule
  • mcp__docverdict__compare_pdfs private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.rogerberent-netizen/docverdict/verify?hash=effe5c504f6ad09a516598972c1c7901b2eeac0aae0a815fa6907e8932313f1d" | jq -e '.changed == false'

Pinned hash effe5c504f6a, from Nov 20, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.rogerberent-netizen/docverdict/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.rogerberent-netizen/docverdict
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.rogerberent-netizen/docverdict.svg)](https://radar.anlyon.com/servers/io.github.rogerberent-netizen/docverdict)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:46 UTC.

DocVerdict MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DocVerdict MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DocVerdict MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DocVerdict MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DocVerdict MCP server have?

4 tools: 3 write, 1 read. verify_pdf, verify_photo, verify_email and compare_pdfs.

Does the DocVerdict MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DocVerdict MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DocVerdict MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.