Scrapeless vs ScraperAPI

Scrapeless

Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package, both in the official MCP registry. llms.txt quotes Deep SerpApi at $0.1 per 1,000 while the plan data charges $1 per 1,000 for Google Search.

ScraperAPI

One GET request with a key and a URL returns a page, and the MCP server's 28 tools carry read-only and destructive hints. No status page, OpenAPI file, security.txt or certification was found, and the documented default puts the API key in the URL query string.

Scrapeless

1. Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
2. Call browser_close when done so the session and its billing stop
3. Set limit on crawl_start. Unset, it defaults to 10,000 pages
4. Crawls are asynchronous. Call crawl_start, then poll crawl_result with the returned id
5. Set SCRAPELESS_API_KEY for the stdio server. Older guides use SCRAPELESS_KEY, which still works as a fallback

ScraperAPI

1. Set the client timeout to 70 seconds. The API retries for that long before it returns 500, and a request cancelled earlier is still charged
2. Send the key as the x-sapi-api_key header to keep it out of URLs and logs
3. Pass max_cost on each request, or call /account/urlcost first, because domain and anti-bot surcharges vary from 1 to 75 credits
4. Use output_format=markdown or text to cut response size, and autoparse=true only on supported domains
5. On 429 reduce concurrency to the plan limit (5 on Free, 20 on Hobby). The request is rejected, not queued