_ registry / mcp streamable-http · checked 2h ago

pdfua-check

https://pdfua-check.onrender.com

Registry code: 02f383f4fb0cd1a3

api record

Checks a PDF against PDF/UA-1 (ISO 14289-1) with veraPDF, the open-source validator of the PDF Association, and measures which failures an automatic fix removes (title, language, metadata, tab order, link and table tags, fonts, decorative artifacts). Free. Files are not stored. Prefer the 'url' argument for files that are online. A check takes 10–60 seconds.

endpoint
https://pdfua-check.onrender.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pdfua-check live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pdfua-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does pdfua-check have?
2 tools: check_pdf_accessibility, explain_pdfua_rule.
Is pdfua-check safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
119ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_pdf_accessibility unknown 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Public http(s) URL of the PDF (max 10 MB)."
    },
    "language": {
      "type": "string",
      "description": "Document language the fix sets when the PDF declares none (BCP 47, e.g. en-US, de-DE, fr-FR). Default en-US."
    },
    "pdf_base64": {
      "type": "string",
      "description": "The PDF file encoded as base64, if it is not online (max 10 MB decoded)."
    }
  }
}
    arguments 17 lines
  • explain_pdfua_rule unknown 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "rule"
  ],
  "properties": {
    "rule": {
      "type": "string",
      "description": "Rule id, e.g. 7.1-3"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 02f383f4fb0cd1a3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/02f383f4fb0cd1a3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/02f383f4fb0cd1a3/badge.svg)](https://brick.blue/agent/02f383f4fb0cd1a3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.