Scrupp vs ShadowCrawl
A side-by-side look at the Scrupp and ShadowCrawl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scrupp for search & data extraction work as a local process; choose ShadowCrawl for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Scrupp when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SCRUPP_API_KEY, SCRUPP_WAIT_SECONDS, PORT, MCP_PUBLIC_URL, SCRUPP_AUTH_SERVER_URL, SCRUPP_API_URL.
Choose ShadowCrawl when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CORTEX_SCOUT_TOOL_TIMEOUT_SECS, CORTEX_SCOUT_TOOL_TIMEOUT_SECS_SCRAPE_URL, CORTEX_SCOUT_TOOL_TIMEOUT_SECS_SEARCH_STRUCTURED, CORTEX_SCOUT_PORT, PORT, RUST_LOG.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 39/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | SCRUPP_API_KEYSCRUPP_WAIT_SECONDSPORTMCP_PUBLIC_URLSCRUPP_AUTH_SERVER_URLSCRUPP_API_URL |
Tools & capabilities
Scrupp tools
No tool names declared yet. Check the project README from the listing page.
ShadowCrawl 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.
Scrupp
{
"mcpServers": {
"scrupp": {
"command": "npx",
"args": [
"-y",
"scrupp-mcp-server"
],
"env": {
"SCRUPP_API_KEY": "YOUR_SCRUPP_API_KEY_HERE",
"SCRUPP_WAIT_SECONDS": "YOUR_SCRUPP_WAIT_SECONDS_HERE",
"PORT": "YOUR_PORT_HERE",
"MCP_PUBLIC_URL": "YOUR_MCP_PUBLIC_URL_HERE",
"SCRUPP_AUTH_SERVER_URL": "YOUR_SCRUPP_AUTH_SERVER_URL_HERE",
"SCRUPP_API_URL": "YOUR_SCRUPP_API_URL_HERE"
}
}
}
}
ShadowCrawl
{
"mcpServers": {
"shadowcrawl": {
"url": "https://api.openai.com/v1"
}
}
}
Frequently asked questions
Scrupp is categorized under Search & Data Extraction and uses a local stdio subprocess. ShadowCrawl belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Scrupp for search & data extraction work and ShadowCrawl 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.
Scrupp is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. ShadowCrawl 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 scrupp and shadowcrawl as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scrupp has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. ShadowCrawl has 44/100 (Fair) with 1 views, 0 installs and 70 GitHub stars.
