Crawlbase
NPM · @PIPEWORX/MCP-CRAWLBASE · 2 COMPONENTS
Crawlbase MCP — wraps the Crawlbase Crawling API (crawlbase.com, formerly ProxyCrawl). One…
Available components
Last scanned (2 hours ago)
Scores higher than 68% 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-crawlbase). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. 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
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 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 31 Oct 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 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-crawlbase@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-crawlbase |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-crawlbase/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612284498 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:be68a629c3ca1ac38415983132fdfd9ef243e67d43b916dedb4595329ec4cc50de6c2434c41d2a08f7a7c9e5c3ea0893cd5d8d4a2d7c925d4a142e038 |
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 →
crawlbase_scrape ~433
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | The absolute URL to scrape including scheme, e.g. "https://example.com/page" |
No output schema declared.
No examples provided.
crawlbase_screenshot ~306
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | The absolute URL of the page to screenshot, e.g. "https://example.com" |
| width | number | – | Viewport width in pixels (only applies with mode:"viewport"). |
No output schema declared.
No examples provided.
crawlbase_structured ~317
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | The Crawlbase scraper name to apply, e.g. "amazon-product-details", "google-serp", "linkedin-profile". Catalog: https://crawlbase.com/docs/scrapers/ |
| url | string | yes | The absolute URL of the page to scrape, e.g. "https://www.google.com/search?q=coffee" for google-serp. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-crawlbase
claude mcp add pipeworx-io-crawlbase -- npx -y @pipeworx/mcp-crawlbase
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.