# Crawlbase (npm · @pipeworx/mcp-crawlbase)

Crawlbase MCP — wraps the Crawlbase Crawling API (crawlbase.com, formerly ProxyCrawl). One…

- 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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-crawlbase/crawlbase-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-crawlbase/crawlbase-mcp)
- npm · `@pipeworx/mcp-crawlbase`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-crawlbase/pipeworx-mcp-crawlbase.md), [page](https://verifymcp.io/servers/pipeworx-io-crawlbase/pipeworx-mcp-crawlbase)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-crawlbase`
- 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-crawlbase).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1109 tokens (~369/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 Crawlbase MCP server?

Crawlbase runs locally as an npm package, launched with npx -y @pipeworx/mcp-crawlbase. 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-crawlbase -- npx -y @pipeworx/mcp-crawlbase
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 53, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (3)

### `crawlbase_scrape` (~433 tokens)

Scrape any website through Crawlbase rotating residential proxies with server-side anti-bot bypass (Cloudflare, DataDome, hCaptcha solved for you). Returns the page as HTML (default), clean markdown (format:"md" — great for LLM context), or a JSON envelope with metadata (format:"json"). JavaScript-heavy pages (SPAs) render when you pass your Crawlbase JavaScript token as _apiKey; the Normal token does fast static fetches. Example: crawlbase_scrape({ url: "https://example.com", format: "md", _apiKey: "your-crawlbase-token" })

Input parameters:

- `_apiKey` (string, required): Your Crawlbase token — Normal token for static pages, JavaScript token for rendered pages. Free tier (10,000 requests) at https://crawlbase.com
- `ajax_wait` (boolean): Wait until the network is idle before capturing (JavaScript token required). Best for SPAs that fetch data after mount.
- `country` (string): Two-letter ISO country code to route the crawl through, e.g. "US", "GB", "DE", "JP". Default: automatic geo selection.
- `device` (string): Device profile to emulate: "desktop" (default), "tablet", or "mobile".
- `format` (string): Response shape: "html" (default, raw page), "md" (GitHub-flavored markdown, LLM-friendly), or "json" (page + metadata in one JSON envelope).
- `javascript` (boolean): Set true when the page needs JavaScript rendering (SPAs, lazy-loaded feeds). Crawlbase selects rendering by TOKEN TYPE, so when this is true you must pass your Crawlbase JavaScript token as _apiKey (…
- `page_wait` (number): Milliseconds to wait after page load before capturing (JavaScript token required). Useful for content that animates in.
- `url` (string, required): The absolute URL to scrape including scheme, e.g. "https://example.com/page"

### `crawlbase_screenshot` (~306 tokens)

Capture a screenshot of a rendered web page via Crawlbase (headless browser + rotating proxies, anti-bot bypass). Returns a stored screenshot_url (JPEG, link expires after about one hour) plus crawl metadata. Requires your Crawlbase JavaScript token as _apiKey — screenshots always render in a real browser. Captures the full page by default; pass mode:"viewport" with width/height to constrain. Example: crawlbase_screenshot({ url: "https://example.com", _apiKey: "your-js-token" })

Input parameters:

- `_apiKey` (string, required): Your Crawlbase JavaScript token (screenshots require browser rendering). Free tier at https://crawlbase.com
- `country` (string): Two-letter ISO country code to route through, e.g. "US", "GB".
- `height` (number): Viewport height in pixels (only applies with mode:"viewport").
- `mode` (string): Capture mode: full rendered page by default; "viewport" captures only the visible area (pair with width/height).
- `page_wait` (number): Milliseconds to wait after page load before capturing — gives animations/JS time to settle.
- `scroll` (boolean): Scroll the page before capture to trigger lazy-loaded content.
- `url` (string, required): The absolute URL of the page to screenshot, e.g. "https://example.com"
- `width` (number): Viewport width in pixels (only applies with mode:"viewport").

### `crawlbase_structured` (~317 tokens)

Scrape a page into clean structured JSON using a named Crawlbase scraper — skip HTML parsing entirely. Common scraper names: "amazon-product-details", "amazon-serp", "google-serp", "facebook-page", "facebook-profile", "instagram-profile", "instagram-post", "linkedin-profile", "linkedin-company", "tiktok-profile", "ebay-product", "walmart-product-details", "github-repository", "generic-extractor". Full catalog: https://crawlbase.com/docs/scrapers/ — social-media scrapers (Facebook/Instagram/LinkedIn) work best with your JavaScript token. Example: crawlbase_structured({ url: "https://www.amazon.com/dp/1098145356", scraper: "amazon-product-details", _apiKey: "your-crawlbase-token" })

Input parameters:

- `_apiKey` (string, required): Your Crawlbase token (JavaScript token recommended for social-media scrapers). Free tier at https://crawlbase.com
- `country` (string): Two-letter ISO country code to route through, e.g. "US", "DE". Matters for localized storefronts and SERPs.
- `scraper` (string, required): The Crawlbase scraper name to apply, e.g. "amazon-product-details", "google-serp", "linkedin-profile". Catalog: https://crawlbase.com/docs/scrapers/
- `url` (string, required): The absolute URL of the page to scrape, e.g. "https://www.google.com/search?q=coffee" for google-serp.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Crawlbase MCP server?

Crawlbase is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crawlbase. Crawlbase MCP, wraps the Crawlbase Crawling API (crawlbase.com, formerly ProxyCrawl). One… This page covers its npm package (@pipeworx/mcp-crawlbase).

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

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

Crawlbase exposes 3 tools: crawlbase_scrape, crawlbase_screenshot, crawlbase_structured. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.

### Is the Crawlbase MCP server still maintained?

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

Crawlbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

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