Rendex: Rendering API for Images, PDFs & Content Extraction vs url-to-pdf
Rendex: Rendering API for Images, PDFs & Content Extraction is an MCP server published by copperline-labs. Marketplaces we read that list it: 1 (Official MCP Registry). url-to-pdf is an MCP server published by strayly. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Rendex: Rendering API for Images, PDFs & Content Extraction |  url-to-pdf |
|---|---|---|
| Official MCP Registry | Listed Version: 1.8.2 Downloads/month (npm): 201 Downloads/week (npm): 21 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Rendex: Rendering API for Images, PDFs & Content Extraction | url-to-pdf |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.rendex.dev/mcp) | Remote server (url-pdf.hammbox.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/copperline-labs/rendex-mcp | github.com/strayly/url-to-pdf |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 302 | Status out of date: last check 42 h ago returned HTTP 200 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Rendex: Rendering API for Images, PDFs & Content Extraction
Render HTML, Markdown, or URLs to images, PDF, or branded artifacts; extract and watch pages.
url-to-pdf
Convert public web pages to PDF, images, Markdown, or JSON using one API key.
How to run each
Rendex: Rendering API for Images, PDFs & Content Extraction As a remote MCP server
claude mcp add --transport http rendex-mcp https://mcp.rendex.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: RENDEX_API_KEY (secret), Authorization header
url-to-pdf As a remote MCP server
claude mcp add --transport http url-to-pdf https://url-pdf.hammbox.com/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of url-to-pdf responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of url-to-pdf publish no settings it asks for, so we do not compare settings.
What it can do: Rendex: Rendering API for Images, PDFs & Content Extraction · What it can do: url-to-pdf · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.