What is the main functional difference between HubVibe Site Audits and Brightdata MCP?

HubVibe Site Audits is categorized under Developer Tools and uses a remote HTTP/SSE transport. Brightdata MCP belongs to Developer Tools and uses a local stdio subprocess. Pick HubVibe Site Audits for developer tools work and Brightdata MCP for developer tools.

How do I install HubVibe Site Audits or Brightdata MCP in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Are HubVibe Site Audits and Brightdata MCP free to use, or do they require API keys?

HubVibe Site Audits has no declared pricing — check the project's own site. Brightdata MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both HubVibe Site Audits and Brightdata MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add hubvibe-site-audits and brightdata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, HubVibe Site Audits has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Brightdata MCP has 71/100 (Great) with 2 views, 0 installs and 2,661 GitHub stars.

HubVibe Site Audits vs Brightdata MCP

HubVibe Site Audits vs Brightdata MCP | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	HubVibe Site Audits	Brightdata MCP
Category	Developer Tools	Developer Tools
Quality signal	37/100 · Fair	71/100 · Great
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Local subprocess (stdio)
Auth	Not declared	Not declared
Pricing	Not declared	Not declared
Required env vars	`HUBVIBE_WALLET_KEYHUBVIBE_API_KEY`	`API_TOKEN`
Verified owner	Community listing	Community listing
GitHub stars	0	2,661
Directory activity	0 views 0 installs 0 upvotes	2 views 0 installs 0 upvotes
Tools	Not listed	11
Full listing	View HubVibe Site Audits	View Brightdata MCP

Tools & capabilities

HubVibe Site Audits tools

No tool names declared yet. Check the project README from the listing page.

Brightdata MCP tools 11

search_engineScrape search results from Google, Bing or Yandex. Returns SERP results in JSON or Markdown (URL, title, description),Ideal forgathering current information, news, and detailed search results.
scrape_as_markdownScrape a single webpage URL with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.
search_engine_batchRun multiple search queries simultaneously. Returns JSON for Google, Markdown for Bing/Yandex.
scrape_batchScrape multiple webpages URLs with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA.
discoverSearch the web and rank results by AI-driven relevance. Returns scored results with title, description, and URL. Supports intent-based ranking, geo-targeting, date filtering, and keyword filtering.
search_scrapersFind a Bright Data pre-built scraper (Web Scraper API, 1,200+ sites) for a site or data type, e.g. "amazon reviews" or "linkedin.com". Returns dataset_id, name, domain and collection_methods. Next: call get_scraper_details with a dataset_id and one method.
get_scraper_detailsShow the scraper description, input fields, example input and main output fields for one method. Call before run_scraper and build the input from sample_input or input_fields. Records may contain more fields than output_fields lists.
run_scraperRun a scraper method. input is a list of objects shaped like sample_input from get_scraper_details, one per URL or query. collect_by_url returns one record per input; discover_by_* methods return up to limit_per_input records per input, and every record is billed. Waits up to 45 seconds; if still running it returns snapshot_id with status "running": then poll get_scraper_progress and call get_scraper_results when ready. Records with an "error" field explain failed inputs.
get_scraper_progressStatus of a run: starting, running, ready, failed or canceled.
get_scraper_resultsRecords of a finished run. Returns status "running" if not ready yet.
refresh_scrapersReload the scraper list now instead of waiting for the daily refresh.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.