com.pagespool/verapdf

veraPDF by pagespool

Is the veraPDF by pagespool MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-04.

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

alive probed 2026-11-14 · unchanged since 2026-11-04 · HTTP 200

2tools

1.6ktokens in Claude Opus 5.5

0.8 %of Claude's 200k window

0.6×the median server

315 msto initialize

160 msto list tools

Endpoint: https://api.pagespool.com/mcp/verapdf/ (streamable-http)
Host: api.pagespool.com
Protocol: 2025-11-25
Reports itself as: pagespool-verapdf 1
Capabilities: experimental, extensions, logging, prompts, resources, tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 1.6k tokens in Claude Opus 5.5, exact, measured 2026-11-04. With the Claude Code prefix mcp__…__ on each tool name: 1.6k. The o200k_base estimate is 994. Counted again when the tool definitions change. Method.
Website: https://pagespool.com
Registry: active, updated 2026-11-04 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.61×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
validate_pdfa	801	497	50 %
check_pdf_accessibility	801	497	50 %

Other registry entries on api.pagespool.com.

Servers that mention verapdf.

EasyAccessPDF io.github.luotwo/easyaccesspdf-mcp · alive
PolyDoc tech.polydoc/polydoc-mcp · alive
PDF/UA accessibility check (veraPDF) with measured auto-fix io.github.nyo-agentti/pdfua-check · not found
Accessibility Agents io.github.Community-Access/accessibility-agents · alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.