Scrapezy vs Rendex: Rendering API for Images, PDFs & Content Extraction
Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-18. 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 |  Scrapezy |  Rendex: Rendering API for Images, PDFs & Content Extraction |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7a19e9b36500 Forks (GitHub): 7 Pulls (Docker Hub): 40 905 Stars (Docker Hub): 3 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.8.2 Downloads/month (npm): 268 Downloads/week (npm): 49 Forks (GitHub): 0 Stars (GitHub): 6 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 | Scrapezy | Rendex: Rendering API for Images, PDFs & Content Extraction |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 6 (worse) |
| Pulls (Docker Hub) (differs) | 40 905 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/scrapezy) | Remote server (mcp.rendex.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/scrapezy/mcp | github.com/copperline-labs/rendex-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 302 (42 h ago) |
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
Scrapezy
A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.
Rendex: Rendering API for Images, PDFs & Content Extraction
Render HTML, Markdown, or URLs to images, PDF, or branded artifacts; extract and watch pages.
How to run each
Scrapezy As a local MCP server: Docker image
claude mcp add --env "SCRAPEZY_API_KEY=<YOUR_SCRAPEZY_API_KEY>" --transport stdio scrapezy -- docker run -i --rm -e SCRAPEZY_API_KEY mcp/scrapezyRequires: SCRAPEZY_API_KEY (secret)
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
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rendex: Rendering API for Images, PDFs & Content Extraction has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Rendex: Rendering API for Images, PDFs & Content Extraction publish no list of tools, so we do not compare tools.
Settings each asks for
Only Scrapezy asks for
SCRAPEZY_API_KEY (secret)
Only Rendex: Rendering API for Images, PDFs & Content Extraction asks for
RENDEX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Scrapezy · What it can do: Rendex: Rendering API for Images, PDFs & Content Extraction · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.