Enterprise DNAEnterprise DNA

MCP Servers · Search and Research

Aas-ee/open-webSearch

Multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval — skill-guided workflows, no API keys.

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed Aas-ee/open-webSearch yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About Aas-ee/open-webSearch

A TypeScript-based MCP server, CLI, and daemon that enables agents to perform multi-engine web searches and content retrieval without requiring API keys. It uses skill-guided workflows to orchestrate searches across multiple engines and parse results locally.

Best for

Developers building autonomous agents that need flexible, API-key-free web search integration

Use cases

  • Letting autonomous agents search the web and retrieve page content
  • Running local search pipelines without external API dependencies
  • Integrating multi-engine search into MCP-compatible development workflows

Notes

1,338 stars on GitHub. Last updated 2026-05-16. Licensed Apache-2.0.

Pros

  • No API keys needed, reducing setup friction and costs
  • Supports multiple search engines for diverse retrieval strategies
  • Modular skill-guided workflow design for adaptable agent behavior

Cons

  • Limited to web search and content retrieval, not a general-purpose MCP server
  • Requires running a daemon or CLI process, adding operational overhead
  • May depend on public search engines that could throttle or block automated access

Key facts

What we have checked

Days since the last commit
18
Checked GitHub
GitHub forks
188
Checked GitHub
GitHub stars
1,875
Checked GitHub
Days to a first reply on issues
99.7
Checked GitHub
Open issues
11
Checked GitHub
Releases in the last 90 days
1
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx skills add https://github.com/Aas-ee/open-webSearch --skill open-websearch

Tools exposed

  • ENABLE_CORS
  • CORS_ORIGIN
  • DEFAULT_SEARCH_ENGINE
  • USE_PROXY
  • PROXY_URL
  • FAKE_IP_CIDRS
  • FETCH_WEB_INSECURE_TLS
  • ALLOWED_SEARCH_ENGINES
  • SEARCH_MODE
  • PLAYWRIGHT_PACKAGE
  • PLAYWRIGHT_MODULE_PATH
  • PLAYWRIGHT_EXECUTABLE_PATH
  • PLAYWRIGHT_WS_ENDPOINT
  • PLAYWRIGHT_CDP_ENDPOINT
  • PLAYWRIGHT_HEADLESS
  • PLAYWRIGHT_NAVIGATION_TIMEOUT_MS
  • OPEN_WEBSEARCH_PROFILE_DIR
  • MCP_TOOL_SEARCH_NAME
  • MCP_TOOL_FETCH_LINUXDO_NAME
  • MCP_TOOL_FETCH_CSDN_NAME

Clients the listing names (not checked here)

Claude Desktop, Cursor, Continue, VS Code

Install

Add Aas-ee/open-webSearch to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What Aas-ee/open-webSearch connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Health and security

Is Aas-ee/open-webSearch looked after, and what do its setup files show

Health score

38 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 18 days ago
Releases7.5 of 151 release in 90 days
Issue replies0 of 20First reply in 99.7 days (median)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Security check static checks

97 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1. What it checks

Licence: Apache-2.0

  • Low The documented install uses skills, whose published metadata points at github.com/vercel-labs/skills, not this repository. Check it is the right package before installing.
  • Note No published npm or PyPI package of this repository was found, so package advisories were not checked.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →