FineData MCP Server
Related Servers
Alternatives to FineData MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables AI agents to crawl, scrape, search, and automate browsers with anti-bot bypass, providing fast web access via 22 tools.2247 npm3MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI models to scrape and extract structured data from any website globally using a 195+ country proxy network with JavaScript rendering, anti-bot bypass, and output in Markdown, HTML, or Links format.MIT
- 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.35 npmISC
- FlicenseBqualityDmaintenanceEnables AI agents to browse and extract data from any public website via Bright Data's cloud infrastructure, handling proxy rotation, CAPTCHA solving, and JavaScript rendering.57-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform undetectable browser automation that bypasses Cloudflare, antibots, and social media blocks. Provides 105 tools for element extraction, network debugging, and real-world web scraping with a 98.7% success rate on protected sites.2,148MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to perform anti-bot web scraping, dynamic SPA rendering, YouTube transcript extraction, and deep OSINT/GEOINT intelligence gathering through 23 integrated tools.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no ambiguity: batch_scrape handles multiple URLs in parallel, scrape_async is for long-running single jobs, scrape_url is for immediate single requests with advanced features, get_job_status tracks async/batch jobs, and get_usage monitors API consumption. The descriptions explicitly differentiate use cases and workflows.
The naming follows a consistent snake_case pattern with clear verb_noun structures (e.g., batch_scrape, get_job_status, scrape_async). However, scrape_url deviates slightly by using a noun_verb format instead of a verb_noun pattern, which is a minor inconsistency in an otherwise predictable set.
With 5 tools, this server is well-scoped for web scraping operations. Each tool earns its place by covering distinct aspects of the workflow: submission (batch, async, immediate), status tracking, and usage monitoring. This count is neither too sparse nor bloated for the domain.
The tool surface provides complete coverage for the web scraping domain. It supports all key operations: multiple submission methods (batch, async, immediate), job lifecycle management (status tracking), and administrative functions (usage monitoring). There are no obvious gaps that would hinder agent workflows.