io.github.DataLeadsPRO/screenshot vs io.github.webmox/screenshotrun-mcp
io.github.DataLeadsPRO/screenshot is an MCP server published by DataLeadsPRO. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.webmox/screenshotrun-mcp is an MCP server published by webmox. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.DataLeadsPRO/screenshot |  io.github.webmox/screenshotrun-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.DataLeadsPRO/screenshot | io.github.webmox/screenshotrun-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (data.dataleads.pro/mcp/screenshot) | On your machine (screenshotrun-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dataleadspro/screenshot | github.com/webmox/screenshotrun-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-22 |
| Endpoint at the last check (differs) | Responded less than an hour ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.DataLeadsPRO/screenshot
Pixel-perfect webpage screenshots rendered in a real browser, full-page or viewport, via one POST.
io.github.webmox/screenshotrun-mcp
Capture website screenshots in AI agents. Full-page, dark mode, mobile, OG images, base64.
How to run each
io.github.DataLeadsPRO/screenshot As a remote MCP server
claude mcp add --transport http screenshot https://data.dataleads.pro/mcp/screenshotio.github.webmox/screenshotrun-mcp As a local MCP server: npm package
claude mcp add --env "SCREENSHOTRUN_API_KEY=<YOUR_SCREENSHOTRUN_API_KEY>" --transport stdio screenshotrun-mcp -- npx -y screenshotrun-mcpRequires: SCREENSHOTRUN_API_KEY
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/screenshot has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.DataLeadsPRO/screenshot publish no settings it asks for, so we do not compare settings.
What it can do: io.github.DataLeadsPRO/screenshot · What it can do: io.github.webmox/screenshotrun-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.