Scrapingdog
NPM · @PIPEWORX/MCP-SCRAPINGDOG · 2 COMPONENTS
Scrapingdog MCP — wraps Scrapingdog (scrapingdog.com), a proxy-based web scraping API with…
Available components
Last scanned (12 hours ago)
Scores higher than 69% of npm servers
Category Web Scraping
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-scrapingdog). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 979 tokens (~326/item across 3 items; 3 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 Management23
- Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 →
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.
- 5 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +2
- Stability: unverified → 0.13 ▲ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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/@pipeworx/mcp-scrapingdog@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-scrapingdog |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-scrapingdog/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692339022 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d0193ab158522131af64e434477edec44a852b2e308a4a12c5b5f0b9a457877d32920ad9cefebf9983d758d145ceb7a3c0564e6bc588c73fe5a87bbc3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
scrapingdog_amazon_product ~275
Get Amazon product data by ASIN via Scrapingdog — title, price, rating, review count, availability, feature bullets, and images as parsed JSON. Pass an asin (e.g. "B0BFC7WQ6R") or a full Amazon product url. Example: scrapingdog_amazon_product({ asin: "B0BFC7WQ6R", domain: "com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BYOK Scrapingdog API key (free trial at scrapingdog.com) |
| asin | string | – | Amazon ASIN (product identifier), e.g. "B0BFC7WQ6R". Provide this or `url`. |
| country | string | – | ISO country code for marketplace targeting, e.g. "us". Default "us" (1 credit; other countries cost 5). |
| domain | string | – | Amazon marketplace TLD, e.g. "com", "co.uk", "de", "in". Default "com". |
| language | string | – | ISO 639-1 language code for product data, e.g. "en", "de". Optional. |
| url | string | – | Full Amazon product URL — the ASIN is extracted from it. Alternative to `asin`. |
No output schema declared.
No examples provided.
scrapingdog_google_search ~280
Google SERP API — run a Google search via Scrapingdog and get structured results: parsed organic results (title, link, snippet), related searches, and people-also-ask questions. Costs 5 credits per search. Example: scrapingdog_google_search({ query: "best running shoes 2026", country: "us", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BYOK Scrapingdog API key (free trial at scrapingdog.com) |
| country | string | – | Two-letter country code to localize results, e.g. "us", "gb", "fr". Default "us". |
| domain | string | – | Google domain to search, e.g. "google.co.uk", "google.co.in". Default "google.com". |
| language | string | – | Results language code, e.g. "en", "es", "fr". Default "en". |
| page | number | – | Result page number, 0-based: 0 = first page, 1 = second page. Default 0. |
| query | string | yes | The Google search query, e.g. "best running shoes 2026". Supports operators like site: and intitle:. |
| results | number | – | Number of results to return per page, e.g. 10. Optional. |
No output schema declared.
No examples provided.
scrapingdog_scrape ~370
Scrape any website through Scrapingdog's rotating proxies and return its content. Returns HTML by default, or clean markdown with format:"markdown" (ideal for feeding an LLM). Set dynamic:true to render JavaScript in a headless browser for SPAs and dynamic pages (costs 5 credits instead of 1), premium:true for hard-to-scrape sites (residential proxies, 10 credits), and country to geotarget the proxy. Example: scrapingdog_scrape({ url: "https://example.com", format: "markdown", dynamic: true, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | BYOK Scrapingdog API key (free trial at scrapingdog.com) |
| country | string | – | ISO 3166-1 alpha-2 country code to proxy from, e.g. "us", "gb", "de". Optional geotargeting. |
| dynamic | boolean | – | Render JavaScript in a headless browser before returning content (use for SPAs / dynamic pages). Costs 5 credits per request instead of 1 (25 with premium proxies). Default false. |
| format | string | – | Response format: "markdown" for LLM-friendly text, "links" for a link list, otherwise HTML (default). Options: html, markdown, links, summary. |
| premium | boolean | – | Use premium residential proxies for hard-to-scrape sites. Costs 10 credits (25 combined with dynamic:true). Default false. |
| url | string | yes | The full URL to scrape including protocol, e.g. "https://example.com/page" |
| wait | number | – | Milliseconds to wait for the page to load (0–35000). Use together with dynamic:true for slow pages. |
No output schema declared.
No examples provided.
How do I install the Scrapingdog MCP server?
Scrapingdog runs locally as an npm package, launched with npx -y @pipeworx/mcp-scrapingdog. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-scrapingdog
claude mcp add pipeworx-io-scrapingdog -- npx -y @pipeworx/mcp-scrapingdog
What is the Scrapingdog MCP server?
Scrapingdog is an MCP server listed in the public MCP registry as io.github.pipeworx-io/scrapingdog. Scrapingdog MCP, wraps Scrapingdog (scrapingdog.com), a proxy-based web scraping API with… This page covers its npm package (@pipeworx/mcp-scrapingdog).
Is the Scrapingdog MCP server safe to use?
Scrapingdog scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Scrapingdog MCP server expose?
Scrapingdog exposes 3 tools: scrapingdog_scrape, scrapingdog_google_search, scrapingdog_amazon_product. Their descriptions and schemas cost roughly 925 tokens of context every time the server is loaded.
Is the Scrapingdog MCP server still maintained?
Scrapingdog 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 Scrapingdog MCP server under?
Scrapingdog 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 Scrapingdog MCP server?
VerifyMCP ran 16 checks on Scrapingdog, 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.