Skip to main content
Glama
ye4wzp

google-search-mcp-v2

by ye4wzp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to google-search-mcp-v2

No user-submitted related servers found.

    Related Servers

    • Perplexity MCP Server

      RossH121
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.
      6
      4
      MIT

    • Gemini Google Web Search MCP

      louxsye
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI models to perform Google Web searches using the Gemini API, complete with citations and grounding metadata for accurate information retrieval. It is compatible with Claude Desktop and other MCP clients for real-time web access.
      1
      3
      Apache 2.0

    • MCP Web Server

      zhaiy
      F
      license
      D
      quality
      D
      maintenance
      A local MCP server providing free network access capabilities including HTTP requests, web search, webpage content extraction, and optional screenshots, designed for integration with Claude Desktop or Claude Code.
      6
      -

    • multsearch-mcp

      liujp2015
      F
      license
      A
      quality
      B
      maintenance
      A dual-path web search MCP server for Claude Code that cross-validates results via Tavily/Firecrawl and Google, explicitly returning sources to reduce hallucinations.
      7
      -
    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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct purpose, but search_and_extract combines functionality of google_search and batch_fetch_urls, which could cause some ambiguity for agents that only need raw search results.

    Naming Consistency3/5

    Naming conventions are mixed: google_search is branded, fetch_url/batch_fetch_urls follow verb_noun, while search_and_extract and search_by_image use different patterns (verb_and_verb, verb_prep_noun).

    Tool Count5/5

    With 5 tools covering basic search, content extraction, and image search, the count is well-scoped for a search-focused server without unnecessary bloat.

    Completeness4/5

    Core operations (search, fetch, combined, image search) are covered, but missing pagination and advanced search filters represent minor gaps for more complex workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources