Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PolyDoc

NPM · POLYDOC-MCP · SCANNED SEP 20

HTML/URL to PDF, screenshots, e-invoices. PDF/A and PDF/UA output with optional veraPDF verify.

Available components

npm · polydoc-mcp 38
−11 this week 38 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security63
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to polydoc-tech/polydoc-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
  • Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the PolyDoc MCP server?

PolyDoc runs locally as an npm package, launched with npx -y polydoc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · polydoc-mcp

# add to Claude Code
claude mcp add tech-polydoc-polydoc-mcp -- npx -y polydoc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "tech-polydoc-polydoc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "polydoc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tech-polydoc-polydoc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "polydoc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add tech-polydoc-polydoc-mcp -- npx -y polydoc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-polydoc-polydoc-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "polydoc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tech-polydoc-polydoc-mcp --command npx --arg -y --arg polydoc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  tech-polydoc-polydoc-mcp:
    command: "npx"
    args: ["-y", "polydoc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tech-polydoc-polydoc-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "polydoc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add tech-polydoc-polydoc-mcp -t stdio -c npx -a -y polydoc-mcp
// mcp.json
{
  "mcpServers": {
    "tech-polydoc-polydoc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "polydoc-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Dependency health: 0.85 → unverified ▼ functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.6 → 0.1.7 functional
  • 18 Sept 26 0
    • Package version: 0.1.4 → 0.1.6 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Aug 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 12 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.85 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/polydoc-mcp@0.1.7

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo polydoc-tech/polydoc-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/polydoc-tech/polydoc-mcp/.github/workflows/release.yml@refs/tags/v0.1.7
Rekor log index 2898407258
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:4268f18683c0c5cb90312dbccb7784d92e8c054364f1fc8b0edcbf25a06f1df94db17ef4313c3600b53f07f13cdf4d1b3f22528fafb40914aa1359e9d

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the PolyDoc MCP server?

PolyDoc is an MCP server listed in the public MCP registry as tech.polydoc/polydoc-mcp. HTML/URL to PDF, screenshots, e-invoices. PDF/A and PDF/UA output with optional veraPDF verify. This page covers its npm package (polydoc-mcp).

Is the PolyDoc MCP server safe to use?

PolyDoc scores 38 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the PolyDoc MCP server still maintained?

PolyDoc is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the PolyDoc MCP server under?

PolyDoc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.