Self-hosted MCP server with SearXNG + Crawl4AI for fast search and reliable web scraping in Claude Code. 3x faster than native tools with 100% scraping reliability.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"searxng-crawl4ai": {
"cwd": "/absolute/path/to/your/project",
"args": [
"fixed-mcp-server.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A self-hosted MCP (Model Context Protocol) server providing fast search and reliable web scraping using SearXNG + Crawl4AI stack.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in search / browser
Browser automation with Puppeteer for web scraping and testing
Web and local search using Brave Search API
Production ready MCP server with real-time search, extract, map & crawl.
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP Security Weekly
Get CVE alerts and security updates for Searxng Crawl4ai Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A self-hosted MCP (Model Context Protocol) server providing fast search and reliable web scraping using SearXNG + Crawl4AI stack.
This project evolved from limitations found in self-hosted Firecrawl:
Our solution provides:
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ │ │ │ │ │
│ SearXNG │ │ Crawl4AI │ │ Redis │
│ (Search) │ │ (Scraping) │ │ (Cache) │
│ │ │ │ │ │
│ Port 8081 │ │ Port 8001 │ │ Port 6380 │
└─────────────┘ └──────────────┘ └─────────────┘
│ │ │
└───────────────────┼───────────────────┘
│
┌──────────────┐
│ │
│ MCP Server │
│ (TypeScript) │
│ │
└──────────────┘
│
┌─────────────┐
│ │
│ Claude Code │
│ │
└─────────────┘
git clone https://github.com/yourusername/searxng-crawl4ai-mcp
cd searxng-crawl4ai-mcp
npm install
npm run build
# Start all services (SearXNG, Crawl4AI, Redis)
docker compose up -d
# Verify services are running
curl http://localhost:8081/search?q=test&format=json # SearXNG
curl http://localhost:8001/health # Crawl4AI
Simple Configuration (No Proxy):
{
"mcpServers": {
"searxng-crawl4ai": {
"command": "node",
"args": ["fixed-mcp-server.js"],
"cwd": "/absolute/path/to/your/project"
}
}
}
With Proxy Configuration:
{
"mcpServers": {
"searxng-crawl4ai": {
"command": "node",
"args": ["fixed-mcp-server.js"],
"cwd": "/absolute/path/to/your/project",
"env": {
"PROXY_URL": "http://username:password@your-proxy-server.com:10000"
}
}
}
}
Create .claude/settings.json:
{
"environmentVariables": {
"MAX_MCP_OUTPUT_TOKENS": "100000"
}
}
search_web - Lightning Fast Search{
"query": "latest AI developments 2025",
"maxResults": 10
}
Returns: 30+ search results in <1 second from multiple engines
crawl4ai_scrape - Advanced Web Scraping{
"url": "https://finance.yahoo.com/quote/BTC-USD/",
"formats": ["markdown"]
}
Returns: Full page content with metadata (title, word count, clean markdown)
search_and_scrape - Combined Power Workflow{
"query": "Bitcoin technical analysis September 2025",
"maxResults": 2
}
Returns: Search