Mmcp.market

Head to head

Rendex: Rendering API for Images, PDFs & Content Extraction vs Plumb

Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.

Rendex: Rendering API for Images, PDFs & Content Extractionio.github.copperline-labs/rendex-mcp
A
No reviews yet

Render HTML, Markdown, or URLs to images, PDF, or branded artifacts; extract and watch pages.

Full listing
Plumbio.github.tathagat22/plumb-mcp
C
No reviews yet

Two-way Figma MCP: extract + verify design-to-code, or generate on-brand Figma pages from a prompt.

Full listing

The short version

Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours Rendex: Rendering API for Images, PDFs & Content Extraction (87/100 against 65). Rendex: Rendering API for Images, PDFs & Content Extraction is hosted and callable through the gateway; Plumb runs on your own machine.

 Rendex: Rendering API for Images, PDFs & Content ExtractionPlumb
User ratingNo reviews yetNo reviews yet
Safety gradeA87/100C65/100
AdoptionGrowingGrowing
GitHub stars783
Downloads / week47–
Runs whereHosted (remote)Your machine (local)
Gateway-readyYesNo
Tools1323
Write actions4—
Price per callFreeFree
LicenceMITMIT
Last release2026-08-142026-09-17
CategoryScraping and browsingScraping and browsing

Other comparisons

Rendex: Rendering API for Images, PDFs & Content Extraction vs Nutrient DWS MCP ServerRendex: Rendering API for Images, PDFs & Content Extraction vs TalonicRendex: Rendering API for Images, PDFs & Content Extraction vs FortressRendex: Rendering API for Images, PDFs & Content Extraction vs Design System ExtractorRendex: Rendering API for Images, PDFs & Content Extraction vs Oya BrowserAll Scraping and browsing servers