Checks a PDF against PDF/UA-1 with veraPDF, reports failed rules, and measures what an automatic fix removes.
What you can do
Validate a PDF against PDF/UA-1 with veraPDF and list every failed rule with rule id, description, failed-check count and an explanation link
Re-run the automatic fix on the file and validate again to show which failures it removes and whether the file then passes
Explain a single veraPDF PDF/UA-1 rule by id: what it checks, the error message, whether the auto-fix removes it, and how to fix it in the authoring tool
When to use it
Useful when you need to audit a PDF for accessibility compliance, triage which PDF/UA failures are fixable automatically, or look up what a specific veraPDF rule means before editing the source document.
Requirements
Remote streamable HTTP endpoint; no authentication, environment variables or headers declared. Accepts a file or a URL to an online PDF. A check takes roughly 10 to 60 seconds.
Before you install
The server states that files are not stored, but PDFs are uploaded to a third-party hosted endpoint, so avoid confidential documents. The automatic fix modifies the file, so keep the original. Results depend on veraPDF and are not a formal conformance certification.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.nyo-agentti%2Fpdfua-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Validate a PDF against PDF/UA-1 with veraPDF and list every failed rule (rule id, description, number of failed checks, link to a plain-language explanation). The automatic fix is then run on the file and validated again, so the result also says which failures the fix removes and whether the file then passes — measured on this file, not estimated. Give either 'url' (a public http(s) address of the PDF, max 10 MB) or 'pdf_base64'. The file is not stored and the fixed file is not returned here.
Parametersurllanguagepdf_base64
explain_pdfua_rule
Explain a PDF/UA-1 rule
Explain a veraPDF PDF/UA-1 rule by id (clause-test, e.g. 7.1-3, 7.3-1, 7.18.5-1, 7.21.4.1-1): what it checks, the veraPDF error message, whether the automatic fix removes it and how to fix it in the authoring tool.
Parametersrulerequired
Version history
1
v1.0.0LatestOct 26, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.