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.

com.mambabuilt/mcp-website-screenshot-capture

NPM · @MAMBALABSDEV/MCP-WEBSITE-SCREENSHOT-CAPTURE

Website screenshots from URLs as PNG or JPEG links, full page or window

70 Trust /100

Last scanned (23 hours ago)

Scores higher than 41% of npm servers

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 560 tokens (~560/item across 1 items; 1 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +16
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.0.2 → 1.0.3 functional
  • 18 Nov 26 53

    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 21 Nov 2026 · Analysed npm/@mambalabsdev/mcp-website-screenshot-capture@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 →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~560 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
capture_website_screenshots ~560

Open each URL in a Chromium browser and save a PNG or JPEG screenshot, full page or window only. Returns one row per URL with the image link, final URL, HTTP status, page title, and image size. Pages that refuse the browser come back as free blocked rows.

NameTypeReqDescription
block_trackersboolean–yes (default) skips analytics, ad, and session replay scripts and video or audio files, which draw nothing you need in the image and make pages slower. no loads everything, so ads appear.
delay_msnumber–Extra wait after the page loads and before the capture, 0 to 20000. Default 0.
formatstring–png (default) or jpeg. JPEG files are smaller.
full_pageboolean–yes captures the whole scrollable page, up to 16,000 pixels tall. no (default) captures the visible window only.
hide_selectorsarray–Elements to hide before the capture, for example a cookie banner or a chat widget: #cookie-banner, .chat-widget.
jpeg_qualitynumber–1 to 100, used for jpeg only. Default 80.
max_charge_usdstring–Optional. The run stops before a charge that would pass this amount. Summary rows are always returned.
proxy_modestring–auto (default): pages load through the Apify proxy pool. none: pages load straight from the Apify server. A reliability setting only; it does not change what you pay.
scroll_to_bottomboolean–yes scrolls down the page before the capture so images that load on scroll appear, then returns to the top. Default no.
timeout_secondsnumber–Longest wait for one page to load, 10 to 120. Default 60. A page still loading at this point is captured as it stands and marked partial.
urlsarray–Pages to capture, each starting with http:// or https://. A bare domain such as example.com gets https:// added. From Clay, put the column inside a one item list.
viewport_heightnumber–Browser window height, 240 to 2160. Default 800. With Full page on, the image is as tall as the page.
viewport_widthnumber–Browser window width, 320 to 3840. Default 1280.
wait_untilstring–When the page counts as loaded. load (default): the page and its images loaded. domcontentloaded: the HTML is parsed, faster. networkidle: no network traffic for 0.5 s, best for pages that load conte…

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-website-screenshot-capture server?

com.mambabuilt/mcp-website-screenshot-capture runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-website-screenshot-capture. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-website-screenshot-capture

# add to Claude Code
claude mcp add com-mambabuilt-mcp-website-screenshot-capture -- npx -y @mambalabsdev/mcp-website-screenshot-capture
Common questions

What is the com.mambabuilt/mcp-website-screenshot-capture server?

com.mambabuilt/mcp-website-screenshot-capture is listed in the public MCP registry as com.mambabuilt/mcp-website-screenshot-capture. Website screenshots from URLs as PNG or JPEG links, full page or window. This page covers its npm package (@mambalabsdev/mcp-website-screenshot-capture).

Is the com.mambabuilt/mcp-website-screenshot-capture server safe to use?

com.mambabuilt/mcp-website-screenshot-capture scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 com.mambabuilt/mcp-website-screenshot-capture server expose?

com.mambabuilt/mcp-website-screenshot-capture exposes 1 tool: capture_website_screenshots. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-website-screenshot-capture server still maintained?

com.mambabuilt/mcp-website-screenshot-capture is still listed as active in the MCP registry. We last reached this channel on 21 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 com.mambabuilt/mcp-website-screenshot-capture server under?

com.mambabuilt/mcp-website-screenshot-capture declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mambabuilt/mcp-website-screenshot-capture server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-website-screenshot-capture, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.