# PDF Accessibility Audit (npm · pdf-a11y-audit)

Local-first PDF accessibility audits with cited findings and an offline HTML report.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `pdf-a11y-audit`: 71/100 (this document), [markdown](https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit.md), [page](https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit)

## Channel facts

- Registry: `npm`
- Package: `pdf-a11y-audit`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 33 of 110 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 441 tokens (~55/item across 8 items; 6 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the PDF Accessibility Audit MCP server?

PDF Accessibility Audit runs locally as an npm package, launched with npx -y pdf-a11y-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add veduis-pdf-a11y-audit -- npx -y pdf-a11y-audit
```

### Cursor

```json
{
  "mcpServers": {
    "veduis-pdf-a11y-audit": {
      "command": "npx",
      "args": [
        "-y",
        "pdf-a11y-audit"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "veduis-pdf-a11y-audit": {
      "command": "npx",
      "args": [
        "-y",
        "pdf-a11y-audit"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add veduis-pdf-a11y-audit -- npx -y pdf-a11y-audit
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "veduis-pdf-a11y-audit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pdf-a11y-audit"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add veduis-pdf-a11y-audit --command npx --arg -y --arg pdf-a11y-audit
```

### Hermes

```yaml
mcp_servers:
  veduis-pdf-a11y-audit:
    command: "npx"
    args: ["-y", "pdf-a11y-audit"]
```

### Netclaw

```json
{
  "McpServers": {
    "veduis-pdf-a11y-audit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pdf-a11y-audit"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add veduis-pdf-a11y-audit -t stdio -c npx -a -y pdf-a11y-audit
```

### Other

```json
{
  "mcpServers": {
    "veduis-pdf-a11y-audit": {
      "command": "npx",
      "args": [
        "-y",
        "pdf-a11y-audit"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 71)

First indexed and scored.

## MCP tools (6)

### `audit_pdf` (~120 tokens)

Audit a PDF

Audit one local PDF for accessibility structure, headings, tables, figures, forms, reading order, fonts, scans, metadata and navigation. Returns JSON, Markdown or a self-contained HTML report. No upload and no model call.

Input parameters:

- `format` (string): Output format (default markdown)
- `maxFindings` (integer): Cap findings per document (default 500)
- `output` (string): Write HTML or Markdown to this path; omit to return text or use the default HTML filename
- `path` (string, required): Path to a local PDF file

### `audit_batch` (~79 tokens)

Audit a folder of PDFs

Audit every PDF in one or more local files or directories and return a compact comparison table. Use JSON to get full reports.

Input parameters:

- `format` (string): Output format (default markdown)
- `maxFindings` (integer)
- `paths` (array, required): Files or directories to scan
- `recursive` (boolean): Walk subdirectories (default true)

### `explain_finding` (~54 tokens)

Explain a finding

Return the rule description, severity, standards mapping and remediation guidance for a rule ID such as pdfua.tagged or figures.missing-alt.

Input parameters:

- `ruleId` (string, required): Rule ID, for example figures.missing-alt

### `list_checks` (~48 tokens)

List checks

List the audit rule catalog, including manual checks. Filter by category, severity or automation status.

Input parameters:

- `automated` (boolean)
- `category` (string)
- `severity` (string)

### `compare_reports` (~58 tokens)

Compare two audit reports

Compare two pdf-a11y-audit JSON reports and list new, fixed and persisting findings plus the score change.

Input parameters:

- `after` (string, required): Path to the later JSON report
- `before` (string, required): Path to the earlier JSON report

### `render_report` (~48 tokens)

Render a JSON report as HTML

Turn an existing pdf-a11y-audit JSON report into the self-contained HTML report.

Input parameters:

- `output` (string): HTML output path
- `report` (string, required): Path to a JSON report

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71

## Common questions

### What is the PDF Accessibility Audit MCP server?

PDF Accessibility Audit is an MCP server listed in the public MCP registry as io.github.Veduis/pdf-a11y-audit. Local-first PDF accessibility audits with cited findings and an offline HTML report. This page covers its npm package (pdf-a11y-audit).

### Is the PDF Accessibility Audit MCP server safe to use?

PDF Accessibility Audit scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 PDF Accessibility Audit MCP server expose?

PDF Accessibility Audit exposes 6 tools: audit_pdf, audit_batch, explain_finding, list_checks, compare_reports, render_report. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.

### Is the PDF Accessibility Audit MCP server still maintained?

PDF Accessibility Audit 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.

### What licence is the PDF Accessibility Audit MCP server under?

PDF Accessibility Audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/pdf-a11y-audit
- Socket report: https://socket.dev/npm/package/pdf-a11y-audit
- Repository: https://github.com/Veduis/pdf-a11y-audit
- Website: https://remediatepdf.com/open/pdf-a11y-audit
- Changelog RSS feed: https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit.xml
- Changelog JSON feed: https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit.json
- HTML version of this page: https://verifymcp.io/servers/veduis-pdf-a11y-audit/pdf-a11y-audit