No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.
by Aas-ee · submitted by oktofeesh1·added 2026-06-06·1,422 source repo stars·
open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets., Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections., Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting., The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API., Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately., Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
Privacy notes
Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context., Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers., Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages., The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs., Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
Author
Aas-ee
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 5 privacy notes across 3 risk areas. Review closely: credentials & tokens, network access.
3 areas
SafetyGeneralopen-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
SafetyGeneralSearch and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
SafetyCredentials & tokensRespect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
SafetyNetwork accessThe optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
SafetyCredentials & tokensProxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
SafetyGeneralLeave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
PrivacyNetwork accessSearch queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
PrivacyNetwork accessLive search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
PrivacyCredentials & tokensPlaywright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
PrivacyCredentials & tokensThe project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
PrivacyNetwork accessRedact sensitive search terms and downloaded page content before sharing transcripts or logs.
Disclosure: Community-maintained Apache-2.0 MCP server, CLI, and local daemon for no-key web search and public content retrieval, published as the `open-websearch` npm package.
Safety notes
open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
Privacy notes
Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
Prerequisites
Node.js 18 or newer for the published npm package.
Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.
A decision about whether to use stdio-only MCP mode, CLI mode, or the local daemon mode.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Stars
1,422 source repo stars
Forks
165
Updated
2026-06-15T17:06:48Z
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Disclosure
Community-maintained Apache-2.0 MCP server, CLI, and local daemon for no-key web search and public content retrieval, published as the `open-websearch` npm package.
open-webSearch gives Claude and other MCP clients no-key web search and public
content retrieval. It supports multiple search engines, public page fetching,
GitHub README fetching, CLI use, stdio MCP mode, and an optional local daemon
for repeated local HTTP calls.
Use it when Claude needs a lightweight search/fetch tool for public web
research without provisioning a commercial search API key, while still keeping
site terms, rate limits, query privacy, and local daemon exposure visible.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, package manifest, local daemon API docs, server
entrypoint, runtime configuration, tool setup, and URL safety helpers for
current setup and behavior details.
Features
Search across supported engines such as Bing, DuckDuckGo, Brave, Exa, Baidu,
CSDN, Juejin, Startpage, and Sogou.
Limit available engines with ALLOWED_SEARCH_ENGINES.
Fetch generic public web pages and Markdown content.
Fetch GitHub repository README content.
Fetch supported article pages from CSDN and Juejin.
Run as a local MCP stdio server, a one-shot CLI, or an explicit local daemon.
Configure request-only, auto, or Playwright search mode for Bing workflows.
Reuse local or remote Playwright/Chromium sessions when manually configured.
Route requests through an approved HTTP proxy when needed.
Reject private or local network fetch targets through URL safety checks.
Start the local daemon separately only when you need a reusable local HTTP
service for scripts, skills, or plugin integrations.
Use Cases
Search the public web without provisioning a search API key.
Compare results across multiple search engines.
Fetch the readable content of a specific public page after search.
Retrieve a GitHub README for quick repository context.
Use a local daemon for repeated search/fetch calls from nearby tooling.
Route live search traffic through an approved proxy in restricted networks.
Use Playwright fallback for pages that need browser-rendered content.
Safety and Privacy
open-webSearch is a public web search and fetch tool, so results can be noisy,
blocked, biased, or incomplete. Verify important claims against primary sources
and respect each site's current terms before repeated fetching.
Keep stdio mode as the default for MCP clients. If you start the daemon, treat
it as local-only tooling, keep CORS narrow when enabled, and avoid connecting it
to browser sessions or proxies that expose sensitive cookies or network routes.
Show that open-webSearch MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/open-websearch-mcp-server)
How it compares
open-webSearch MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.
Local-first MCP server for web scraping, crawling, URL mapping, batch extraction, structured extraction, summarization, diffing, brand extraction, and optional hosted API fallback for bot-protected pages.
MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools.
MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge.
✓open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets.
Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections.
Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting.
The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API.
Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately.
Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.
✓WebClaw MCP Server can scrape one URL, crawl same-origin links, map URLs, batch multiple URLs, extract structured data, summarize pages, compare snapshots, and extract brand metadata.
Scraping, crawling, search, research, and hosted fallback can trigger target-site rate limits, bot protections, legal restrictions, or terms-of-service limits.
The server validates public HTTP URLs and rejects private or internal destinations, but operators should still avoid fetching internal, secret, customer-specific, or credential-bearing URLs.
Cookie-bearing requests, proxies, and browser profiles can expose authenticated sessions or route traffic through external infrastructure.
Setting `WEBCLAW_API_KEY` enables hosted API fallback, which can send target URLs and page context to the WebClaw service.
Structured extraction and summarization may use configured LLM providers; review provider data handling before enabling those tools with sensitive pages.
✓Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers.
Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns.
GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used.
Large result mode can write response content to files; review where those files are stored before using it with private or regulated data.
Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations.
✓Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project.
Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested.
Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content.
Generated audio and image publishing can call configured model/provider services and consume credits or quota.
Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes.
Privacy notes
✓Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context.
Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers.
Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages.
The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs.
Redact sensitive search terms and downloaded page content before sharing transcripts or logs.
✓URLs, fetched page content, crawl results, extracted structured data, snapshots, brand metadata, cookies, proxy settings, API keys, and LLM prompts can be exposed to the MCP client.
Crawled pages may include personal data, customer content, non-public links, access tokens embedded in URLs, or site-specific identifiers.
Diff snapshots and exported JSON can preserve page content longer than expected; store and delete them according to the workflow's retention needs.
Hosted fallback, proxy providers, search/research APIs, and LLM providers may observe target URLs, headers, cookies, prompts, and extracted content when enabled.
Redact sensitive URLs and extracted data before sharing MCP transcripts, crawl results, logs, or generated RAG context.
✓Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client.
Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies.
Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider.
GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details.
Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens.
✓Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client.
Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot.
Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content.
Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations.
Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.
Prerequisites
Node.js 18 or newer for the published npm package.
Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.
Node.js for the `create-webclaw` installer, or Rust/Cargo when building the MCP binary from source.
Review of AGPL-3.0 obligations before redistributing or operating modified server versions.
Review of target-site terms, robots expectations, rate limits, and scraping permissions.
Optional `WEBCLAW_API_KEY` only when hosted API fallback is acceptable for bot-protected or JavaScript-heavy pages.
Node.js 22 or newer for the published npm package.
At least one provider API key for Tavily, Kagi, Brave Search, GitHub, Exa, Linkup, or Firecrawl.
Optional `FIRECRAWL_BASE_URL` when using a self-hosted Firecrawl instance.
Optional `OMNISEARCH_LARGE_RESULT_MODE` choice for file or inline handling of large results.
Active Graphlit platform account and project access.
Graphlit organization ID, environment ID, and JWT secret from the Graphlit API settings dashboard.
Node.js 18 or newer for the npm stdio server.
Review of which files, URLs, feeds, SaaS connectors, memories, conversations, collections, and web crawls Claude may create or query.