Ext Ops Panel
Open dashboard
Comparison

Local Web Capture vs HasData Web Scraping

Local Web Capture is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). HasData Web Scraping is an MCP server published by hasdata.com. 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

Where each is published
MarketplaceLocal Web CaptureHasData Web Scraping
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 306
Downloads/week (npm): 25
Forks (GitHub): 1
Stars (GitHub): 10
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

Local Web Capture vs HasData Web Scraping
FactLocal Web CaptureHasData Web Scraping
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.hasdata.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/claude-local-web-capture-plugingithub.com/hasdata/web-scraping-mcp
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

Local Web Capture

In its own words, on Community GitHub marketplaces:

Capture geo-restricted web content (articles, prices) via the user's own localhost so requests exit via the user's IP. Headless-first escalation ladder (Scrapling static -> stealth -> Playwright -> real Chrome via bb-browser). Project-local save (in-repo captures/) with global fallback. Batch capture with human + agent summaries, Typst PDF compilation, and arbitrary-language capture+translate (default Hebrew -> English).

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.

How to run each

Local Web Capture As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install local-web-capture@danielrosehill

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

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

The marketplaces of Local Web Capture publish no settings it asks for, so we do not compare settings.

What it can do: Local Web Capture · What it can do: HasData Web Scraping · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built