X402 Scraper API vs CRW Web Scraper
A side-by-side look at the X402 Scraper API and CRW Web Scraper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose X402 Scraper API for search & data extraction work as a local process; choose CRW Web Scraper for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose X402 Scraper API when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BASE_RPC_URL.
Choose CRW Web Scraper when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | BASE_RPC_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,161 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View X402 Scraper API | View CRW Web Scraper |
Tools & capabilities
X402 Scraper API tools
No tool names declared yet. Check the project README from the listing page.
CRW Web Scraper tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
X402 Scraper API
{
"mcpServers": {
"x402-scraper-api": {
"command": "npx",
"args": [
"-y",
"x402-scraper-api"
],
"env": {
"BASE_RPC_URL": "YOUR_BASE_RPC_URL_HERE"
}
}
}
}
CRW Web Scraper
{
"mcpServers": {
"crw-web-scraper": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
]
}
}
}
Frequently asked questions
X402 Scraper API is categorized under Search & Data Extraction and uses a local stdio subprocess. CRW Web Scraper belongs to Search & Data Extraction and uses a local stdio subprocess. Pick X402 Scraper API for search & data extraction work and CRW Web Scraper for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
X402 Scraper API is listed as a paid service. CRW Web Scraper has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add x402-scraper-api and crw-web-scraper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X402 Scraper API has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. CRW Web Scraper has 51/100 (Good) with 1 views, 0 installs and 1,161 GitHub stars.