Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.webmox/screenshotrun-mcp

NPM · SCREENSHOTRUN-MCP

Capture website screenshots in AI agents. Full-page, dark mode, mobile, OG images, base64.

Available components

0 this week 64 Trust /100

Last scanned (2 hours ago)

Scores higher than 32% of npm servers

Category Browser Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 355 tokens (~177/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 23 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 22 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/screenshotrun-mcp@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~355 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_usage ~29

Check your ScreenshotRun API usage for the current billing period. Shows screenshots used, remaining, and limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

take_screenshot ~326

Capture a screenshot of any webpage. Returns the image as base64-encoded data. Supports custom viewport sizes, device emulation, dark mode, full-page capture, ad blocking, and more.

NameTypeReqDescription
block_adsboolean–Block advertisements during capture
block_cookiesboolean–Block cookie consent dialogs
click_selectorstring–CSS selector of an element to click before capture
cssstring–Custom CSS to inject into the page
dark_modeboolean–Enable dark mode (prefers-color-scheme: dark)
delayinteger–Delay in seconds after page load before capturing
devicestring–Device preset (affects viewport and user agent)
formatstring–Output image format
full_pageboolean–Capture the entire scrollable page
heightinteger–Viewport height in pixels
hide_selectorsarray–CSS selectors of elements to hide before capture
jsstring–Custom JavaScript to execute before capture
qualityinteger–Image quality for JPEG/WebP (1-100)
retinaboolean–Capture at 2x resolution (retina)
scroll_tostring–CSS selector of an element to scroll into view before capture
selectorstring–CSS selector to capture a specific element instead of the full viewport
urlstringyesURL of the page to screenshot (must start with http:// or https://)
widthinteger–Viewport width in pixels

No output schema declared.

No examples provided.

Install

How do I install the io.github.webmox/screenshotrun-mcp server?

io.github.webmox/screenshotrun-mcp runs locally as an npm package, launched with npx -y screenshotrun-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · screenshotrun-mcp

# add to Claude Code
claude mcp add webmox-screenshotrun-mcp -- npx -y screenshotrun-mcp
Common questions

What is the io.github.webmox/screenshotrun-mcp server?

io.github.webmox/screenshotrun-mcp is listed in the public MCP registry as io.github.webmox/screenshotrun-mcp. Capture website screenshots in AI agents. Full-page, dark mode, mobile, OG images, base64. This page covers its npm package (screenshotrun-mcp).

Is the io.github.webmox/screenshotrun-mcp server safe to use?

io.github.webmox/screenshotrun-mcp scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.webmox/screenshotrun-mcp server expose?

io.github.webmox/screenshotrun-mcp exposes 2 tools: take_screenshot, check_usage. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.

Is the io.github.webmox/screenshotrun-mcp server still maintained?

io.github.webmox/screenshotrun-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.webmox/screenshotrun-mcp server under?

io.github.webmox/screenshotrun-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.