F
licenseNot graded
qualityNot graded
maintenanceOfficial UProc Model Context Protocol server that enables AI assistants to reference and make decisions based on public web data.
-
Bright Data MCP
Officialby brightdata
Related Servers
Alternatives to Bright Data MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceModel Context Protocol server that enables Claude Desktop (or any MCP client) to fetch web content and process images appropriately.155 npmMIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots in real-time.4454 npm9MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots.3454 npm20MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server for web research. Bring real-time info into Claude and easily research any topic.3454 npm300MIT
302AI BrowserUse MCP Serverofficial
AlicenseAqualityDmaintenanceA Model Context Protocol server that enables Claude Desktop to browse the web, likely allowing the AI to access and interact with web content.237 npm9MIT
TDQS
B3.4/5.0
Scored across 32 tools
Disambiguation3/5
Most tools target distinct actions, but there is real overlap: scrape_as_html duplicates scrape_as_markdown with format='html', and scraping_browser_get_text/get_html and scrape_as_markdown's text/html formats read similar. The two AI-insight tools (chatgpt_ai_insights vs perplexity_ai_insights) and the scrape vs extract vs run_scraper trio are separable only by careful reading of descriptions.
Naming Consistency4/5
All snake_case and mostly verb_noun with clear group prefixes (scraping_browser_*, get_scraper_*, search_*). Minor deviations: bare 'extract', noun-first names like session_stats and chatgpt_ai_insights, and the ad-hoc 'as_' pattern in scrape_as_markdown/scrape_as_html, but nothing that breaks predictability.
Tool Count3/5
32 tools is heavy, driven mostly by the 14-tool scraping_browser_* automation subgroup. That subgroup is internally coherent and justified by the browser-automation capability, but combined with scraper/dataset/search/AI-insight tools the surface is larger than an agent can comfortably navigate.
Completeness4/5
Covers stateless scraping, batch, search, an extract/sampling path, full dataset and scraper lifecycle (discover, inspect, run, poll progress, fetch results, refresh), and full browser automation. Minor gaps: no explicit snapshot download/export or list/cancel of snapshots, and no dataset-schema discovery beyond filterable fields.
Maintenance
ActivityActive
ResponsivenessSlow