scrape-mcp
Related Servers
Alternatives to scrape-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.22 npmISC
- AlicenseAqualityCmaintenanceEnables AI agents to extract clean, structured web content (articles, tables, links, visual layouts) optimized for LLM token efficiency, with fast response times and optional JavaScript support.538 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to fetch and process web content securely, including HTML-to-markdown conversion, reader mode, metadata extraction, RSS/sitemap parsing, and robots.txt-aware requests with SSRF protection.15126 npm2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.312 npmMIT
- AlicenseBqualityAmaintenanceEnables AI agents to fetch web pages, convert them into token-efficient semantic Markdown, and extract hyperlinks and page metadata while rotating realistic browser fingerprints to reduce anti-bot blocks.3MIT

foundrynet-scrapeofficial
FlicenseNot gradedqualityFmaintenanceEnables AI agents to extract clean, structured content from any web page via a pay-per-call API or with a Forge key.-
TDQS
Scored across 9 tools
The five web_* tools have distinguishable roles: single page fetch (web_fetch), given-URL batch (web_batch), link-discovery/pagination crawl (web_crawl), schema-based structured extraction (web_extract), and change tracking (web_watch). The only borderline pairs are web_batch vs web_crawl (both fetch multiple pages) and web_extract vs web_fetch (extraction is a specialization of fetching), but descriptions make the intended split clear.
Nearly all tools follow a predictable prefix_verb_noun scheme with two natural groups: web_* for fetching operations and session_* for credential management. The lone 'login' breaks the pattern (should be session_login/web_login), a minor deviation that is still readable.
Nine tools is well within the ideal 3-15 range for a scraping server, and each tool earns its place by covering a distinct fetch mode or session operation. No filler or trivially redundant tools.
The surface covers the full scraping lifecycle: single fetch, batch, crawl, structured extraction, change monitoring, and session login/export/import/list. The main gap is session lifecycle cleanup — no logout/session_delete or cache/robots inspection tool — but agents can work around this, so it's a minor gap rather than a blocker.