# Scrapingbee (npm · @pipeworx/mcp-scrapingbee)

ScrapingBee MCP — wraps the ScrapingBee headless-scraping API (scrapingbee.com)

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 85/100, [markdown](https://verifymcp.io/servers/pipeworx-io-scrapingbee/scrapingbee-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-scrapingbee/scrapingbee-mcp)
- npm · `@pipeworx/mcp-scrapingbee`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee.md), [page](https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-scrapingbee`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-scrapingbee).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 769 tokens (~256/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Scrapingbee MCP server?

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

### Claude

```bash
claude mcp add pipeworx-io-scrapingbee -- npx -y @pipeworx/mcp-scrapingbee
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-scrapingbee": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-scrapingbee"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-scrapingbee": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-scrapingbee"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-scrapingbee -- npx -y @pipeworx/mcp-scrapingbee
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-scrapingbee": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-scrapingbee"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-scrapingbee --command npx --arg -y --arg @pipeworx/mcp-scrapingbee
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-scrapingbee:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-scrapingbee"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-scrapingbee": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-scrapingbee"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-scrapingbee -t stdio -c npx -a -y @pipeworx/mcp-scrapingbee
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-scrapingbee": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-scrapingbee"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-04 (score 78, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `scrapingbee_scrape` (~282 tokens)

Fetch and render any web page through ScrapingBee (headless browser + proxy rotation), returning the resulting HTML. Handles JS-heavy sites, geolocation, and ad-blocking. Example: scrapingbee_scrape({ url: "https://example.com", render_js: true, _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Your ScrapingBee API key (get one free at scrapingbee.com).
- `block_ads` (boolean): Block advertisements while rendering (default false).
- `country_code` (string): ISO 3166-1 alpha-2 country code for proxy geolocation, e.g. "us", "de", "br".
- `premium_proxy` (boolean): Route through residential premium proxies (higher credit cost). Use for hard-to-scrape or geo-blocked sites.
- `render_js` (boolean): Execute JavaScript via a headless browser (default true). Set false for faster/cheaper static fetches.
- `stealth_proxy` (boolean): Use the stealth proxy pool for the most heavily protected sites (highest credit cost).
- `url` (string, required): Full target URL including protocol, e.g. "https://example.com/page"
- `wait_for` (string): CSS/XPath selector to wait for before capturing the page, e.g. "#content" or ".results".

### `scrapingbee_ai_extract` (~201 tokens)

Extract structured data from a web page using ScrapingBee's AI. Pass a natural-language question or field description via `ai_query` and get back structured JSON. Example: scrapingbee_ai_extract({ url: "https://example.com/product", ai_query: "product name and price", _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Your ScrapingBee API key.
- `ai_query` (string, required): Natural-language description of the data to extract, e.g. "the article title, author, and publish date".
- `country_code` (string): ISO 3166-1 alpha-2 country code for proxy geolocation, e.g. "us".
- `premium_proxy` (boolean): Route through residential premium proxies (higher credit cost).
- `render_js` (boolean): Execute JavaScript via a headless browser before extraction (default true).
- `url` (string, required): Full target URL including protocol.

### `scrapingbee_google` (~232 tokens)

Scrape Google Search results via ScrapingBee's Google SERP API. Returns structured JSON with organic results, AI overviews, local results, related searches, and more. Example: scrapingbee_google({ search: "best coffee grinder", country_code: "us", _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Your ScrapingBee API key.
- `country_code` (string): ISO 3166-1 alpha-2 country code to localize results (default "us"), e.g. "gb", "de".
- `language` (string): Results language code (default "en"), e.g. "fr", "es".
- `nb_results` (number): Number of organic results to request (default 100). Lower values are faster.
- `page` (number): Result page number (default 1).
- `search` (string, required): The Google search query, e.g. "best coffee grinder".
- `search_type` (string): Type of search: "classic" (default), "news", "maps", "images", or "shopping".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Scrapingbee MCP server?

Scrapingbee is an MCP server listed in the public MCP registry as io.github.pipeworx-io/scrapingbee. ScrapingBee MCP, wraps the ScrapingBee headless-scraping API (scrapingbee.com). This page covers its npm package (@pipeworx/mcp-scrapingbee).

### Is the Scrapingbee MCP server safe to use?

Scrapingbee 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 Scrapingbee MCP server expose?

Scrapingbee exposes 3 tools: scrapingbee_scrape, scrapingbee_ai_extract, scrapingbee_google. Their descriptions and schemas cost roughly 715 tokens of context every time the server is loaded.

### Is the Scrapingbee MCP server still maintained?

Scrapingbee 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 Scrapingbee MCP server under?

Scrapingbee 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 Scrapingbee MCP server?

VerifyMCP ran 16 checks on Scrapingbee, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-scrapingbee
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-scrapingbee
- Repository: https://github.com/pipeworx-io/mcp-scrapingbee
- Website: https://pipeworx.io/packs/scrapingbee
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-scrapingbee/pipeworx-mcp-scrapingbee