Log inSubmit server
My Websearch logo

My Websearch

Keyless MCP server for multi-engine web search, article extraction, GitHub content, and technical documentation lookup.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install My Websearch

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

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for my-websearch, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

my-websearch combines multi-engine web search with focused web, repository, and library-documentation retrieval for AI coding agents. Its MCP tools can fan out queries across Chinese, English, and developer-focused sources, extract cleaned content from public URLs, and retrieve GitHub or Gitee resources without cloning repositories. No API key is required for the core search and fetching features; Exa and Brave API keys are optional paths.

Use cases

  • Search across Chinese, English, and developer-focused engines
  • Extract readable articles, PDFs, code, tables, and citations
  • Inspect GitHub or Gitee files, issues, pull requests, and commits
  • Look up official documentation and code examples for packages
  • Retrieve focused web passages for an AI coding workflow

Key features

  • Multi-engine search with query fan-out and filtering
  • Readable web and PDF extraction with focus and schema modes
  • GitHub and Gitee resource retrieval without cloning
  • Context7-based package documentation lookup
  • MCP STDIO, Streamable HTTP, SSE, CLI, and local daemon modes

Tools4

What My Websearch lets your agent do. Expand a tool for its parameters.

Verified live~2.0k 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.

10/10 checks healthy over the last 55d

What it can do

From the 4 tools this server returned when we ran it; 4 declare their own safety hints.

Handles credentials · 1Makes network requests · 4Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age75 days
Maintainers1

Observed 2026-10-29 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · my-websearch (npm)

Adoption & maintenance

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

GitHub stars2Stargazers on the source repository.
npm downloads4kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How My Websearch works

What my-websearch does

my-websearch provides MCP tools for search and data extraction, with additional CLI and local HTTP daemon modes. It can query a broad set of general, regional, news, developer, academic, and code-search sources, then return results with resolved links and structured metadata. The server is designed for AI coding workflows that need both discovery and retrieval rather than search-result links alone.

Its four MCP tools are search, fetchWebContent, fetchGithubContent, and queryDocs. Core operation is keyless. Exa can be used when an optional free key is configured, and Brave offers an optional API-key fallback.

How it works

search routes requests among Chinese, English, and specialist engines. It supports multiple queries in one call, URL deduplication, time-range filtering, site restrictions, and an option to fetch the leading articles. Available sources include Bing, Baidu, CSDN, Juejin, Sogou, DuckDuckGo, Startpage, Yahoo, Brave, Exa, GitHub, Stack Overflow, Hacker News, arXiv, Bing News, and grep.app through the code search path.

The server uses direct HTTP retrieval and engine-specific request handling. It can detect operating-system proxy settings and route selected overseas engines through a proxy while keeping domestic engines direct. Outside mainland China, direct access without a proxy is the supported default. Some anti-bot challenges are handled computationally; DuckDuckGo's human CAPTCHA is reported rather than bypassed.

Setup and configuration

The server supports MCP over STDIO for desktop clients and Streamable HTTP or SSE for remote clients. It can also run as a one-shot CLI command or a persistent local HTTP daemon with connection-pool reuse and a Prometheus /metrics endpoint.

No API key is needed for the main tools. PROXY_URL can be used when a proxy is required. BRAVE_API_KEY is an optional fallback for Brave search, while Exa supports an optional free key. The server also detects system proxy configuration on Windows, macOS, and Linux.

Tools and capabilities

  • fetchWebContent retrieves readable material from public web pages, documentation, and PDFs. It removes common page chrome while retaining titles, code blocks, and tables.
  • Web extraction supports batches of one to three URLs, CSS-selector scoping, BM25-focused output, paging with startIndex, caching, JSON extraction through schemas, citations, and retained links.
  • fetchGithubContent reads GitHub and Gitee repositories, source files, trees, issues, pull requests, commits, comparisons, releases, and README files. Source requests can select a branch, tag, or commit and can restrict output to line ranges.
  • queryDocs looks up official library and package documentation, API references, and code snippets through Context7, with fallback lookup through npm, PyPI, and GitHub README content.
  • Search results can use specialist APIs such as GitHub, Stack Exchange, Hacker News, arXiv, and grep.app in addition to conventional web engines.

Limitations and notes

fetchGithubContent retrieves selected repository resources; it is not a repository clone. Web extraction targets public URLs. Engine availability and response behavior can vary with network conditions and anti-bot systems. Brave may require waiting, changing the IP, or using its API key when both HTTP retrieval and the browser-based challenge path fail. Exa is skipped when its optional key is not configured.

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 My Websearch

my-websearch is an MCP server that connects AI clients to multi-engine web search, public web and PDF extraction, GitHub and Gitee content retrieval, and package documentation lookup. Its main tools are search, fetchWebContent, fetchGithubContent, and queryDocs, with no API key required for core use.

Install and run it through one of its supported deployment modes: MCP STDIO, Streamable HTTP, SSE, a one-shot CLI, or a local HTTP daemon. The package is published as my-websearch, and the server can run without API keys for its core features.

Yes, my-websearch supports Cursor through MCP STDIO, and it also supports HTTP-based MCP modes for clients that use them. The server is likewise described for Claude Desktop, Windsurf, and Cline.

Yes, fetchGithubContent can retrieve GitHub or Gitee source files from blob URLs, including a selected branch, tag, or commit and optional line ranges. It fetches repository resources rather than cloning the repository.

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 PreviewMy Websearch AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/my-websearch?style=directory)](https://allmcps.com/mcp/my-websearch)
HTML Embed
<a href="https://allmcps.com/mcp/my-websearch"><img src="https://allmcps.com/api/badge/my-websearch?style=directory" alt="My Websearch on AllMCPs" /></a>