io.github.nyo-agentti/pdfua-check
PDF/UA accessibility check (veraPDF) with measured auto-fix
Is the PDF/UA accessibility check (veraPDF) with measured auto-fix MCP server down? Yes. It has given no valid answer since 2026-10-28: not found (HTTP 404).
Check PDFs against PDF/UA-1 with veraPDF; see which failures an automatic fix removes; explain rules
not found down since 2026-10-28 · probed 2026-11-15 · unchanged since 2026-10-30 · HTTP 404
Streamable HTTP error: Error POSTing to endpoint: Not Found
- Endpoint
- https://pdfua-check.onrender.com/mcp (streamable-http)
- Host
- pdfua-check.onrender.com
- Website
- https://nyo-agentti.github.io/pdf.html#mcp
- Registry
- active, updated 2026-10-25 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention check.
- Business Contact Finder agency.ottobot/business-contact-finder · alive
- groTAX by Grovisor ae.grovisor/grotax · alive
- Agentic Fabrication Network (AFN) ai.agenticfabricationnetwork/ufp · alive
- Plumbline - Contractor License Checks ai.agentlookups/plumbline · alive
- ai.agentlookups/overassessed · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- One-Page Readiness Check — 10 Signals, Arabic or English ai.advisorsai/store-readiness · alive
- ai.aivonic/mcp · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-28 10:06 | not found | ||||
| 2026-10-25 21:20 | alive | 374 ms | 2 | 558 | 360 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-28, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.