PDF/UA accessibility check (veraPDF) with measured auto-fix MCP Server

by nyo-agentti Your server? Claim it

answering

PDF/UA accessibility check (veraPDF) with measured auto-fix is answering right now. Last checked 5 min ago. It exposes 2 tools.

Check PDFs against PDF/UA-1 with veraPDF; see which failures an automatic fix removes; explain rules

Uptime history 4 hours of history

4 hours agonow

100.0%

Uptime 24h

12 of 12 checks

Tools

read from the server

112 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check PDF/UA accessibility check (veraPDF) with measured auto-fix every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pdfua-check --transport http https://pdfua-check.onrender.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://pdfua-check.onrender.com/mcp

~/.codex/config.toml

[mcp_servers.pdfua-check]
url = "https://pdfua-check.onrender.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "pdfua-check": {
      "url": "https://pdfua-check.onrender.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "pdfua-check": {
      "type": "http",
      "url": "https://pdfua-check.onrender.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

explain

explain_pdfua_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.

pdf

check_pdf_accessibility

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.

Endpoints

URL	Transport	State	Latency	Checked
https://pdfua-check.onrender.com/mcp	streamable-http	answering	154 ms	5 min ago

Alternatives to PDF/UA accessibility check (veraPDF) with measured auto-fix

same job, measured the same way

EasyAccessPDF

by luotwo

PDF accessibility checks (veraPDF PDF/UA-1), auto-fix and Markdown conversion. EU-hosted.

5 tools answering

Epub A11y Metadata Lint

by jmshinhwa

18 rules over the accessibility metadata in your .opf: 12 findings in the sample file, 9 of them err

25 installs/wk local only

Inclusio MCP

by sebastienrousseau

Inclusio MCP server for accessibility-first LaTeX publishing (PDF/UA-2, WTPDF, PDF/A-4f).

77 installs/wk local only

Spotlight

by thrain

Local PDF accessibility audit: machine-checkable PDF/UA basics (ADA/EAA/508). No uploads.

22 installs/wk local only

PDF Extract MCP

by diyaluo

Digital PDF invoices/bank statements to CSV, JSON or Excel with automatic PII redaction.

local only

wcagc — accessibility scanning

by wcag-compliance

Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account.

45 installs/wk answering

Arkrel

by arkrel

Turn documents into verified, structured data: fields, tables, and automatic checks.

answering

Blinkpdf

by blinkpdf

Render Markdown and LLM output into accessible PDF/UA-1 PDFs. No headless Chromium.

answering

PDF/UA accessibility check (veraPDF) with measured auto-fix — questions

Answers built from our own checks of this server.

What can PDF/UA accessibility check (veraPDF) with measured auto-fix do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_pdf_accessibility, explain_pdfua_rule. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is PDF/UA accessibility check (veraPDF) with measured auto-fix working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 12 of 12 checks got a reply (100.0%), average response time 112 ms. The bar chart above shows every period we have measured.

How do I connect PDF/UA accessibility check (veraPDF) with measured auto-fix?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does PDF/UA accessibility check (veraPDF) with measured auto-fix need an API key?

No. PDF/UA accessibility check (veraPDF) with measured auto-fix completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is PDF/UA accessibility check (veraPDF) with measured auto-fix?

It answers our handshake in 112 ms on average, which is faster than 95% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.