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.

veraPDF by pagespool

REMOTE · API.PAGESPOOL.COM

Hosted veraPDF: check a PDF against PDF/A or PDF/UA and get the full validation report.

72 Trust /100

Last scanned (4 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 673 tokens (~336/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 72

    First indexed and scored.

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 5 Nov 2026 · Probed https://api.pagespool.com/mcp/verapdf/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.pagespool.com CN=YE1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 54927056eafd7135415646cf7fa6cd50a7a
SANs: api.pagespool.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 4 Jun 2015 4 Jun 2035 RSA 4096 SHA256-RSA 8210cfb0d240e3594463e0bb63828b00

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.pagespool.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pagespool.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https://api.pagespool.com; worker-src 'self' blob:; font-src 'self' data:; frame-ancestors 'none'; form-action 'self' https://polar.sh https://*.polar.sh https://sandbox.polar.sh; base-uri 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.pagespool.com/mcp/verapdf/ Verified 200
http (plaintext) http://api.pagespool.com/mcp/verapdf/ HTTPS enforced 301 https://api.pagespool.com/mcp/verapdf/
MCP tools · 2 exposed · ~673 tokens

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 →

Tool Tokens
check_pdf_accessibility ~350

Check whether a PDF is accessible by PDF/UA, the ISO standard for accessible PDF. veraPDF checks the machine-checkable rules of PDF/UA: tags, structure, alt text present, fonts, metadata. Whether alt text or reading order make sense still needs a person. Input: `pdf_base64` is the PDF as base64, at most 4 MB decoded; or pass the file as a download link in `file`. `profile` is "ua1" or "ua2". Returns `compliant` (true or false), `profile_name`, `statement`, `passed_rules`, `failed_rules` and `top_failed_rules`: up to 10 failed rules with their `id` (clause and test number), `specification`, `description` and `failed_checks`. A file that is not a PDF fails with `not_a_pdf`; an unavailable veraPDF with `engine_unavailable`. For the full report, use the REST API (`POST /v1/verapdf/api/validate/ua1`). Credits: 10 per call.

NameTypeReqDescription
fileobject–The file as a download link, instead of `pdf_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL.
pdf_base64––The PDF, base64-encoded. At most 4 MB decoded.
profilestring–"ua1" (the default) checks against PDF/UA-1 (ISO 14289-1), "ua2" against PDF/UA-2 (ISO 14289-2).

Structured output declared, but exposes no named fields.

No examples provided.

validate_pdfa ~323

Check whether a PDF conforms to PDF/A, the ISO archiving standard, with veraPDF. Input: `pdf_base64` is the PDF as base64, at most 4 MB decoded; or pass the file as a download link in `file`. `profile` picks the PDF/A part and level. Returns `compliant` (true or false), `profile_name` (the profile veraPDF used), `statement`, `passed_rules`, `failed_rules` and `top_failed_rules`: up to 10 failed rules with their `id` (clause and test number), `specification`, `description` and `failed_checks`. A file that is not a PDF fails with `not_a_pdf`; an unavailable veraPDF with `engine_unavailable`. For the full report in JSON, XML or HTML, use the REST API (`POST /v1/verapdf/api/validate/{profile}`). Credits: 2 per call.

NameTypeReqDescription
fileobject–The file as a download link, instead of `pdf_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL.
pdf_base64––The PDF, base64-encoded. At most 4 MB decoded.
profilestring–The PDF/A part and level, such as "2b" or "3a". "auto" (the default) checks against the part the file declares, and against PDF/A-1b when it declares none.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the veraPDF by pagespool MCP server?

veraPDF by pagespool is a hosted endpoint at https://api.pagespool.com/mcp/verapdf/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.pagespool.com

# add to Claude Code
claude mcp add --transport http com-pagespool-verapdf 'https://api.pagespool.com/mcp/verapdf/'
Common questions

What is the veraPDF by pagespool MCP server?

veraPDF by pagespool is an MCP server listed in the public MCP registry as com.pagespool/verapdf. Hosted veraPDF: check a PDF against PDF/A or PDF/UA and get the full validation report. This page covers its hosted endpoint (https://api.pagespool.com/mcp/verapdf/).

Is the veraPDF by pagespool MCP server safe to use?

veraPDF by pagespool scores 72 out of 100 on VerifyMCP. 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.

What tools does the veraPDF by pagespool MCP server expose?

veraPDF by pagespool exposes 2 tools: validate_pdfa, check_pdf_accessibility. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.

Does the veraPDF by pagespool MCP server require authentication?

No. We connected to veraPDF by pagespool without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the veraPDF by pagespool MCP server still maintained?

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