mcp-flaresolverr
Related Servers
Alternatives to mcp-flaresolverr
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables scraping and fetching websites with protection handling like Cloudflare and captchas, via an MCP interface.01Apache 2.0
- AlicenseAqualityDmaintenanceThis MCP server provides tools for interacting with Cloudflare Browser Rendering, allowing you to fetch and process web content for use as context in LLMs directly from Cline or Claude Desktop.511MIT
- FlicenseNot gradedqualityDmaintenanceA remote MCP server deployable on Cloudflare Workers without authentication, providing tools for website scraping and content extraction using Cloudflare's Browser Rendering and AI.1-
- AlicenseNot gradedqualityBmaintenanceRemote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.1MIT

zenrows-mcpofficial
AlicenseAqualityCmaintenanceScrape any webpage and return clean markdown, HTML, or structured JSON. Bypasses anti-bot protection, renders JavaScript (React/Vue/Angular), supports premium residential proxies and CSS extraction. Works with any MCP client — no local install required.11,065 npm19MIT- FlicenseNot gradedqualityBmaintenanceEnables local-first web scraping and captcha solving via an MCP server written in Rust.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: two HTTP request methods (GET/POST) and three session management operations (list/create/destroy). No overlap or ambiguity; an agent can easily select the correct tool.
All tools use snake_case with a consistent 'flare_' prefix, but the pattern is mixed: session tools include the resource noun 'session' (e.g., flare_session_create) while HTTP request tools omit it (e.g., flare_get). Minor deviation, still readable.
Five tools is well-scoped for this domain: two core request methods and three session lifecycle operations. Each tool earns its place with no redundancy.
The surface covers the standard FlareSolverr API completely: GET/POST requests and session create/list/destroy. No obvious missing operations for the stated purpose.