ScrapingBot MCP Server
Related Servers
Alternatives to ScrapingBot MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to scrape web pages into Markdown, text, HTML, JSON, PDFs, screenshots, and structured data, while managing batch scraping jobs, persistent browser sessions, usage/request history, and docs lookup through native MCP tools.25120 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to scrape, crawl, map, search, and extract web pages as clean markdown or structured JSON directly through MCP tools.AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables agents to extract structured data from web pages by giving a URL and a natural-language prompt describing the fields to retrieve. It exposes this capability as an MCP tool that plugs into clients like Claude, VS Code, Cursor, and Windsurf.128 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to extract structured, prompt-defined data from any web page by supplying a URL and a description of the fields to retrieve. It exposes this capability as a single tool for use in MCP-compatible clients such as Claude, VS Code, Cursor, and Windsurf.128 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to search, scrape, crawl, map, and interact with live web pages, returning clean, structured, agent-ready content. It also supports recurring page monitoring, autonomous deep research, and credit-usage checks.151,287 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to fetch webpages and crawl sites, extract main content, and convert it into clean Markdown with preserved links for fast, token-efficient scraping.-
TDQS
Scored across 10 tools
The split between scrape_raw_html and the domain-specific extractors (retail, real estate, booking, grocery, search engine, social) is explicitly documented, including 'prefer X over raw_html' guidance, which removes most ambiguity. The residual overlap is scrape_retail vs scrape_grocery (both extract product title/price/brand from an e-commerce-like page) and scrape_booking vs scrape_real_estate for rental listings, where an agent could plausibly pick either.
Every tool is snake_case with a clear verb_noun form: scrape_<domain> for extraction and get_<resource> for retrieval (get_account, get_usage_history, get_social_media_result). The grouping is immediately legible and the async continuation tool is named to pair with its producer.
Ten tools is a tight, well-earned surface for a scraping service: one generic fetcher, five domain extractors, one search-engine tool, one social-media tool, and account/usage/async-result support. Nothing looks redundant or padding-like, and the set stays well under typical context-bloat thresholds.
The lifecycle is essentially covered: fetch, specialized extraction, account credit state, usage/error history, and an async result poller for the long-running social path. Minor gaps remain — no batch/bulk scraping, no screenshot or rendered-page artefact, and no way to discover which sites/APIs are supported other than the hardcoded examples in descriptions.