pdfmd
Registry code: f195f8a0194d9237
PDFMD's Markdown connector converts public PDF links into Markdown with page and table metadata. This connector does not OCR scanned pages or read local files; English OCR is a separate REST endpoint at /api/v1/ocr. Replies contain at most 20,000 Markdown characters and explicitly mark excerpts. The entire conversion counts toward the existing API page allowance even when the reply is an excerpt. No result is saved or given a download link.
- endpoint
- https://pdfmd.dev/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 pdfmd live?
- Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
- Is pdfmd free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pdfmd have?
- 1 tool: convert_pdf_url.
- Is pdfmd 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.
90 days 99.7%· all time 99.7%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- documents & files conversion
- used for
- convert a pdf link to markdown
- extract tables from a public pdf
- takes → gives
- documents → text
- tools
- 1 reads
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.
through this hub
successful
what callers paid
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
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.
convert_pdf_url reads unknown 19h ago
Use when someone asks to read, quote or summarize a PDF that sits at a public web link, or wants it as Markdown or HTML for research or a coding project. Returns extracted text, page and table counts, and whether scanned pages were found. It does not OCR scanned pages and it cannot open private links or local files. The reply holds at most 20,000 Markdown characters and marks a longer result as an excerpt; the whole PDF counts toward the API page allowance.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "maxLength": 2048 }, "format": { "enum": [ "markdown", "html", "both" ], "type": "string", "description": "markdown (default), html or both. html is a fragment you can embed." } } }arguments 23 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf195f8a0194d9237.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f195f8a0194d9237/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f195f8a0194d9237?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.