md2pdf
Registry code: dce98cdd6c1948cc
md2pdf turns markdown into a clean A4 PDF. Free, no account, no API key. Documents are rendered in memory and never stored.
Format: standard markdown (GitHub flavour). Optional signature lines, one per signer on its own line:
- endpoint
- https://md2pdf.free/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 md2pdf live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is md2pdf free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does md2pdf have?
- 4 tools: render_pdf, send_for_signature, validate_markdown, get_markdown_spec.
- Is md2pdf 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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
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.
get_markdown_spec open 8h ago
The full markdown format md2pdf accepts: markdown features, signature lines, fill-in fields, styles and limits.
{ "type": "object", "properties": {} }arguments 4 linesrender_pdf unknown 8h ago
Render markdown as an A4 PDF. The PDF comes back inside this result as an embedded application/pdf resource (base64); nothing is stored and there is no download link. If you can run shell commands, save the file directly instead: curl -sS -X POST https://md2pdf.free/api/pdf -H "Content-Type: text/markdown" --data-binary @document.md -o document.pdf
{ "type": "object", "required": [ "markdown" ], "properties": { "style": { "enum": [ "classic", "modern", "formal" ], "type": "string", "description": "classic (default), modern or formal. Overrides any <!-- md2sign:style=... --> line." }, "markdown": { "type": "string", "description": "The full markdown document. Start with \"# Title\": it names the file." }, "letterhead": { "type": "string", "description": "Name in the formal style's letterhead band, e.g. a company name. Defaults to the document title." } } }arguments 25 linessend_for_signature unknown never probed
Get a document e-signed instead of printed. Nothing is sent to anyone: this hands the markdown to md2sign (same company) and returns a link your human opens to sign up or log in, where the document waits as a draft ready to send. The link works once and expires after 24 hours; md2sign keeps the document until then. Also returns how to connect md2sign's own MCP server so you can send it directly. Use when the document has signature lines and your human wants it signed.
{ "type": "object", "required": [ "markdown" ], "properties": { "markdown": { "type": "string", "description": "The full markdown document, with a [[signature: Name <email>]] line for each signer." } } }arguments 12 linesvalidate_markdown unknown 8h ago
Check markdown before making the PDF. Returns the title (which names the file), style, signature lines and signers found, whether a PDF can be made, and, separately, any problems md2sign would raise if the document were sent for e-signature, with line numbers.
{ "type": "object", "required": [ "markdown" ], "properties": { "markdown": { "type": "string", "description": "The full markdown document." } } }arguments 12 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 iddce98cdd6c1948cc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dce98cdd6c1948cc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dce98cdd6c1948cc?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.