Skip to main content
Glama
ScrapeUnblocker

ScrapeUnblocker MCP Server

Official
by ScrapeUnblocker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ScrapeUnblocker MCP Server

No user-submitted related servers found.

    Related Servers

    • SteadyFetch

      carsonlabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with reliable web fetching capabilities, handling retries, caching, and anti-bot bypass automatically.
      MIT

    • BypassAPI MCP Server

      inside83
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fetch any web page (including those behind Cloudflare or CAPTCHAs), extract clean markdown, structured data, crawl sites, and map URLs via BypassAPI.
      MIT
    • @unblockingapi/mcp by unblockingapi

      @unblockingapi/mcpofficial

      unblockingapi
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to fetch bot-protected web pages, run structured Google searches, and check domain authority through UnblockingAPI's anti-detection engine and residential proxies.
      3
      621 npm
      1
      MIT

    • Fetch MCP Server

      MaartenSmeets
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to fetch and extract web content using browser automation, OCR, and multiple extraction methods, handling JavaScript rendering and anti-scraping techniques.
      17
      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.
      13
      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.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have mostly distinct purposes: fetch_html retrieves raw HTML with optional interaction, list_elements extracts selectable elements, fetch_parsed returns structured JSON, and google_search performs web searches. However, fetch_html and fetch_parsed could be confused since both fetch pages; the distinction (raw HTML vs. parsed JSON) is clear from descriptions but could still cause misselection if an agent needs structured data but picks fetch_html.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern: fetch_html, list_elements, fetch_parsed, google_search. All start with a verb (fetch, list, google) followed by a noun. Minor inconsistency: 'google_search' mixes a brand (google) with the action, but the pattern is clear and predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of scraping and unblocking web pages. Each tool serves a distinct function: fetching raw HTML, discovering elements, getting parsed data, and searching. This is a tight, purposeful set without redundancy.

    Completeness3/5

    The set covers the core scraping workflow: discover URLs (google_search), inspect page structure (list_elements), fetch with or without interaction (fetch_html), and extract structured data (fetch_parsed). However, there is no tool to handle common post-fetch actions like saving results or managing sessions, and no tool for custom parsing beyond fetch_parsed's AI output. The fetch_html tool includes browser steps, but there is no tool for handling cookies or persistent sessions. Still, for a minimal scraping server, the workflow is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources