Skip to main content
Glama
georgittanchev

web-tools-mcp-server

by georgittanchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to web-tools-mcp-server

No user-submitted related servers found.

    Related Servers

    • tracked-search

      MikeyBeez
      F
      license
      Not graded
      quality
      C
      maintenance
      A drop-in replacement for Claude's built-in web_search tool that automatically tracks usage and provides multiple search backends.
      -

    • CC Web MCP

      JcDizzy
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides web search and page fetching tools for third-party models (e.g., DeepSeek, Qwen, Kimi) in Claude Code, with configurable search backends, Markdown output, and safety boundaries.
      42 PyPI
      63
      MIT

    • webfetch-mcp

      simonediroma
      A
      license
      Not graded
      quality
      C
      maintenance
      Drop-in MCP replacement for the built-in WebFetch tool. Adds domain-scoped custom HTTP headers via YAML config, with bot-block detection, HTML-to-text extraction, retries, proxies, and prompt-injection sanitization.
      1
      MIT

    • ai-first-scraper-mcp

      yubinkim444
      A
      license
      A
      quality
      C
      maintenance
      Ad-free web scraping and search exposed as 3 MCP tools. fetch_page, fetch_pages_batch, search_web. Works with Claude Desktop, Cursor, Cline.
      10
      3
      52 PyPI
      2
      MIT

    • web-search-mcp

      quangnx99
      A
      license
      A
      quality
      B
      maintenance
      Enables web search, page fetching, and search statistics for Claude Code and any MCP client without requiring an API key, using automatic provider fallback and caching.
      3
      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

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: web_fetch retrieves a single page, web_bulk_fetch retrieves multiple pages in parallel, and web_search performs a web search. There is no overlap between these operations; even web_fetch and web_bulk_fetch are clearly differentiated by the number of URLs they handle.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with a web_ prefix: web_fetch, web_search, web_bulk_fetch. The naming is predictable and clearly indicates the action and resource, with 'bulk' correctly modifying the fetch verb.

    Tool Count5/5

    With only three tools, the set is well-scoped for a web utility server. Each tool covers a distinct primary use case (single fetch, bulk fetch, search), and the size is appropriate without being bloated or too sparse.

    Completeness5/5

    The tool surface covers the core operations for the domain: searching the web and fetching one or multiple pages, with strategy options (auto/direct/jina) for different anti-blocking needs. No obvious gaps for typical web research workflows, as pagination via count/offset is available in web_search.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources