Ext Ops Panel
Open dashboard
Comparison

HasData Web Scraping vs Site-Shot

HasData Web Scraping is an MCP server published by hasdata.com. Marketplaces we read that list it: 1 (Official MCP Registry). Site-Shot is an MCP server published by site-shot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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

Where each is published
MarketplaceHasData Web ScrapingSite-Shot
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (npm): 199
Downloads/week (npm): 61
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 1.2.3
Downloads/month (npm): 470
Downloads/week (npm): 340
Forks (GitHub): 0
Stars (GitHub): 3
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

HasData Web Scraping vs Site-Shot
FactHasData Web ScrapingSite-Shot
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)3 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-11-12
Where it runs (differs)Remote server (mcp.hasdata.com/mcp)On your machine (site-shot-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/hasdata/web-scraping-mcpgithub.com/site-shot/site-shot-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 23 h ago, requires authenticationno 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

HasData Web Scraping

In its own words, on Official MCP Registry:

Fetch any public web page through managed proxies, with optional JS rendering and extraction rules.

Site-Shot

In its own words, on Official MCP Registry:

Website screenshot API for AI agents: full-page, ad & cookie-banner removal, paid-plan geo

How to run each

HasData Web Scraping

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: HASDATA_API_KEY (secret), x-api-key header

Site-Shot As a local MCP server: npm package

Claude Code
claude mcp add --env "SITESHOT_API_KEY=<YOUR_SITESHOT_API_KEY>" --transport stdio site-shot-mcp -- npx -y site-shot-mcp

Requires: SITESHOT_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only HasData Web Scraping 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

Only HasData Web Scraping asks for

  • HASDATA_API_KEY (secret)

Only Site-Shot asks for

  • SITESHOT_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: HasData Web Scraping · What it can do: Site-Shot · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built