MCP.Market

Screenshotline MCP server

online · 100% uptime
by MAMubeenKhan·io.github.MAMubeenKhan/screenshotline·v0.1.0
No reviews yet

Screenshot any web page, or read it as clean Markdown, with consent banners, ads and popups removed.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Screenshotline yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Screenshotline tools (2)

write = sends, deletes, buys or posts
  • read_pageFree

    Render a web page and return its content as clean Markdown. The page is fully rendered first - JavaScript executed, consent banners dismissed, lazy images loaded - so this works on sites that return nothing useful to a plain HTTP fetch. Prefer this over screenshot when you need to read or reason about the text.

  • screenshotFree

    Capture a screenshot of a web page and return it as an image. Handles consent banners, ads, lazy-loaded images and late-rendering SPAs. Use this when the layout, styling or visual appearance is what matters; use read_page when you only need the text.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 988ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Screenshotline compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,243 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,164 ms
faster than 10% of 30,027 servers

What its tools let an agent do: 2 read

Install Screenshotline in Claude Code, Cursor or VS Code

claude mcp add --transport http screenshotline https://api.screenshotline.com/mcp
Add to Cursor

What the publisher says

From the Screenshotline repository's README, as published. We do not edit it. Read it on GitHub

Screenshotline

A screenshot API that survives production. URL in, image out.

curl "https://api.screenshotline.com/take?url=https://example.com&block_cookie_banners=true" -o shot.png

Above: france24.com, captured by this API. The consent wall is gone, the empty ad slot has been collapsed rather than left as a grey hole pushing content below the fold, and the lazy-loaded hero image has actually loaded. Most screenshot failures are not crashes — they are a 200 with the wrong picture.

Two ways to use it

Hosted — screenshotline.com. Free tier, 500 renders a month, no card. Warm browser pool, cache, and someone else's pager.

Self-hosted — docker compose up -d. The same renderer, nothing held back. See SELF-HOSTING.md, which is honest about what running headless Chrome at scale actually costs you.

Why this exists

Taking one screenshot with Puppeteer is twenty lines. Taking ten thousand is a different job, and it is the job people pay to avoid:

Plus the one that is not a performance problem: an endpoint that fetches arbitrary URLs is an SSRF engine by default. Private and reserved ranges are refused, and every redirect hop is re-checked, not just the submitted URL.

Quick start

Docker (recommended)

docker compose up -d
curl "http://localhost:3000/take?url=https://example.com" -o out.png

Node 22+

npm install
npm start          # http://localhost:3000
npm run smoke      # 30 checks against the real render path

Open for a demo with no signup.

API

One endpoint. GET or POST /take, returning binary image data — no JSON envelope, no second round trip. That is deliberate: the URL has to work directly inside an .

GET /take
  ?url=https%3A%2F%2Fexample.com
  &format=webp
  &full_page=true
  &block_cookie_banners=true
  &viewport_width=1440
  &cache=true&cache_ttl=86400

Parameters

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Screenshotline: common questions

Is Screenshotline MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Screenshotline safety report
How do I install Screenshotline?
It runs remotely at api.screenshotline.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Screenshotline need an API key?
Yes. The registry entry asks for X-Access-Key.
Is Screenshotline maintained?
The last commit was 49 days ago (2026-09-17). The latest release is v0.1.0.
Is Screenshotline up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Screenshotline?
Servers from other publishers that do the same job: Front-End Checklist MCP server and Reticle MCP server.
How does Screenshotline compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Screenshotline

Same job from other publishers: the closest match first, then the best rated.

  • Front-End Checklist
    Review frontend code and live pages against 386 quality-gated web development rules.
    A
  • Reticle
    Verify a running web app from the inside over MCP: look, act, observe, assert. No screenshots.
    B