# veraPDF by pagespool

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

- name: com.pagespool/verapdf
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 81/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.pagespool%2Fverapdf
- tools: https://api.protogrid.dev/v1/servers/com.pagespool%2Fverapdf/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "verapdf": {
      "type": "http",
      "url": "https://api.pagespool.com/mcp/verapdf/",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-3d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 81/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: validate_pdfa (destructiveHint, idempotentHint); check_pdf_accessibility (destructiveHint, idempotentHint)
- pass `tools.token_cost`: about 939 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 3 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 939 tokens to load them all
- tool set hash: 9dee9a5c790a465cbaf976773e225228
- badge: [![protogrid quality](https://protogrid.dev/badge/com.pagespool/verapdf.svg)](https://protogrid.dev/servers/com.pagespool/verapdf)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.pagespool.com/mcp/verapdf/ (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `check_pdf_accessibility`: 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.
- `validate_pdfa`: 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.