Rendex: Rendering API for Images, PDFs & Content Extraction

io.github.copperline-labs/rendex-mcp · v1.8.2 · productivity

Rendex: Rendering API for Images, PDFs & Content Extraction is healthy: it completed an MCP handshake in 1872 ms and exposes 13 tools.

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

Endpoint: https://mcp.rendex.dev/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count13
Latency1872 ms
Last checked (UTC)2026-10-15T03:20:34.727Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T03:20:34.727ZHealthy1872

Tools (13)

rendex_screenshotUse this when the user asks to screenshot, capture, or take a picture of a webpage/URL, or to render raw HTML or Markdown to an image or PDF. Do NOT use to get a reusable hosted image URL (use rendex_render_link) or to make a branded multi-format document (use render_artifact). Captures a screenshot
rendex_extractUse this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Do NOT use for a visual screenshot (use rendex_screenshot). Extracts clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs the same Chromium render pass as a screenshot, s
rendex_render_linkUse this when the user wants a reusable, HOSTED image URL — an og:image or a link to embed in an <img> tag — rather than the image bytes. Do NOT use for a one-off inline screenshot (use rendex_screenshot). Renders a URL, raw HTML, or Markdown and gives back a signed, hosted, edge-cached image URL in
render_artifactUse this when the user asks to make or create a branded report, invoice, summary, release notes, or document — or to 'turn this Markdown/HTML into a PDF and PNG' (optionally with a logo or accent color). Do NOT use to screenshot an existing URL (use rendex_screenshot). Turns Markdown or HTML into a
rendex_accountCheck the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (and when it resets), the per-minute rate limit, and a one-tap link to upgrade to a higher tier. Use this whenever the user asks about their usage, remaining quota, current plan, or how to get
watch_createUse this when the user asks to monitor, watch, or track a webpage for changes, or to be alerted/notified when a page changes. Do NOT use for a one-time capture (use rendex_screenshot). Creates a Rendex Watch — monitors a URL on a schedule and notifies when it changes (real-Chrome visual diff with a
watch_testDry-run a watch config BEFORE creating it — render the proposed config once and report what was captured + whether the page is reachable (and the text a text-watch would compare). Creates no watch, no baseline, no diff. Use this to validate a selector/scope/identity first. Returns JSON.
watch_listList your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }.
watch_getFetch one watch by ID, including its current baseline image URL and status. Returns JSON.
watch_runRun an immediate check now (charges 1 credit). Returns the queued run; poll watch_runs for the result or receive a watch.changed webhook.
watch_runsRead a watch's run history (newest first), paged. Each run includes changed, diffScore, and signed before/after/overlay image URLs. Returns { items, nextCursor }.
watch_deleteDelete a watch and its run history. Irreversible.
watch_updateUpdate a watch in place — pause/resume (paused), re-point (url), change schedule/diff/notify settings, or turn a channel off (webhookUrl/notifyEmail = null). Only the fields you send change; renderParams is deep-merged over the existing config. A scope change (url/selector/fullPage/size/device) re-b