Skip to main content
Glama
theriskus

mcp_web_search

by theriskus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp_web_search

No user-submitted related servers found.

    Related Servers

    • web-search-cli

      AusertDream
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables web search using Bing and DuckDuckGo combined, and fetching readable content from web pages, with no API key required.
      9 npm
      2
      MIT

    • Web Search MCP

      pranavms13
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables web searching through Google, DuckDuckGo, and Bing using a headless Chrome browser, returning structured results with titles, URLs, and snippets. Also supports fetching and extracting text content from any webpage.
      14
      MIT

    • MCP MyZ Search

      kimmywork
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables web search across Bing, DuckDuckGo, and Google using Playwright automation, with tools for retrieving search results and extracting page text content.
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    Tools are mostly distinct: web_search for search results, web_fetch for static content, web_scrape for dynamic pages, open_url for a quick preview. However, open_url and web_fetch have overlapping functionality (both fetch a URL), which could cause slight confusion if descriptions are not carefully read.

    Naming Consistency3/5

    Three tools use the 'web_' prefix (web_fetch, web_scrape, web_search), but open_url breaks the pattern. Verbs are inconsistent (open, fetch, scrape, search). A uniform naming convention like 'web_search', 'web_fetch', 'web_scrape', 'web_preview' would be clearer.

    Tool Count5/5

    Four tools is an appropriate number for a web search MCP server. Each tool serves a distinct purpose (search, static fetch, dynamic scrape, quick preview), and no tool feels unnecessary. The count is well-scoped.

    Completeness4/5

    The tool surface covers the main workflows: searching the web, retrieving content from static pages, and handling dynamic pages. A minor gap is the lack of a dedicated tool for metadata extraction or advanced search filtering, but the core functionality is complete for typical usage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources