Log inSubmit server
Open WebSearch logo

Open WebSearch

by Aas-ee

Searches the web through multiple free engines and fetches content from web pages, GitHub READMEs, and CSDN.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Open WebSearch

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aas-ee-open-websearch": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 6 tools correctly (1mo ago).

Overview

The Aas-ee/open-webSearch MCP server provides live web search through multiple engines without API keys or authentication. It returns structured results with titles, URLs, and descriptions, and can retrieve content from generic web pages, Markdown, GitHub README files, and CSDN pages. Configure a default engine, result count, proxy, server mode, and other runtime behavior with environment variables. Reach for it when an MCP client needs current web results or basic article and documentation retrieval without a paid search API.

Use cases

  • Search current web results from an MCP client
  • Fetch readable content from a specific article page
  • Retrieve GitHub README documentation
  • Route searches through a local HTTP proxy

Key features

  • Multi-engine web search without API keys
  • Structured titles, URLs, and descriptions
  • Web, Markdown, GitHub README, and CSDN fetching
  • MCP, CLI, and local daemon modes
  • Configurable engine, result count, proxy, and search strategy

Tools6

What Open WebSearch lets your agent do. Expand a tool for its parameters.

Verified live~522 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

16/17 checks healthy over the last 77d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 0High 1Medium 0Low 0

Scanned 5d ago via OSV.dev · open-websearch@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1.9kStargazers on the source repository.
npm downloads33kPackage downloads in the last 30 days.
Last commit19d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Open WebSearch works

What Aas-ee/open-webSearch MCP server does

The Aas-ee/open-webSearch MCP server exposes web search and content retrieval through MCP, a command-line interface, and an optional local HTTP daemon. Search requests can use engines including Bing, Baidu, DuckDuckGo, Brave, Exa, CSDN, Juejin, Startpage, Sogou, and Hacker News. Linux.do is listed as temporarily unsupported.

Search responses contain structured result data such as titles, URLs, and descriptions. The server can also fetch content from individual CSDN pages, GitHub README files, and generic HTTP(S) pages or Markdown content. For extraction, searching first and then fetching a specific result is recommended because some homepages and JavaScript-heavy pages may not provide readable text.

How it works

For MCP use, the package can run through an stdio-compatible entrypoint. It also supports HTTP mode or both HTTP and stdio, depending on the MODE setting. The default port for HTTP operation is 3000. A separate local daemon can be started with open-websearch serve; its documented endpoints include health checks, search, and fetch operations. The open-websearch status command checks the daemon state.

The command-line interface supports one-shot searches, while the daemon stays available for repeated requests. Search actions can use the local daemon automatically when it is available, or a specific daemon can be selected with --daemon-url. HTTP proxy support is available for restricted network environments. Installation proxy settings and runtime proxy settings are separate concerns.

Setup and configuration

Install and launch the MCP entrypoint with:

Terminal
npx -y open-websearch@latest

The Aas-ee/open-webSearch MCP server does not require API keys or authentication. Optional settings include DEFAULT_SEARCH_ENGINE, ALLOWED_SEARCH_ENGINES, and SEARCH_MODE. SEARCH_MODE can select request-based or Playwright-based searching, or allow automatic selection. ENABLE_CORS and CORS_ORIGIN configure CORS behavior when HTTP access is enabled.

Set USE_PROXY=true and provide PROXY_URL to route runtime requests through an HTTP proxy. PORT changes the HTTP port, and MODE selects both, http, or stdio. FETCH_WEB_INSECURE_TLS can disable TLS verification for the web-content fetch request leg, but does not change Playwright browser navigation. This option should be limited to cases involving broken certificate chains.

Tools and capabilities

  • Search across supported engines without an API key.
  • Select a default engine and restrict the engines available to clients.
  • Control the number of returned results.
  • Fetch generic web or Markdown content.
  • Retrieve GitHub README and CSDN page content.
  • Run as an MCP server, one-shot CLI, or local HTTP daemon.

The project also documents an optional agent skill that helps discover and activate an available open-websearch path. That skill complements the MCP server, CLI, or daemon rather than replacing them.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Open WebSearch

Run `npx -y open-websearch@latest` to start the MCP entrypoint.

No.

Supported engines include Bing, Baidu, DuckDuckGo, Brave, Exa, CSDN, Juejin, Startpage, Sogou, and Hacker News. Linux.do is temporarily unsupported.

Yes. It supports fetching GitHub README content, along with CSDN pages and generic HTTP(S) or Markdown content.

Yes. Set `USE_PROXY=true` and configure `PROXY_URL` for runtime HTTP proxy use.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpen WebSearch AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aas-ee-open-websearch?style=directory)](https://allmcps.com/mcp/aas-ee-open-websearch)
HTML Embed
<a href="https://allmcps.com/mcp/aas-ee-open-websearch"><img src="https://allmcps.com/api/badge/aas-ee-open-websearch?style=directory" alt="Open WebSearch on AllMCPs" /></a>