Skip to main content
Glama
marcopesani

serper-search-scrape-mcp-server

by marcopesani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to serper-search-scrape-mcp-server

No user-submitted related servers found.

    Related Servers

    • evo-scry

      krich11
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.
      MIT

    • mcp-searxng

      atomlong
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that integrates the SearXNG API for web search and URL content extraction with advanced features like pagination, caching, and proxy support.
      4
      8,974 npm
      2
      MIT

    • mcp-searxng-local

      dduartee
      A
      license
      A
      quality
      B
      maintenance
      MCP server for local web search via SearXNG, providing unlimited queries without API keys or cost, with automatic fallback to public instances.
      3
      1
      MIT

    • go_serper_mcp_server

      hightemp
      A
      license
      Not graded
      quality
      D
      maintenance
      A Go-based MCP server that provides comprehensive access to the Serper Google Search API, including tools for images, news, maps, and scholar results. It also features a dedicated endpoint for scraping webpage content directly.
      3 npm
      MIT

    • SerpApi MCP Server

      serpapi
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that integrates with SerpApi to retrieve search results from multiple search engines including Google, Bing, Yahoo, and others, enabling fast access to both live and archived search data.
      3
      173
      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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: google_search is for performing web searches and retrieving search results, while scrape is for extracting content from a specific webpage. There is no overlap in functionality, making it easy for an agent to choose the right tool for each task.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern using snake_case with descriptive, action-oriented names (google_search and scrape). The naming is straightforward and predictable, with no deviations or mixed conventions.

    Tool Count3/5

    With only 2 tools, the server feels thin for a search-and-scrape domain, as it might lack additional utilities like batch processing, advanced filtering, or result summarization. However, the core functions are covered, making it borderline but functional.

    Completeness4/5

    The tools cover the essential workflows for search and scraping: performing searches and extracting webpage content. Minor gaps exist, such as no tool for managing search history or handling pagination, but agents can work around these with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources