Skip to main content
Glama
websearch-mcp

websearch-mcp

by xronocode

Related Servers

Alternatives to websearch-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables keyless multi-engine web, news, image, and video metasearch plus full-page markdown extraction for AI agents over MCP, with resilient fallback across DuckDuckGo, Bing, Brave, Google, and other backends.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Free web search, web-page reading as Markdown, and llms.txt documentation retrieval for MCP clients. Runs locally with Node.js over stdio using @alkasima/alka-search-mcp. Searches DuckDuckGo, Mojeek, and Brave; default providers require no API key. Website and provider availability may vary.
      8
      3
      31 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      5
      136 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes metasearch across many engines and a page-to-Markdown fetcher as two MCP tools, web_search and web_fetch, so any MCP client can run searches and pull clean article content on demand. It also supports news-focused queries with category and time-range filters, plus optional inline page content.
      AGPL 3.0

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation3/5

    search_news, search_semantic and the generic search all perform web search with overlapping use cases; the descriptions give routing hints (e.g. 'articles about X' could reasonably go to search or search_semantic), so boundaries are not crisp. search_github and fetch are clearly distinct. An agent must read the routing prose carefully to pick correctly.

    Naming Consistency4/5

    Four of five tools follow a search_<domain> pattern (search_news, search_semantic, search_github), and fetch is a clean verb. The bare 'search' breaks the pattern slightly where search_web would have been more consistent, but overall the convention is readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for a search/fetch server: general search, news, semantic, code search, and URL fetch each earn their place with no filler.

    Completeness4/5

    The surface covers the main research workflow (search → fetch → code/news lookup) with sensible fallbacks and caching. Minor gap: when a page is JS-rendered the fetch tool points users to 'browser automation' but no such tool exists, leaving a dead end, and there is no image or pagination support beyond max_results=20.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues