Screenshot & PDF Capture API

io.github.Br0ski777Published by GitHub account Br0ski777v1.2.0Updated Oct 28, 2026

Capture screenshots (PNG/JPEG/WebP) and generate PDFs from any URL. x402 payments.

The publisher's own server: screenshot.com.ar

VerifiedSSEWeb executableBrowser AutomationMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that renders any URL in Chromium to return a screenshot image or a paginated PDF, paid per call in USDC.

What you can do
  • Capture a screenshot of any URL as PNG, JPEG or WebP, with viewport width, height and full-page options
  • Convert a live web page into a printable PDF with a chosen paper format
  • Both actions are available as GET and POST variants with the same parameters
  • Returns binary image or PDF content rather than extracted text
When to use it
Useful for visual QA and responsive-design checks, page thumbnails, archiving web pages as images or PDFs, and saving receipts, invoices or articles from a URL. Not intended for text extraction or for building PDFs from your own HTML or Markdown.
Requirements
A remote MCP endpoint; nothing to install locally. No API key or signup, but each call is paid per use through the x402 protocol in USDC on Base L2, so an x402-capable client with a funded wallet is needed. Network access to the provider's endpoint.
Before you install
Every call costs money ($0.015 per screenshot, $0.02 per PDF) and is settled in USDC on Base through a crypto wallet, so spending is not capped by the server. The URL you submit is fetched by a third-party service, which sees the requested pages. Payment handling is delegated to x402 clients and facilitators.

Installation

In SourceWeft

  1. Open Screenshot & PDF Capture API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fscreenshot-pdf/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "screenshot-pdf-capture-api": {
      "type": "sse",
      "url": "https://screenshot-pdf.api.klymax402.com/mcp"
    }
  }
}

README

Screenshot & PDF Capture API

[MCP Server] [x402] [License: MIT]

Capture full-page screenshots and PDFs from any URL. Chromium rendering, custom viewport, PNG/JPEG/WebP output. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "screenshot-pdf": {      "url": "https://screenshot-pdf.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://screenshot-pdf.api.klymax402.com/api/screenshot?url=https://example.com"# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
capture_screenshotGET/api/screenshot$0.015Capture a screenshot of any URL
capture_screenshotPOST/api/screenshot$0.015Capture a screenshot of any URL (POST variant)
webpage_to_pdfGET/api/pdf$0.02Generate a PDF from any URL
webpage_to_pdfPOST/api/pdf$0.02Generate a PDF from any URL (POST variant)

capture_screenshot

Use this when you need a visual capture of a web page. Renders in a real Chromium browser and returns an image.

Parameters

NameTypeRequiredDescription
urlstringyesURL to screenshot (e.g. https://example.com)
widthnumbernoViewport width in px (default: 1280)
heightnumbernoViewport height in px (default: 720)
fullPagebooleannoCapture full scrollable page (default: false)
formatstringnoImage format (default: png)

Example response:

json
binary image file with Content-Type image/png, typical size 200-800KB for a full page.

When to use: visual QA testing, generating page thumbnails, archiving web pages, or verifying responsive design. Essential for automated screenshot pipelines and visual regression testing.

Not for: text extraction (use web_scrape_to_markdown), PDF from data (use document_generate_pdf), PDF from URL (use webpage_to_pdf).

capture_screenshot

Use this when you need a visual capture of a web page. Renders in a real Chromium browser and returns an image. POST variant of capture_screenshot -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
urlstringyesURL to screenshot (e.g. https://example.com)
widthnumbernoViewport width in px (default: 1280)
heightnumbernoViewport height in px (default: 720)
fullPagebooleannoCapture full scrollable page (default: false)
formatstringnoImage format (default: png)

Example response:

json
binary image file with Content-Type image/png, typical size 200-800KB for a full page.

When to use: visual QA testing, generating page thumbnails, archiving web pages, or verifying responsive design. Essential for automated screenshot pipelines and visual regression testing.

Not for: text extraction (use web_scrape_to_markdown), PDF from data (use document_generate_pdf), PDF from URL (use webpage_to_pdf).

webpage_to_pdf

Use this when you need to convert a live web page to a printable PDF document. Renders in a real Chromium browser and returns binary PDF.

Parameters

NameTypeRequiredDescription
urlstringyesURL to convert to PDF (e.g. https://example.com)
formatstringnoPaper format (default: A4)

Example response:

json
binary PDF file with Content-Type application/pdf, properly paginated with headers/footers.

When to use: archiving web pages as PDF, generating printable articles, saving receipts or invoices from URLs, or creating offline documentation snapshots.

Not for: custom documents from HTML/Markdown (use document_generate_pdf), screenshots (use capture_screenshot), web scraping text (use web_scrape_to_markdown).

webpage_to_pdf

Use this when you need to convert a live web page to a printable PDF document. Renders in a real Chromium browser and returns binary PDF. POST variant of webpage_to_pdf -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
urlstringyesURL to convert to PDF (e.g. https://example.com)
formatstringnoPaper format (default: A4)

Example response:

json
binary PDF file with Content-Type application/pdf, properly paginated with headers/footers.

When to use: archiving web pages as PDF, generating printable articles, saving receipts or invoices from URLs, or creating offline documentation snapshots.

Not for: custom documents from HTML/Markdown (use document_generate_pdf), screenshots (use capture_screenshot), web scraping text (use web_scrape_to_markdown).

Example agent prompts

  • "A visual capture of a web page"
  • "A visual capture of a web page"
  • "Convert a live web page to a printable PDF document"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit d079418

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Screenshot integrations