Skip to main content
Glama
naku111

Web Scraper MCP Server

by naku111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Web Scraper MCP Server

No user-submitted related servers found.

    Related Servers

    • TheCrawler

      manchittlab
      A
      license
      Not graded
      quality
      D
      maintenance
      Open-source web scraper and extraction MCP server with JavaScript rendering, markdown output, PDF/DOCX parsing, structured errors, and validated extraction contract diagnostics for agents.
      2
      AGPL 3.0
    • ScrapeGraph MCP Server by ScrapeGraphAI

      ScrapeGraph MCP Serverofficial

      ScrapeGraphAI
      A
      license
      A
      quality
      D
      maintenance
      A production-ready Model Context Protocol server that enables language models to leverage AI-powered web scraping capabilities, offering tools for transforming webpages to markdown, extracting structured data, and executing AI-powered web searches.
      8
      100 PyPI
      113
      MIT

    • Firecrawl MCP Server

      ampcome-mcps
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables web scraping, crawling, and content extraction capabilities through integration with Firecrawl.
      8
      190,664 npm
      2
      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 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly divided between scraping operations (scrape_images, scrape_text), listing operations (list_images, list_texts), cleanup operations (cleanup_images, cleanup_texts), and status monitoring (get_scraping_status). There is no overlap in functionality.

    Naming Consistency5/5

    The naming follows a perfectly consistent verb_noun pattern throughout. All tools use snake_case with clear action prefixes (scrape_, list_, cleanup_, get_) followed by specific resource nouns (images, texts, scraping_status). There are no deviations in naming conventions.

    Tool Count5/5

    The 7 tools are well-scoped for a web scraping server. Each tool earns its place by covering distinct aspects of the scraping workflow: initiating scrapes, listing results, cleaning up files, and checking status. This is an appropriate number for the domain without being too thin or bloated.

    Completeness4/5

    The tool surface provides excellent coverage for core web scraping operations with clear CRUD-like patterns (create via scrape, read via list, delete via cleanup). The only minor gap is the lack of update operations for existing scraped content, but agents can work around this by re-scraping. Status monitoring is included, which is valuable for workflow management.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources