MyWebSearch
Related Servers
Alternatives to MyWebSearch
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to run web and image searches across nine engines with automatic fallback and ad filtering, fetch pages and PDFs as Markdown, and search WeChat Official Account articles — all without requiring a search account or API key out of the box. Works over stdio or Streamable HTTP with any MCP-capable client.5479 npmApache 2.0
- AlicenseAqualityAmaintenanceSelf-hosted web search and page extraction for AI agents. Stdio MCP server, HTTP API and Python/npm CLI.840 npm51 PyPI2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.4MIT
- AlicenseAqualityCmaintenanceA self-hosted MCP server for web search with multi-engine support, combining search, URL fetching, and deep research along with proxy routing and deduplication.3MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing web search, news search, and X/Twitter search capabilities via HTTP or stdio.-
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to run web and academic searches across multiple engines (Baidu, Bing, DuckDuckGo, Tavily, Exa, Doubao and 9 scholarly sources) with local relevance scoring, deduplication and caching, plus SSRF-protected page fetching and PDF parsing, and works without any API key. It plugs into MCP clients like Claude Code, Cursor and Qwen Code, or can be embedded as a Go module.26MIT
TDQS
Scored across 4 tools
The four tools mostly target distinct acquisition modes: web search, generic URL fetching, GitHub-specific fetching, and package/library documentation lookup. There is some overlap because fetchWebContent can fetch documentation and public GitHub pages, while search can also retrieve article content, but the descriptions clarify primary intent.
All names use lowerCamelCase and are verb-led or action-oriented, with fetchGithubContent and fetchWebContent sharing a clear fetch+source pattern. The standalone search name and queryDocs create minor stylistic deviation, but the set remains predictable and readable.
Four tools is well-scoped for a web retrieval/search server, and each tool covers a distinct retrieval mode. There are no redundant tools bloating the surface, and the small set is easy to navigate.
The surface covers the main retrieval workflows: web search, general content extraction, GitHub/Gitee content, and library documentation lookup. Minor gaps exist around specialized crawling or direct repo cloning, but core agent needs are well covered.