Skip to content

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

io.github.nyo-agentti/pdfua-checknyo-agenttistreamable-httpv1.0.0Scanned

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

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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

The PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server is published by the GitHub account nyo-agentti. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (check_pdf_accessibility); 1 tool can send data out of your system (check_pdf_accessibility).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • check_pdf_accessibilityValidate 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).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • explain_pdfua_ruleExplain a veraPDF PDF/UA-1 rule by id (clause-test, e.g.No findings

    Why it is in this group

    • The name "explain_pdfua_rule" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Nov 2, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pdfua-check__explain_pdfua_rule"
    ],
    "ask": [
      "mcp__pdfua-check__check_pdf_accessibility"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pdfua-check. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pdfua-check__check_pdf_accessibility untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nyo-agentti/pdfua-check/verify?hash=45d582b793039fb3176db340cc3f129584864a108849b5e399c380528a604477" | jq -e '.changed == false'

Pinned hash 45d582b79303, from Oct 25, 2026, 14:26 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nyo-agentti/pdfua-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nyo-agentti/pdfua-check
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nyo-agentti/pdfua-check.svg)](https://radar.anlyon.com/servers/io.github.nyo-agentti/pdfua-check)

Source: MCP Registry. Synced Oct 25, 2026, 14:25 UTC.

PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server have?

2 tools: 2 read. check_pdf_accessibility and explain_pdfua_rule.

Does the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_pdf_accessibility.

Has the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.