← Explore all mcp servers

WEB CAPTURE / ScreenshotOne

ScreenshotOne MCP Server

Render website screenshots, extract cleaned Markdown and inspect ScreenshotOne usage.

“Render website screenshots, extract cleaned Markdown and inspect ScreenshotOne usage.”

01 / THE REASONING

Why this made the selection.

  • Render website screenshots, extract cleaned Markdown and inspect ScreenshotOne usage.
  • The setup documentation makes this operating boundary explicit: Target pages are rendered by ScreenshotOne; the API account supplies quota and concurrency access.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • LICENSE
  • package.json
  • src/core.ts

Our findings

  • Target pages are rendered by ScreenshotOne; the API account supplies quota and concurrency access.
  • Screenshot and slice URLs are temporary. The adapter always requests JSON with API caching disabled; slices require full_page=true.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx --yes @screenshotone/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Run npx --yes @screenshotone/mcp with SCREENSHOTONE_API_KEY in the environment. Explicitly request full_page and metadata_content if the task needs those outputs.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • A compatible local process MCP client.
  • Target pages are rendered by ScreenshotOne; the API account supplies quota and concurrency access.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/screenshotone/mcp/blob/6e96803d10d3759e057d384a1929fc7eb8be8934/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://github.com/screenshotone/mcp/blob/6e96803d10d3759e057d384a1929fc7eb8be8934/LICENSE

    Supports: license

  3. Pinned package metadata ↗Checked

    https://github.com/screenshotone/mcp/blob/6e96803d10d3759e057d384a1929fc7eb8be8934/package.json

    Supports: install, language, review

  4. https://github.com/screenshotone/mcp/blob/6e96803d10d3759e057d384a1929fc7eb8be8934/src/core.ts

    Supports: review, install, access, limitations

Evidence & Ask